Fix DNS Query Error: Service Location (SRV) Record Issue

Graphic illustrating the three types of DNS queries: Recursive, Iterative, and Non-recursive, with brief descriptions for each type.

A DNS query (also known as a DNS request) is a demand for information sent from a user’s computer (DNS client) to a DNS server. When prompted with the following error as shown below. In this guide, I will show you how to fix “the following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DS) for domain: Error code 0x0000232B RCODE_NAME_ERROR”. Please see the following guides: DNS: Unable to register a client to Domain, How to find disabled Active Directory User accounts, how to fix WinRM cannot process the request: The following error occurred while using Kerberos authentication, cannot find the computer.

Computer properties window displaying an error message indicating that the Active Directory Domain Controller for the domain 'technet.local' could not be contacted.

This is a DNS issue, no doubt! Use this guide for the different types of DNS records. When you search on the internet, you may find conflicting tips. In my environment, here are some tips I followed to resolve this issue.

Please see these exciting articles: Domain Name System: How to create a DNS record. How to fix DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names. And how to enable God Mode via PowerShell, CLI and GUI.

Resolve Error for “DNS was queried for the service location (SRV)”

Here are  my recommendations below

1: Ensure the client(s) IP parameters (preferred DNS Server) set on the client machine points to the DNS points to internal DNS servers as DNS servers. See a similar error “The following errors occurred attempting to join the domain: The specified domain either does not exist or could not be contacted“.

As you can see, it was pointing to a wrong IP Address (gateway).

Error message indicating that an Active Directory Domain Controller for the domain 'techdirect.local' cannot be contacted, with details about DNS records and IP addresses.

Therefore, I will have to corrected the information.

Screenshot of the Ethernet Properties window displaying Internet Protocol Version 4 (TCP/IPv4) settings, including fields for IP address, subnet mask, default gateway, preferred DNS server, and alternate DNS server, with highlighted sections for editing.

2: Ensure the DNS server has the right IP address of itself populated for all zones and records. A similar idea was used in resolving this issue “How to fix nslookup unknown: cannot find non-existent domain“.

After ensuring the above two recommendations are met, flush the DNS cache and registered the DNS again using the command below on the DNS server and restart the DNS and netlogon service. You can optionally restart your DNS server. for other DNS troubleshooting parameters, see this link.

			
ipconfig /registerdns
net stop netlogon
net start netlogon

Command Prompt window displaying an error message indicating that 'ipconfig' is not recognized as a command, with the command 'ipconfig /registerdns' highlighted.

Now, you should e able to join your device to the domain as shown below. For how to set up a domain, see the following link. Also for how to add a second DC, see the following link. For how to join a PC to a Domain, see the following link.

Computer Properties window displaying computer name and domain settings, with a notification confirming membership in the 'techdirect.local' domain.

Note: You will be prompted to restart your device as shown below. Proceed and have it restarted.

A pop-up notification from Microsoft Windows indicating the need to restart the computer to apply changes, with options to 'Restart Now' or 'Restart Later'.

I hope you found this blog post helpful on how to fix the following error occurred when DNS was queried for the service location”. If you have any questions, please let me know in the comment session.