LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   named server error (https://www.linuxquestions.org/questions/linux-networking-3/named-server-error-446048/)

mchitrakar 05-18-2006 08:34 AM

named server error
 
I had a dns server running on RHLinux 9. And the named server pkg I am using is "bind-9.2.1-16". Now, this service has completely stopped. any attempt by:
#service named start gives [FAILED] error message.
I tried to #named and with its options like #named -d0. All give error message: Segmentation error. Viewing /var/log/messages shows just "myABC named: named startup failed".

I checked all conf files and found them OK.

before this anomaly, the server had rebooted several times due UPS problem and I had to fsck many times.


How can I solve this problem?do advise.

zaichik 05-18-2006 09:14 AM

How did you check the conf files?

How many zones do you have?

You'd think that if there were a problem with named.conf or a zone file, you'd see something more specific in the messages log.

mchitrakar 05-18-2006 09:44 AM

Only one domain (and that is intranet domain-"myABC.org") and not connected to internet directly.

did following:

#named-checkzone myABC.org /var/named/myABC.hosts
zone myABC.org/IN: loaded serial 2003071301
OK

checking /var/log/messages shows nothing (meaning no new error messages)

#named-checkconf
# (no errors reported)

checking /var/log/messages reveals nothing (meaning no new error messages)

and;
/etc/named.conf has:

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

zone "myABC.org" IN {
type master;
file "myABC.hosts";
allow-update { none; };
};

zone "0.168.192.in-addr.arpa" IN {
type master;
file "myABC.rev";
allow-update { none; };
};

zaichik 05-18-2006 10:00 AM

Hmm, looks OK to me. named.conf has the reverse lookup zone, and you haven't said anything about the zone file for that. But even so, if the file were missing or had errors, the error should be logged to messages, and it shouldn't prevent named from starting, let alone cause it to segfault.

I think you might have a corrupt binary, maybe caused by the power-cycling from the UPS. You might want to try uninstalling and reinstalling bind, or potentially using yum to try to update it if it was installed via RPM.

mchitrakar 05-18-2006 10:06 AM

thanks ...gotta try that..and abour reverse...there is a file "myABC.rev" but not included in the discussion because reverse dns lookup is not so important.

and thanks for your advice.

zaichik 05-18-2006 10:09 AM

I'll be interested in knowing how that turns out. Keep us posted, and good luck!

mchitrakar 05-18-2006 11:49 AM

great. it worked.
#rpm -e --nodeps bind-utils
#rpm -e --nodeps bind

#rpm -ivh --aid bind-utils
#rpm -ivh --aid bind

#service named start
[ OK ]

..thanks...

zaichik 05-18-2006 01:22 PM

Awesome! You're more than welcome--I love happy endings.


All times are GMT -5. The time now is 03:56 PM.