named does not listen on eth0 right after boot.
This is a weird problem I'm pitted against on my Fedora 9 server which I would like to have as a local dns caching server on my network.
What happens is that right after reboot, named refuses to listen on the ethernet interface. I have to do /etc/init.d/named restart to read the named.conf file again and begin working.
I came to know this through this log entry (showing the named restart cycle)
My firewall ports are open, and things work well right after a named restart, but I certainly wouldn't like doing it after each reboot of the server.
Can anyone tell me what the problem is? Is it a bug in named?
I had added this entry to the named.conf file to listen on the ethernet interface:
Have you verified that the interface is actually up and working at the point named starts?
To eliminate the edns timeouts, add:
About the listening issue, that is something that had also occurred to me, but I didn't know how to do it. Some pointers please.
You can test the theory by adding a line to the /etc/rc.d/named script that shows the output of ifconfig -a. Add the line:
ifconfig -a > /tmp/testing.out
somewhere near the top. Then either reboot, or bring the system down to run level 1 and back up to either 3 or 5 as is normal for you (stated in /etc/inittab). Check the contents of /tmp/testing.out. Either eth0 will exist and be up, or not.
If eth0 is not up, look in /var/log/messages and /var/log/dmesg for clues as to eth0.
It is possible it is coming up slowly, and/or named is started before the interface is fully ready.
The scripts in /etc/init.d are run in numeric order. I don't recall what scripts exist in Fedora. If there is a named or bind startup/stop script, determine its number and determine where it is relative to the script that starts up networking.
If this isn't clear, show output of :
ls -ld /etc/rc2.d/* /etc/rc3.d/*
Your goal is to
I had the same problem, and the way I fixed it is as follows
1. Disable "Network Manager" from the list of services at boot-up time
2. Enable "network"
1. Uncheck the "Controlled by NetworkManager" from the Device (in my case eth0)
Reboot the machine and presto!
I don't have a good explanation, but I think if Bind is started before the computer acquires an IP address (by Network Manager) then it won't Listen on the IP address that doesn't know at that time.
|All times are GMT -5. The time now is 10:44 PM.|