DHCP client receving address from one server and scope options from another

I am having trouble understanding something that is occuring on one of
my client computers. I am in the process of bringing a new Windows
2003 R2 DC online to replace an old Windows 2000 DC. Both servers are
running DHCP (with non-overlapping scopes), DNS, WINS. There is
another Windows 2000 server on the same network offering the same
services. My previous setup is as follows:

All DHCP servers have non-overlapping scopes and each scope provides
scope options to point DHCP clients to DNS and WINS servers. When a
DHCP server offers a client an address, the options that it sends
always list the DHCP server as the primary server for DNS and WINS. So
for example, Server A gives out an address and the DNS options for it
would be Server A as the primary, and Server B as the secondary. This
has always worked without any problems. With the addition of the new
server I am seeing some very strange behaviour. In particular, one
client is getting a DHCP address from Server C (the new server), but
it's getting it's DNS scope options from Server B. The WINS scope
options on the other hand are coming from Server C as they should be.

If I release and renew the IP address on the affected client, it gets
all of the proper settings. It gets all scope options from Server C.
But, a few minutes later (5-15) when I check the client using IPCONFIG
/ALL, the DNS options have changed to those offered by Server B.

Does anyone have any insight into why this is happening, or any
suggestions for how I would troubleshoot? There are no errors in the
event logs on the clients or servers, and dns resolution on all servers
seems to be working fine when checked with NSLOOKUP.

Thanks,
Troy.

.

Relevant Pages

  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Dual NIC vs Single NIC
    ... |> 135919 DNS Server Search Order Functionality in Windows ... Thank you for helping me to correct the misunderstand of DNS query ... Thank you again for your supplement about the client DNS cache issue. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dual NIC vs Single NIC
    ... I will again argue that turning off the client DNS cache (0 refresh ... 261968 Explanation of the Server List Management Feature in the Domain ... Internet when the SBS server is offline. ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)