//
you're reading...

How To's

How to override a single host on your Windows DNS Server

Situation

1. Your internal Active Directory domain name is different than your public Internet domain name. For example, your AD domain name might be contoso.local but your public Internet domain name might be contoso.com

2. You want to override a single host on contoso.com but your internal DNS server is not authoritative for that zone. For example, mail.contoso.com points to the external IP address of your mail server but you want to override it so that it points to the internal IP address of your mail server for internal clients only.

Problem

You could accomplish this by adding a record to the hosts file on every machine on your local network. But that would be very inefficient and hard to manage. You could also create a forward lookup zone for contoso.com on your internal DNS server, but then you would have to create host records for every host in that domain.

Solution

The solution is to create a forward lookup zone called ‘mail.contoso.com’ on your internal DNS server. This is technically called a subdomain. However, you can create a blank host record within that subdomain and point it to whatever IP address you want.

Be Sociable, Share!

Discussion

3 Responses to “How to override a single host on your Windows DNS Server”

  1. Thanks for that pointer Kent!

    Slight variation: Translated to your example situation, I’d like to internally resolve a couple of hosts like http://www.contoso.com, jobs.contoso.com etc. to resolve to a specific IP address (which is easy given your instructiona) but I would also like the FQDN contoso.com to resolve to the same IP address. Can that be achieved?

    Posted by Marco van den Berg | June 4, 2013, 3:41 am
  2. Brilliant! Works perfect for sub-domains, but I see answering Marco’s question may not be possible with this approach.

    Posted by Joel | November 13, 2013, 3:17 pm

Trackbacks/Pingbacks

  1. […] Just as a final note, you should also make sure you have a DNS record for autodiscover.youdomain.com that points to your Exchange server. So if your email address is joe@somedomain.com then you should have a DNS record that points autodiscover.somedomain.com to the IP address of your Exchange server. If your server is behind a NAT router, you should create a DNS record on your external DNS server that point to your servers external IP address, and you should create a DNS record on your internal DNS server that points to your servers internal IP address. If your internal and external domain names are different, you may need to review this article. […]

Post a Comment