Sorry guys, this question should not be here. Anyway I already solved it. <div><br></div><div>Thank You and Sorry for inconvenience caused.<br><br><div class="gmail_quote">On Mon, Jun 28, 2010 at 9:29 AM, Reindy <span dir="ltr"><<a href="mailto:reindy@gmail.com">reindy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<div><br></div><div>I know this might be not DRBD issues, but it could related to all users here since most of us using drbd and heartbeat as well. Just curious, anyone encountered problem with DNS and NTP after reboot their server?</div>
<div><br></div><div><div>I'm having problem with my DNS and NTP.</div><div><br></div><div>For the DNS:</div><div>I'm using RHEL4, Bonding and heartbeat.</div><div>Bond0 IP address: 192.168.1.10</div><div>Heartbeat or Bond0:0: 192.168.1.50</div>
<div><br></div><div>Currently, I use my heartbeat ip address for my DNS or in named.conf</div><div><br></div><div>Everytime I reboot my server, it says that dns/named successfully started during the login process but after that when I type nslookup in shell, it did not show anything at all. But when I restart the named service by using "/etc/init.d/named restart" I able to nslookup my dns configuration.</div>
<div><br></div><div>I'm confused, what's going on? shouldnt redhat startup process starts my named? why do I need to restart the service again in order to make it works.. anyone can help?</div><div>--------------------------------------------------------------</div>
<div><br></div><div>For the NTP:</div><div>I'm using RHEL4, Bonding and heartbeat.</div><div>Bond0 IP address: 192.168.1.10</div><div>Heartbeat or Bond0:0: 192.168.1.50</div><div><br></div><div>I use NTP for server and client. I set my NTP configuration using my heartbeat IP (192.168.1.50)</div>
<div><br></div><div>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).</div>
<div><br></div><div>But when I restart ntpd "/etc/init.d/ntpd restart"</div><div><br></div><div>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.</div>
<div><br></div><div>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?</div><div><br></div><div>is there a way to tweak the named and ntpd to start after the heartbeat starts? or any idea on how you guys solved this issue?</div>
<div><br></div><div>Thanks.</div><div><br></div><div>Regards,</div><div>Rein</div></div>
</blockquote></div><br></div>