Re: issue with DC replication
- From: "Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jun 2009 09:39:42 -0400
"millin" <ssuj@xxxxxxxxxxxxxxxxxxxxxxxxx(No Spam)> wrote in message news:F7E9E91A-09C9-4545-B073-E43400A7FB7F@xxxxxxxxxxxxxxxx
Hi Ace,
Thanks for the suggestion.
As per your suggestion I have set up one NIC for name resolution and still I
am not able to achieve what
I am really looking for.
is there any mechanism there to switch over straight away from the preferred
DNS server to
other DNS before taking down ,the one which is providing name resolution
service.
Testing Network Scenario:
1)2 On-Line Web Servers.(Web 01 and web 02)-Clustered using NLB.
2)2 DNS Servers.(DC-01&Dc-02).---Both are AD-I.
PS: what happens if the DNS Server running on a different subnet other than
web boxes.
Regards
Mill
Hi Mill,
Which exact suggestion did you follow? Did you disable the additional NIC, so there is only one now? Is the web server using the DC/DNS servers as their only DNS addresses, or is there a mixture of internal and external DNS?
When entering multiple DNS addresses in a NIC properties, they must all reference internal DNS only that either host the internal zone, or a have a reference to it. Multiple addresses are not load balancing, meaning it will check the first, and if no answer (only if no answer), will it go to the next one, then removing the first one out of the "eligible resolvers list" for 15 minutes before it resets the list automatically. That is why any DNS addresses in there must all have the same exact info on the DNS servers, or have a way to get to the DNS server with the same answer (either using secondaries, stubs, or conditional forwarding). Now if the first one gives an "NXDOMAIN" response, that means it doesn't know the answer, and being a non-answer, it is an answer, and will look no further. That is why all DNS entered must have references to internal resources or to zone data that needs to be available to all machines internally.
So I am a little confused why, that is if the only DNS servers listed are your DCs, why you would want to try to reset the list? Theoretically, as I stated, they BOTH should be able to resolve for you. If the first one doesn't respond, it will automatically go to the next one.
Also, if DNS is on another subnet, it wouldn't matter because your internal infrastructure knows how to route to get to the other subnets, unless there's a problem in that area?
Ace
.
- Follow-Ups:
- Re: issue with DC replication
- From: Jorge Silva
- Re: issue with DC replication
- References:
- issue with DC replication
- From: millin
- Re: issue with DC replication
- From: Jorge Silva
- Re: issue with DC replication
- From: millin
- Re: issue with DC replication
- From: Jorge Silva
- Re: issue with DC replication
- From: millin
- Re: issue with DC replication
- From: Jorge Silva
- Re: issue with DC replication
- From: millin
- Re: issue with DC replication
- From: Ace Fekay [Microsoft Certified Trainer]
- Re: issue with DC replication
- From: millin
- issue with DC replication
- Prev by Date: Re: issue with DC replication
- Next by Date: RE: NPS DHCP with NAP
- Previous by thread: Re: issue with DC replication
- Next by thread: Re: issue with DC replication
- Index(es):
Relevant Pages
|