Strange DNS behavior

Hi all,

I have a Windows Server 2003R2 Active Directory domain with three AD
integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. No matter
which servers my XP workstations are configured to use, they want to go
to x.x.x.85. For example if I type a nslookup query, it performs the
query against x.x.x.85. The problem comes when I have to take this
machine down or maintenance or patching. Clients lose the ability to
resolve names. The clients don't revert to their secondary DNS server
listed in their IP configuration (most clients are DHCP for the IP
address but static for DNS settings). Any insight or suggests is much
appreciated!

Thanks,
MW

I've seen this in all the AD setups I've worked in. There are those in the
newsgroup that say they have seen the client roll over to the secondary DNS
but I have never seen it happen in actual production.

Maybe someone will post a solution we both can learn from.

DDS
<> wrote in message
news:%23Zx3q$...
> Hi all,
>
> I have a Windows Server 2003R2 Active Directory domain with three AD
> integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. No matter which
> servers my XP workstations are configured to use, they want to go to
> x.x.x.85. For example if I type a nslookup query, it performs the query
> against x.x.x.85. The problem comes when I have to take this machine down
> or maintenance or patching. Clients lose the ability to resolve names. The
> clients don't revert to their secondary DNS server listed in their IP
> configuration (most clients are DHCP for the IP address but static for DNS
> settings). Any insight or suggests is much appreciated!
>
> Thanks,
> MW

<> wrote in message
news:%23Zx3q$...
> Hi all,
>
> I have a Windows Server 2003R2 Active Directory domain with three AD
> integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. No matter which
> servers my XP workstations are configured to use, they want to go to
> x.x.x.85. For example if I type a nslookup query, it performs the query
> against x.x.x.85. The problem comes when I have to take this machine down
> or maintenance or patching. Clients lose the ability to resolve names. The
> clients don't revert to their secondary DNS server listed in their IP
> configuration (most clients are DHCP for the IP address but static for DNS
> settings). Any insight or suggests is much appreciated!
>
> Thanks,
> MW


This is due to the client side resolver's algorithm and how it uses the DNS
addresses listed in the DNS list of the NIC.It also has to do with the
client side resolver local cache. There are other factors as well, such as
Outlook caching the DSAcces request. There's more to this than meets the
eye. Having multiple DNS addresses DO NOT give you fault tolerance based on
the algorithm and these factors.

Please read my blog on this behavior. I hope you find it helpful.

DNS, WINS & the Client Side Resolver, NetBIOS, Browser Service, Disabling
NetBIOS, Direct Hosted SMB (DirectSMB), If One DC is Down, Does a Client
logon to Another DC, and DNS Forwarders Algorithm
http://msmvps.com/blogs/acefekay/arc...algorithm.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

Hello ,

Have a look into for the name resolution process:
http://technet.microsoft.com/en-us/l.../cc961411.aspx

http://technet.microsoft.com/en-us/l...37(WS.10).aspx

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


> Hi all,
>
> I have a Windows Server 2003R2 Active Directory domain with three AD
> integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. No matter
> which servers my XP workstations are configured to use, they want to
> go to x.x.x.85. For example if I type a nslookup query, it performs
> the query against x.x.x.85. The problem comes when I have to take this
> machine down or maintenance or patching. Clients lose the ability to
> resolve names. The clients don't revert to their secondary DNS server
> listed in their IP configuration (most clients are DHCP for the IP
> address but static for DNS settings). Any insight or suggests is much
> appreciated!
>
> Thanks,
> M

Why you are making alternate ip address as static,assign the alernate ip address also from DHCP server,so this may help you.



testpe wrote:

Strange DNS behavior
06-Jan-10

Hi all

I have a Windows Server 2003R2 Active Directory domain with three A
integrated DNS servers, x.x.x.85, x.x.x.87, and x.x.x.95. No matte
which servers my XP workstations are configured to use, they want to g
to x.x.x.85. For example if I type a nslookup query, it performs th
query against x.x.x.85. The problem comes when I have to take thi
machine down or maintenance or patching. Clients lose the ability t
resolve names. The clients do not revert to their secondary DNS serve
listed in their IP configuration (most clients are DHCP for the I
address but static for DNS settings). Any insight or suggests is muc
appreciated

Thanks
MW

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
SQL Server Reporting Services - Lessons Learned
http://www.eggheadcafe.com/tutorials...ting-serv.aspx

In message < lhost>
Jonathan de Boyne Pollard <J.deBoynePollard-> was
claimed to have wrote:

>As M. Fekay pointed out, not only is the fallback procedure used
>by the Microsoft DNS Client service not as entirely straightforward
>as one would at first assume, it also varies from version to version
>of Windows NT, with different algorithms employed by different versions,
>and with known problems in several versions about ignoring proxy DNS servers.

More annoyingly, it's also very different with DNS Cache enabled vs
disabled.

"Dave Warren" <dave-> wrote in message
news:...
> In message < lhost>
> Jonathan de Boyne Pollard <J.deBoynePollard-> was
> claimed to have wrote:
>
>>As M. Fekay pointed out, not only is the fallback procedure used
>>by the Microsoft DNS Client service not as entirely straightforward
>>as one would at first assume, it also varies from version to version
>>of Windows NT, with different algorithms employed by different versions,
>>and with known problems in several versions about ignoring proxy DNS
>>servers.
>
> More annoyingly, it's also very different with DNS Cache enabled vs
> disabled.


If you disable the client side cache, assuming that's what you are referring
to, yes, it will alter the behavior.

Ace