Installed bind9.1.2 but named is behaving like bind8

Jim Reid jim at rfc1035.com
Wed Jun 27 15:25:19 UTC 2001


>>>>> "Matthias" == Matthias Laube <laubm at freenet.de> writes:

    Matthias> I recently installed bind9.1.2 on my Suse Linux 7.1
    Matthias> system where bind8 was installed before. Now -though I'm
    Matthias> a newbie to dns configuring - it seems that named
    Matthias> doesn't understand the named.conf in the bind9 style, as
    Matthias> he is claiming a syntax error for the statement:

    Matthias> controls { inet 192.168.0.2 port 953 allow {localhost; } keys { rndc_key; }; };

    Matthias> He doesn't understand the 'keys' statement. I looked it
    Matthias> up in the bind8 manuals and there this feature has not
    Matthias> existed yet. 

The above controls{} statment is perfectly valid for BIND9. It is
illegal syntax for BIND8. So if you are getting syntax errors -- why
didn't you show them? -- it means you're running a BIND8 rather than a
BIND9 server. That suggests you've not installed BIND9 or else there's
an old BIND8 named executable which is found in your search path
before the BIND9 one.

You might find it helpful to read the BIND9 documentation if you want
to know about BIND9. The BIND9 Administrator's Reference Manual is in
doc/arm and some migration notes are in doc/misc. If you consult the
BIND8 documentation instead you will get confusing, irrelevant, out of
date or even incorrect information about BIND9.


More information about the bind-users mailing list