Red Hat Bugzilla – Bug 235809
bind crashes on restart and also when running without forwarders
Last modified: 2018-04-11 14:25:53 EDT
Description of problem:
Using bind as a caching nameserver (without chroot) to connect to my ISP and to
RH's intranet (see attached named.conf). I played a little bit with opendns.com,
but now I have forwarders set only to the DNS server of my ISP provider
Suddenly I begun to getting resolutions of everything to 220.127.116.11 -- couple of
times before I suspected some kind of misconfiguration and after couple of
restarts the problem went away. Today, it didn't so I switched off all
forwarding and run 'service named restart'. bind crashed I was able to make bind
working only when:
a) I set up forwarder again (this time just to my ISP DNS server, not OpenDNS)
b) I used 'service named stop; service named start' with 'service named restart'
bind constantly crashes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 152124 [details]
output of grep named /var/log/messages
Created attachment 152125 [details]
Optional schema is this:
When you want use named like caching-only nameserver, please install
caching-nameserver package and work with /etc/named.caching-nameserver.conf &
/etc/named.rfc1912.zones configfiles. If you want use named like local
nameserver, please config your own zones and put your configuration to
/etc/named.conf (for example with system-config-bind utility). This always works
better than "wild" configurations which you write :). But this end of named
(sigsegv) is really bad, so let me check it.
Just for the record -- I DID try system-config-bind and the results were exactly
the same as with my own named.conf (actually, the generated named.conf was the
same, so no surprise here).
Could be fixed in latest bind.
bind-9.4.1-4.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.