DHCP giving wrong DNS

I have a windows 2003 server that was an AD/DNS/DHCP server.
I removed the AD/DNS to another machine and changed all the configuration of
the DHCP server to point to the new address.

Now when clients get addresses they receive the old DNS configuration that
was there 6 months ago. doing an release/renew will provide them the good
DNS. The DHCP server is always the same

I ran a dhcploc and can't find any other server.
Could it be a corrupt database ?

I can't see it being a corrupt database is you run an ipconfig /renew and
they get the correct configuration, including DNS and other settings.

How long is the lease?

The lease is 4 days on that subnet.

"Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
news:AF8542E3-E79D-401D-8798-C73FCC8A6263@microsoft.com...
> Hi Ace
>
> The lease is 4 days on that subnet.
>
Then it doesn't make sense that when they get a new lease they have the
wrong DNS config. Whenever a client gets a new lease, such as when and if it
was restarted, it will get the current Options set in DHCP.

When you run an ipconfig /all on both an offending machine and a good one,
does it both show the same DHCP server?

Ace

Yes they show the same DHCP Server, that's why I was thinking the DB was
corrupt

"Ace Fekay [MCT]" wrote:

> "Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
> news:AF8542E3-E79D-401D-8798-C73FCC8A6263@microsoft.com...
> > Hi Ace
> >
> > The lease is 4 days on that subnet.
> >
> Then it doesn't make sense that when they get a new lease they have the
> wrong DNS config. Whenever a client gets a new lease, such as when and if it
> was restarted, it will get the current Options set in DHCP.
>
> When you run an ipconfig /all on both an offending machine and a good one,
> does it both show the same DHCP server?
>
> Ace
>
>
> .
>

"Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
news:29EF5D5F-8FB0-403D-9162-C3A067CD8FA6@microsoft.com...
> Yes they show the same DHCP Server, that's why I was thinking the DB was
> corrupt

Not if a renew works. If you restart a workstation, does it work? If so,
have any of the workstations been restarted since the change?

Ace

Usually a restart will not work, I have to do /release /renew to get a new ip.
The DNS change has been done 6months ago, a couple of power failures and
normal shutdowns passed.

There is no logic as to when the workstations gets the old configuration

"Ace Fekay [MCT]" wrote:

> "Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
> news:29EF5D5F-8FB0-403D-9162-C3A067CD8FA6@microsoft.com...
> > Yes they show the same DHCP Server, that's why I was thinking the DB was
> > corrupt
>
> Not if a renew works. If you restart a workstation, does it work? If so,
> have any of the workstations been restarted since the change?
>
> Ace
>
>
>
> .
>

I'd recommend turning off network switch(es) next weekend (or Friday
afternoon). Keep the switch(es) turned of for couple of minutes, then turn
them back on. I know it's drastic, but it works. I tried this several times
already and it worked for me.

"Dan Dussault" <Dan Dussault@discussions.microsoft.com> wrote in message
news:77EBE77B-4633-4DF4-BAEB-1A9E1F8F88B9@microsoft.com...
> I have a windows 2003 server that was an AD/DNS/DHCP server.
> I removed the AD/DNS to another machine and changed all the configuration
> of
> the DHCP server to point to the new address.
>
> Now when clients get addresses they receive the old DNS configuration that
> was there 6 months ago. doing an release/renew will provide them the good
> DNS. The DHCP server is always the same
>
> I ran a dhcploc and can't find any other server.
> Could it be a corrupt database ?
>

"Dusko Savatovic" <savatovic@nospam.gmail.com> wrote in message
news:%23UJdKhtcKHA.1652@TK2MSFTNGP05.phx.gbl...
> I'd recommend turning off network switch(es) next weekend (or Friday
> afternoon). Keep the switch(es) turned of for couple of minutes, then turn
> them back on. I know it's drastic, but it works. I tried this several
> times already and it worked for me.

Drastic is putting it mildly. :-)

But if it works... why not!

Ace

Dan Dussault wrote:
> Usually a restart will not work, I have to do /release /renew to get a new ip.
> The DNS change has been done 6months ago, a couple of power failures and
> normal shutdowns passed.
>
> There is no logic as to when the workstations gets the old configuration
>
> "Ace Fekay [MCT]" wrote:
>
>> "Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
>> news:29EF5D5F-8FB0-403D-9162-C3A067CD8FA6@microsoft.com...
>>> Yes they show the same DHCP Server, that's why I was thinking the DB was
>>> corrupt
>> Not if a renew works. If you restart a workstation, does it work? If so,
>> have any of the workstations been restarted since the change?
>>
>> Ace
>>
>>
>>
>> .
>>

Just a stab, but whenever I have an invalid DNS resolution on a
workstation, I issue "ipconfig /flushdns".

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/

"Dan Dussault" <DanDussault@discussions.microsoft.com> wrote in message
news:316F81B8-80BA-4D51-9B19-2D9FD7DEBC6B@microsoft.com...
> Usually a restart will not work, I have to do /release /renew to get a new
> ip.
> The DNS change has been done 6months ago, a couple of power failures and
> normal shutdowns passed.
>
> There is no logic as to when the workstations gets the old configuration
>

Is there a GPO controlling DNS settings?

Ace