Thursday , October 29 2020
Home - Don't Forget! - How to use DNS Pin Point instead Split Horizon – the easy way!

How to use DNS Pin Point instead Split Horizon – the easy way!

Background on the DNS issue faced

There are times when DNS split horizon is required to point an ‘A’ record to an internal address however this normally requires you to duplicate every record in the zone on the internal DNS server.  For example without needing the whole domain of being duplicated on the internal DNS servers.

An example of an external zone for a company:

Record TypeHostAddress


The normal approach for split dns requires you to duplicate all the entires in the zone on your internal DNS server.  This is risky with changes to the public zone not always being updated on the internal zone. An example of an internal required zone design:

Record TypeHostAddress

The table above show how an internal zone allows for internal clients to use an internal IP address for the host name of “”.

The Easy Solution

If you have internal Windows Server 2012 or higher there is a easy to achieve the same results without having to duplicate all the entires.  This creates a zone and with the same name as the record for the DNS entry you are pin pointing.

First step is the creation of a DNS zone for the hostname (not the domain name zone!) with powershell command:

Add-DnsServerPrimaryZone -Name -ReplicationScope Forest

The second step creates a record type of ‘A’ with the same name as the DNS zone:

Add-DnsServerResourceRecordA -IPv4Address -ZoneName -Name 


The much long version of how to configure this feature can be found here:

Check Also

How To Change Your Office 365 App Password

If you are enabled for Multi-Factor Authentication (MFA) in Office 365 then you will need …

Leave a Reply

Your email address will not be published. Required fields are marked *