DNS resolving incorrectly

[Alis_Klar]

Hi,

Our AD linked internal DNS randomly resolves names incorrectly. It only ever effects hosts allocated an IP by DHCP.

Amazingly we have had this issue for many years and lived with it as it only really hurts us when we need to Remote Desktop into a client that has its IP from DHCP.

Most of the time names resolve correctly.

[kili]

Are you sure you have the correct DNS details set under "scope options" (015 DNS Domain Name) and DNS server IP's listed under 006 DNS Servers

[Alis_Klar]

006 is correct, 015 is empty

We used to have 2 AD linked DNS servers which were both DC's. I have demoted one and removed the DNS role from it. I have just removed also an old DNS server entry in the DNS servers TCP/IP properties of the local area Connection under network connections.

Will update thread if this works!

[glennda]

Are the DHCP servers set to automatically update the dns even if the client doesn't request it?

if not then its worth it as clients don't always request it.

[kili]

006 is correct, 015 is empty

We used to have 2 AD linked DNS servers which were both DC's. I have demoted one and removed the DNS role from it. I have just removed also an old DNS server entry in the DNS servers TCP/IP properties of the local area Connection under network connections.

Will update thread if this works!

Add an entry for 015, the string value should be the domain name for your domain ( Not the forest root domain name if your part of a WAN)

[Alis_Klar]

@kili will try your suggestion later as i wish to implement one change at a time so i can see what fixed it.

[Alis_Klar]

DHCP-DNS-update.PNG
@glennda this setting?

[kili]

@kili will try your suggestion later as i wish to implement one change at a time so i can see what fixed it.

Good idea, but having a 015 entry would be a normal set-up and should be included in your DHCP scope options by default