Windows 10: CNAME with different domain name on Windows DNS server

Hi there,Hope there is someone can help me on this case. I am facing a problem when create a CNAME in forward zone on our internal DNS.Our primary domain is abc.com and have a developing domain abc-dev.com. Both domain are existing in external DNS server, but abc.com only existing on internal DNS server.Our developer is requesting to have a CNAME, uat.abc-dev.com, and can only be resolved internally. I tried to create a new zone in internal DNS server which is abc-dev.com and added a CNAME uat. in there. But this caused all other existing abc-dev.com URLs cannot be resolved internally. Because

:)

 

DNS Servers

I run a DNS server locally, so when a domain is already cached, I get it back almost instantly, otherwise it responds as fast as the first server in my list (75.75.75.75 in my case.)

 

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:

Code:

nslookup ccccccc-serv3.ccccccc
Server:  zzzzzzzz.bbb.aaaaaaaaa.netAddress:  10.250.9.1

Code:

Non-authoritative answer:Name:    ccccccc-serv3.ccccccc.bbb.aaaaaaaaa.netAddress:  10.13.1.9

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

Code:

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?

 

Implementing a new CIFS server - Once CNAME of \\files\ is changed to the new server from the old windows 10 users cannot logon but windows 7 users can

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that some of the users are facing issue while accessing files over the new CIFS server.



Since you have reached the consumer Windows Forums, let me point you in the right direction where you can get adequate support for the issue that you are facing. I would suggest you to post your query on

TechNet forums.



Additional information:

• SMB file server share access is unsuccessful through DNS CNAME
  alias
  
• How to troubleshoot DNS issues when there
  could be multiple issues on the user"s network
  

Regards,

Prakhar Khare

Microsoft Community – Moderator