skip to Main Content

Configure internal DNS Exchange 2016

After installing Exchange Server 2016, the next step is to configure internal DNS in Exchange 2016. It’s essential to keep the same namespace internal and external. We will create a couple of forward lookup zones in Active Directory and test the namespaces. In the next article, we will configure external DNS for Exchange 2016. In this article, you will learn how to configure internal DNS in Exchange 2016.

Configure namespaces with Pinpoint DNS

Important: Read the article Exchange 2016 namespace design and planning before you go further.

You can configure the DNS zones internally with Pinpoint DNS or Split DNS. I recommend to configure it with Pinpoint DNS. Both the records that we are going to add will look like the following.

An architecture view of the Exchange 2016 namespace is shown below in the diagram.

Create Pinpoint DNS zone for mail

Open DNS Manager. Right-click on Forward Lookup Zones and select New Zone… from the context menu.

Configure internal DNS Exchange 2016 Create New Zone in Forward Lookup Zones

Click Next.

Configure internal DNS Exchange 2016 New zone wizard

Keep the default settings. Click Next.

Configure internal DNS Exchange 2016 Zone Type

Keep the default settings. Click Next.

In the Zone Name field, enter your external domain name (in our example mail.exoip.com).

Configure internal DNS Exchange 2016 Zone Replication Scope

We will manually create all the records in this zone, so select Do not allow dynamic updates. Click Next.

Configure internal DNS Exchange 2016 Zone Name Dynamic Update

Click Finish.

Configure internal DNS Exchange 2016 Complete New Zone

Create A record for mail

Expand Forward Lookup Zones. In the left pane, right-click on mail.exoip.com zone and select New Host (A or AAAA) from the context menu.

Configure internal DNS Exchange 2016 new host A record mail

In the IP address field, type the internal IP of your Exchange server. In our example, it is 192.168.1.52. Do you have a load balancer? Add that address. Click Add Host.

Configure internal DNS Exchange 2016 add new host

Host record mail.exoip.com is created. Click OK.

Configure internal DNS Exchange 2016 host record created

After creating the record, the PinPoint DNS zone should look similar to the example shown below.

Configure internal DNS Exchange 2016 mail forward lookup zone

The next step is to configure the same for autodiscover.

Create Pinpoint DNS zone for autodiscover

Open DNS Manager. Right-click on Forward Lookup Zones and select New Zone… from the context menu.

Configure internal DNS Exchange 2016 Create New Zone in Forward Lookup Zones autodiscover

Click Next.

Keep the default settings. Click Next.

Keep the default settings. Click Next.

In the Zone Name field, enter your external domain name (in our example autodiscover.exoip.com).

Configure internal DNS Exchange 2016 Zone Name autodiscover

We will manually create all the records in this zone, so select Do not allow dynamic updates. Click Next.

Click Finish.

Configure internal DNS Exchange 2016 complete New Zone autodiscover

Create A record for autodiscover

Expand Forward Lookup Zones. In the left pane, right-click on autodiscover.exoip.com zone and select New Host (A or AAAA) from the context menu.

Configure internal DNS Exchange 2016 new host A record autodiscover

In the IP address field, type the internal IP of your Exchange server. In our example, it is 192.168.1.52. Do you have a load balancer? Add that address. Click Add Host.

Configure internal DNS Exchange 2016 add new host autodiscover

Host record autodiscover.exoip.com is created. Click OK.

Configure internal DNS Exchange 2016 host record created autodiscover

After creating the record, the PinPoint DNS zone should look similar to the example shown below.

Configure internal DNS Exchange 2016 mail forward lookup zone autodiscover

In the next step, we will verify the Pinpoint DNS for both the zones.

Verify Pinpoint DNS zones

Log into Exchange Server or another system in the LAN network. Resolve both the mail and autodiscover DNS records or ping both of the DNS records. The answer will be the Exchange Server or load balancer IP address. That depends on the setup. In our example, it’s the Exchange Server. It’s essential to verify that it’s an internal DNS. Run PowerShell as administrator and use the Resolve-DnsName cmdlet.

Everything is looking great.

Log into Exchange with the newly configured namespace

Open your favorite browser and log into EAC with the newly configured DNS namespace, https://mail.yourdomain.com/ecp. Change yourdomain to yours. In our example, it’s the address https://mail.exoip.com/ecp.

You can keep logging into Exchange Admin Center with https://localhost/ecp, even if you have configured the newly DNS namespace.

A certificate warning will show up in your browser. We will cover Exchange certificates in the next article.

Test new namespace ECP warning security risk

Accept the risk and continue.

Test new namespace ECP warning browser certficate

The Exchange Admin Center screen will show up. You can log in with your credentials.

Test new namespace ECP

You are successfully logged in the Exchange Admin Center.

Test Internal DNS Exchange 2016 EAC

Reach the OWA address with https://mail.yourdomain.com/owa. In our example, it’s https://mail.exoip.com/owa.

Test new namespace OWA

Keep reading: Exchange 2016 firewall ports for mail flow and clients »

Conclusion

In this article, you learned how to configure internal DNS in Exchange 2016. You learned why and how to configure the namespaces. Test the configuration with the Resolve-DnsName cmdlet. You can also ping the records that you have configured.

Did you enjoy this article? You may also like Configure ReFS volume Exchange 2013/2016/2019. Don’t forget to follow us and share this article.

ALI TAJRAN

ALI TAJRAN

ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Connect with ALI TAJRAN on social media. Read more »

This Post Has 0 Comments

Leave a Reply

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

Back To Top