Windows 10: Additional DNS suffixes not checked if there's a dot in the partial domain name

Windows has always had the "Append these DNS suffixes" list in network adapter (IPv4) properties.

However, there's a difference in behavior between nslookup.exe and windows itself.


I wish I could find a workaround for this...


I have a forest of domains, names masked for security, length kept approximately intact.


External domain, registered, used for e-mail etc.: aaaaaaaaa.net


Internal top level AD domain: bbb.aaaaaaaaa.net.

(Having bbb there allows for split DNS, base domain forwarded to external server, only bbb and subdomains DNS-hosted internally in AD.)


Child domains: ccccccc.bbb.aaaaaaaaa.net, dddddddd.bbb.aaaaaaaaa.net, etc.


A server name may look like, for example, ccccccc-serv3.ccccccc.bbb.aaaaaaaaa.net


To avoid a lot of typing, I decided to try and add "bbb.aaaaaaaaa.net" to the DNS suffix list, but it turns out to be useless.


It works in nslookup.exe:


nslookup ccccccc-serv3.ccccccc


Server: zzzzzzzz.bbb.aaaaaaaaa.net

Address: 10.250.9.1



Non-authoritative answer:

Name: ccccccc-serv3.ccccccc.bbb.aaaaaaaaa.net

Address: 10.13.1.9


But that's the only place where it works, if there is a period in the name being looked up.


ping ccccccc-serv3.ccccccc


Ping request could not find host ccccccc-serv3.ccccccc. Please check the name and try again.


Same when trying to connect to a share, trying to connect with RDP, etc.


Why can't Windows' built in network support treat this the way nslookup does?

:)

 

windows10 dns resolution name problem - hostname.other not add the suffix dns

Hello Roberto,

Make sure that the Append primary and connection specific DNS suffixes
option is enabled in the Advanced TCP/IP Settings window of your network adapter. This option specifies that resolution for unqualified names that are used on your computer is limited to the domain suffixes of the primary suffix and all connection-specific
suffixes. For more information, you may refer to the following link:
Configure a Connection-Specific DNS Name. (Note: These steps are also applicable for Windows 10 machines.)

You might also be experiencing this issue because of DNS Devolution. This is applicable to computers that are in an Active Directory environment. For more information, you may refer to the following link:

DNS Devolution.

For more advanced troubleshooting, we recommend that you also post this concern in the

Windows 10 IT Pro section of the Microsoft TechNet forums. TechNet Forums is a community for IT professionals and advanced users.

If you need further assistance, please do not hesitate to post a reply.

If you think this was helpful, do not hesitate to "mark it as answer" to help those who are facing the same problem.

 

windows10 dns resolution name problem - hostname.other not add the suffix dns

Hi ,

I have windows10 clinent and if I open a cmd and type :

ping examplehostname

the dns function correctly , paste the suffix and resolve the nome to ip address.

The problem I have when I try to ping examplehostname.pub . In this case on windows 10 not paste the suffix dns but in windows7 function correctly add the suffix. If I type ping examplehostname.pub.my.domain.xxthe
dns resolve the name .

Please there is a anyone that can help me, please!

thanks a lot

Roberto

 

After updating to the Windows 10 April 2018 build (1803) the DNS Suffix Search List behavior seems to have changed

After being updated to the Windows 10 April 2018 build (1803) the DNS Suffix Search List behavior seems to have changed and is no longer a combination of my Primary DNS Suffix (my Windows domain name) followed by my Connection-specific DNS Suffix (previous
default Windows behavior).

This appears to be related to Windows 10 April 2018 build (1803) change in honoring DHCP option 119. All previous versions of the Windows DHCP client ignored option 119 but it now appears build 1803 honors this setting.

Can anyone confirm?