> Mark_Andrews@xxxxxxx writes:
>
> >
> >> Hello all,
> >>
> >> I have a Sun box, running SunOS 5.8, and BIND 9.2.2rc1, as my primary
> >> DNS server.
> >>
> >> Everything worked fine until this morning, when we changed the netmask
> >> of the machine as part of a network capacity increase. After reboot, the
> >> "messages" file shows these errors when the reboot was run:
> >> Aug 27 05:54:33 sundns named[155]: [ID 295310 daemon.error]
> >> /etc/named.conf:15:
> >> syntax error near keys
> >> Aug 27 05:54:33 sundns named[155]: [ID 295310 daemon.error]
> >> /etc/named.conf:16:
> >> syntax error near '}'
> >>
> >> /etc/named.conf was not changed at all.
> >>
> >> The start of my named.conf files is:
> >>
> >> # Named.conf
> >> #
> >> options {
> >> directory "/var/named.d";
> >> pid-file "/var/run/named.pid";
> >> };
> >>
> >> key "rndc-key" {
> >> algorithm hmac-md5;
> >> secret "JxMFNeMU9BR1DYDiLbS0cQ==";
> >> };
> >>
> >> controls {
> >> inet 127.0.0.1 port 953
> >> allow { 127.0.0.1; } keys { "rndc-key"; };
> >> };
> >>
> >> zone "." {
> >> type hint;
> >> file "named.cache";
> >> };
> >>
> >> Now, when running "rndc reload example.com" or "rndc status" I get the
> >> error "rndc: recv failed: out of range".
> >>
> >> "rndc" by itself reports the version as Version: 9.2.2rc1
> >>
> >> The server accepts DIG and/or NSLOOKUP commands normally.
> >>
> >> The slave DNS server, running same OS and BIND versions, went thru same
> >> netmask changes, has no problems.
> >>
> >> Any ideas?
> >>
> >> Robert Kropiewnicki
> >> Network Administrator
> >> StructuredWeb Inc.
> >> Phone: 201-325-3146
> >> robert.kropiewnicki@xxxxxxxxxxxxxxxxx
> >
> > I suspect that you actually started a BIND 8 instance of
> > named. Note: it is unwise to run a RC version once the
> > final release is made.
> >
> > Mark
> > --
>
> Mark,
>
> That is what the scarce references we found via google seemed to suggest.
> The only problem with that scenario is that this machine was rebuilt from
> the OS up when we went to 9.2.2rc1. Prior to the rebuild, the machine was
> running SunOS 5.7 with a very out-of-date version of BIND 8 (might have been
> as old as 8.1.6) which we needed to get rid of for obvious reasons. Because
> the initial install was not well documented, the decision was made to wipe
> the server clean and then do the OS and BIND installs.
"keys" in the controls clause is only supported in BIND 9
Also BIND 9's named won't start if there is a error in named.conf.
The fact that named complain about keys but continued on indicates
that it is BIND 8's named.
> We did keep the zone files and named.conf we had from the previous install,
> having stored them on a separate machine and then brought them back upon OS
> install. The files passed the utility that checked for BIND 9 compliance as
> we had added the TTL statement to the beginning of the zone file.
BIND 9 named will run a BIND 8 config. BIND 8 will not run a
BIND 9 config. BIND 8 also support $TTL.
> This is not the first time this machine has been rebooted since the install.
> To add to the mystery, the other name server underwent the exact same
> process and is showing none of these symptoms. Other than new zone files
> being added and then this netmask adjustment, nothing else has changed.
>
> Is there anything in particular I should be looking for? I'm perfectly
> willing to find the answer for myself but in this case, given how few hits
> the error message gave, I could use a pointer in the right direction.
Your system startup scripts are starting "in.named" rather than
"named".
> Regards,
>
> Robert Kropiewnicki
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@xxxxxxx
|
