DNS is a server role that you can install by using Server Manager or Windows PowerShell commands. If you are installing a new Active Directory forest and domain, DNS is automatically installed with Active Directory as the Global Catalogue server for the forest and domain. In this article, we shall discuss “What happens when WDS and DNS are installed on the same Windows Server? DNS issues with WDS”. Please see Domain Name System Protocol: Client Registration Issue, and how to enable or disable Secure Boot in Windows.
Note: There is no need to install the DNS server role alongside AD DS. This is because; you must not necessarily use the built-in DNS server. So I will be using a 3rd party DNS Server.
You may want to see How to configure Windows Deployment Services on Windows Server 2019, and Windows Deployment Services: How to setup and install WDS role.
Active Directory Domain Services (AD DS)
Active Directory Domain Services (AD DS) uses DNS as its domain controller location mechanism. When any of the principal Active Directory operations are performed, such as authentication, updating, or searching, computers use DNS to locate Active Directory domain controllers. In addition, domain controllers use DNS to locate each other.
The DNS Client service is included in all client and server versions of the Windows operating system and is running by default upon operating system installation. When you configure a TCP/IP network connection with the IP address of a DNS server, the DNS Client queries the DNS server to discover domain controllers and to resolve computer names to IP addresses.
See the following guides for other information. What are the differences between Universal, Global, and Domain Local Group Scopes, and Differences between Active Directory Lightweight Directory Services and Active Directory Domain Services.
What happens when WDS and DNS are together
When WDS and DNS run on the same server, they may introduce some problems. This happens when the DNS is installed first.
- The DNS service binds to all ports needed by WDS. The Default WDS port range is 64,000 to 65,000
- A specific patch can also cause this problem, watch out!
DNS with WDS
For how to set various DHCP options. Note: In my case, I do not have any issues since I am using Windows Server 2019. I have the option to obtain a dynamic port from Winsock as shown below!
But if you are running Windows Server 2008 or 2012 you will run into this issue.
Method 1: DNS issues with WDS
To resolve this, you will have to navigate to the WDS Server properties as shown below.
Click the Network settings tab,
Change the range from say 64100 to
64200 or 65000 as you wish. Note: You have to ensure other applications are not making use of these ports).
That is all you need to do 🙂
Method 2: DNS issues with WDS
You can also set this from the command line using WDSUTIL, see the syntax below.
wdsutil /set-Server /Transport /StartPort:65100 /EndPort:65200
If you are running Windows Server 2008 R2. You can also configure WDS to dynamically query WinSock for available ports instead of using a port range. This is done by setting the UdpPortPolicy value in the registry to 0.
You will find it in the path below and you need to restart WDS after changing the value.
Use the above method if both DNS and WDS are on the same server. I hope you found this blog post helpful. Please let me know in the comment session if you have any questions.
Here are some more guides: Domain Name System: How to create a DNS record, and DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names. Also see, Uninstall WDS: How to remove Windows Deployment Services role via the GUI and PowerShell.
I hope you found this blog post on “What happens when WDS and DNS are installed on the same Windows Server? DNS issues with WDS” helpful. Please let me know in the comment session if you have any questions.