DHCP not providing correct DNS all of the time

[Guest Jeremey]

Hello,

I have a client that is having an issue after demoting old Windows 2000

Server, which prior to putting in a new 2003 server was the FSMO roles

holder, that some times when a pc reboots it points to the 2000 server for

DNS when the DHCP server on the 2003 DC is set for the DHCP server to give

the 2003 IP as the DNS server. The only way around the fix is to flush dns

and a release/renew and then it gets the correct IP. When this does happen

it shows that it obtained the IP from the 2003 server and not some rogue DHCP

server.

The goal is to shut down the 2000 server and upgrade some parts so it can be

reinstalled as a 2003 server, but until we can fix this it still needs to

stay up. Is there anything in a GPO that might be triggering this?

 

Thanks,

Jeremey

[Guest Meinolf Weber]

Re: DHCP not providing correct DNS all of the time

 

Hello Jeremey,

 

Did you unauthorize the 2000 DHCP server in AD and remove the scopes from

it before also?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello,

> I have a client that is having an issue after demoting old Windows

> 2000

> Server, which prior to putting in a new 2003 server was the FSMO roles

> holder, that some times when a pc reboots it points to the 2000 server

> for

> DNS when the DHCP server on the 2003 DC is set for the DHCP server to

> give

> the 2003 IP as the DNS server. The only way around the fix is to

> flush dns

> and a release/renew and then it gets the correct IP. When this does

> happen

> it shows that it obtained the IP from the 2003 server and not some

> rogue DHCP

> server.

> The goal is to shut down the 2000 server and upgrade some parts so it

> can be

> reinstalled as a 2003 server, but until we can fix this it still needs

> to

> stay up. Is there anything in a GPO that might be triggering this?

> Thanks,

> Jeremey