On Mon, Feb 8, 2010 at 3:36 PM, Emmanuel Sekyewa <[email protected]> wrote: > Good afternoon, > > I'm in a situation in which after changing the IP addressing scheme on a > network, certain machines obtain a wrong entry for DNS at startup, but when > I run an ipconfig /release and subsequently /renew, they pick up the correct > settings/configuration for the DNS server. I have gone through my DHCP > configuration a number of times to ensure that the correct IP addresses are > specified for the primary and secondary DNS servers, but this still keeps > coming up. > This even happens after flushing the DNS cache on a client machine and > rebooting. > Any ideas of what could be causing this? Or a viable work around? >
1 -- what platform are you running you DHCP server? 2 -- The quickest way to check whether you have another DHCP server on the LAN is to run tcpdump and listen out for any bootp traffic. A quick run of tcpdump -i <interface> -n port 67 or port 68 will show you all bootp traffic on your LAN. 3 -- If you did not change the scope on your DHCP server, you may end up with some wrong info. -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ------------------------------------------------------------ _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
