We've recently migrated from a unix/BIND based DHCP setup to a new Windows
2003 DNS/DHCP server. We've setup a domain just for our windows network. We
used a script to create all the reservations for the IP's we'll give out and
are not allowing unknown mac's on our network.
When a computer is booted for the first time of the day, certain info is not
correct when you look at ipconfig /all - the DNS connection specific suffix
and the DNS server info is wrong. If you do a ipconfig /renew, the
information is correct. If you reboot, the correct info sticks. I don't
know how long you need to leave a computer off for it to lose the correct
info.
This happens for every computer we cold boot for the first time of the day.
This happens whether the computer has been added to the domain or not. I
created a GPO to try to force feed the correct info and it doesn't take
either ( for systems that are part of the domain ).
I've doubled checked the scope options and even set the server options the
same for DNS connection specific suffix and DNS servers. Because the lease
is correct once you renew, I don't know what to check on the server side.
This is a new AD install and this DHCP/DNS setup is an important first step
for our migration to an MS AD domain. I need to correct this kink before
moving on to step two.
Any and all assistance is GREATLY appreciated.
|
Similar Threads
Linear Mode
