![]() |
|
1
4th May 00:32
External User
Posts: 1
|
We had a similar problem on class B network. When round robin and netmask
ordering were enabled, DNS will present the A records of two local subnet domain controllers and the two remote controllers on different subnets. We disabled round robin on our local subnet 192.168.x.x and indeed netmask ordering will present the DC server closest to this subnet. We currenlty have two DNS ending on .100 and .101. it seems that now after the change all the DNS lookups are going through .101. any particular reason why .101 is the primary choice and not the other DNS server? BTW both servers are AD controllers and GC's. subnets on Sites and services have been setup as well. tx Raul Carrion raul@spotrunner.com |
|
|
SPONSORED LINKS BY GOOGLE |
|
|