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

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Anindya Sen <Anindya Sen@discussions.microsoft.com> wrote:
>
> IN addition to Jorge's replies, I would like to add this.
>
> > But when it is joining the domain it is going to some other domain
> > controller say 10.80.0.5.
>
> When a computer joins the domain it is not just a member of the DC it
> connects to. When joining the domain it will use the first DC that responds.
> Though, if Netmask ordering is enabled and round robin is disabled it will
> get the domain IP that is the closest match for its subnet.
> Does each site (subnet) have a Global Catalog?
>
> >
> > nslookup a.co.in( where a.co.in) is the domain, returns all the ips of
> > the a.co.in DCs and it keeps on changing( even the first value).
>
> On your DNS servers' Advanced tab, clear the check box for "Enable round
> robin" and check the box "Enable Netmask ordering"
> This will insure that if there is more than one host for the name, The first
> address returned will be one that matches its subnet.
>
> For Dynamic DNS registration to work, the machine needs a primary DNS
> suffix that matches the domain it is supposed to register in. Or
> alternately, it will use the connection specific suffix, IF you have
> selected "Use this connection's DNS suffix for DNS registration". Either of
> these require "register thei connections addresses in DNS"
> They also require the DHCP client service to be running, regardless if the
> client is not a DHCP client.
> Also. it will try to register using the DNS servers listed in TCP/IP
> properties. So if the router is assigning addresses, make sure the router
> only assigns DNS servers that support the AD domain.
>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This s
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oe.com/OEBackup/Default.aspx
> ===================================
>
>
>