Home / server / Questions / 241649
Accepted
Ryaner
Asked: 2011-03-02 05:11:24 +0800 CST

Active Directory DNS - Change entry only on one site

  • 772

Some background information first. We run a split horizon dns setup. So publicly entry.ourdomain.com goes to 123.123.123.123 (Public Address) and internally, entry.ourdomain.com goes to 10.1.1.1 (Internal Address). The zone for ourdomain.com is integrated into AD for replication. For this problem, we have two sites, siteA and RemoteSiteB. The two are connected via a site-to-site vpn so users can access both internal and external addresses.

What we want is to have users in RemoteSiteB go to the public address for particular entries on our domain, but only in that site.

Is there any way to achieve this without putting the zone back to an non integrated AD one? Doing so looses all the replication features.

Servers are all 2008R2 in case that makes any difference.

Edits for clarity. This is the DNS responses I'm looking to achive

SiteA DNS:
entry.ourdomain.com -> 10.1.1.1
entry2.ourdomain.com -> 10.1.1.2

RemoteSiteB DNS:
entry.ourdomain.com -> 123.123.123.123
entry2.ourdomain.com -> 10.1.1.2

domain-name-system active-directory

2 Answers

  1. Best Answer

    I would recommend putting the zone back to non integrated and using forwarders to achieve what you want. In this scenario you can still keep 1 record of the zone that every site can use.

    In the example.

    SiteA
ourdomain.com - NS for the zone - AD replicated
entry.ourdomain.com - NS for the zone - no replication

SiteB
ourdomain - NS for the zone - AD replicated
entry.ourdomain.com - forwards to the internet DNS server
subdomain.entry.ourdomain.com - forwards to site A
ourdomain.com - forwards to site A
anyotherrecord.ourdomain.com - forwards to site A

    Setting up forwards in DNS is very easy http://technet.microsoft.com/en-us/library/cc754941.aspx

    Alternatively, you could use a secondary DNS server in site B that everyone used, but that sounds a bit silly for your purpose, or host files on local machines, but that might be a bit silly as well.

    Also, it may be you do not want to have a single copy of the DNS records, in that case you could use a secondary DNS server in Site A or Site B that was also a nameserver for the domain, and you can configure 2 forwarder address for redundancy.

    If you have trouble with the forwarders please comment so I can provide more info.

    Hope this helps you.

    • 2

  2. Wanted to give a clear answer of the solution we've established based on the answer from pablo.

    ourdomain.com - AD integrated Domain

    In the DNS of RemoteSiteB, we added a subzone for entry.ourdomain.com. Inside of this zone, we added the blank A record for the public address we are directing traffic to.

    This way all the replication from the primary server is being handled and the individual entries are being overridden where required.

    • 0