Configure Corporate DNS for the Federation Service and DRS
Applies To: Windows Server 2016, Windows Server 2012 R2
Step 6: Add a Host (A) and Alias (CNAME) Resource Record to Corporate DNS for the Federation Service and DRS
You must add the following resource records to corporate Domain Name System (DNS) for your federation service and Device Registration Service that you configured in previous steps.
|federation_service_name||Host (A)||IP address of the AD FS server or the IP address of the load balancer that is configured in front of your AD FS server farm|
You can use the following procedure to add a host (A) and alias (CNAME) resource records to corporate DNS for the federation server and the Device Registration Service.
Membership in Administrators, or equivalent, is the minimum requirement to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups.
To add a host (A) and alias (CNAME) resource records to DNS for your federation server
On you domain controller, in Server Manager, on the Tools menu, click DNS to open the DNS snap-in.
In the console tree, expand the domain_controller_name node, expand Forward Lookup Zones, right-click domain_name, and then click New Host (A or AAAA).
In the Name box, type the name to use for your AD FS farm.
In the IP address box, type the IP address of your federation server. Click Add Host.
Right-click the domain_name node, and then click New Alias (CNAME).
In the New Resource Record dialog box, type enterpriseregistration in the Alias name box.
In the fully qualified domain name (FQDN) of the target host box, type federation_service_farm_name.domain_name.com, and then click OK.
In a real world deployment, if your company has multiple User Principal Name (UPN) suffixes, you must create multiple CNAME records for each of those UPN suffixes in DNS.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.