Emergency UNIX and Linux Support

Hi,

I'm having problem with my DNS and NTP.

For the DNS:
I'm using RHEL4, Bonding and heartbeat.
Bond0 IP address: 192.168.1.10
Heartbeat or Bond0:0: 192.168.1.50

Currently, I use my heartbeat ip address for my DNS or in named.conf

Everytime I reboot my server, it says that dns/named successfully started but when I type nslookup in shell, it did not show anything at all. But when I restart named by using "/etc/init.d/named restart" I able to nslookup my dns configuration.

I'm confused, what's going on? shouldnt redhat startup process starts my named? why do I need to restart again.. anyone can help?
--------------------------------------------------------------

For the NTP:
I'm using RHEL4, Bonding and heartbeat.
Bond0 IP address: 192.168.1.10
Heartbeat or Bond0:0: 192.168.1.50

I use NTP for server and client. I set my NTP configuration using my heartbeat IP (192.168.1.50)

I able to sync from server to client, the problem is also after I reboot the server. the ntpd is running, but when I trace the wireshark from my server, actually my server send the packets by using my bond0 ip address (192.168.1.10) instead using my heartbeat ip (192.168.1.50).

But when I restart ntpd "/etc/init.d/ntpd restart"

I trace again from wireshark, the server starts to send packets using my heartbeat ip address (192.168.1.50) which is the way it supposed to be.

I'm confused, whats happening here? is it because my named and ntpd starts before the heartbeat starts during the startup process when I reboot the server?

is there a way to tweak the named and ntpd to start after the heartbeat starts?

Thank You.

I think that you're probably right - it might very well be a start order issue.

To change the order, since you're running RH, edit the start scripts for named and ntpd in /etc/init.d and find the line:

# chkconfig: -

The two numbers after that are the numbers that control the start, and the stop, respectively.

For example, if it's "13 87" for named, you will be able to see that there's a symlink in /etc/rc3.d called S13named (and in all the other run levels that named is configured to start in) and also one called K87named in /etc/rc6.d (and the runlevels that named is configured to be stopped at).

Edit the first number to increase the number to start named and ntpd after the bond. Increase the second number to have those processes shut down before the bond.

Then you can use "chkconfig --del named" and "chkconfig --del ntpd" to remove the existing symlinks, and then "chkconfig --add named" and "chkconfig --add ntpd" to add them with the new orders.

under some distros, "servers" has to be enabled :

for instance the word ENABLE has to be in /etc/default/serverd (ntp or other services)

please check that .

also, is it to much for u to give us a ls -R of your rc?.d and the likes ...

order issue / scripts executable or not ...

regards

I have had this problem with SuSE when using NetworkManager and DHCP. The Named comes up before the DHCP has successfully registered itself and named then does not work. My bodgy fix was to add a service restart for named in the local init file which initalizes last. I then stopped using NetworkManager and everything seemed to work again - I presume the static network scripts probably work better with their startup sequence ordering...