"SOME" devices can resolve the ALIAS (CNAME record) for a device, but not the REAL name (A record) - Why? How do I fix this?

I'm running the DNS server role on Windows Server 2012 R2 on a physical machine on my home network.
My AD is configured with a non-registered name - let's say it's "home.acme.ca" and the DNS server is configured to host that zone.  I also configured a 2nd zone in the DNS server called "myinf.acme.ca".  They both run on a physical
server with an IP of 192.168.1.10
The DHCP server on my Cable Modem is configured to hand out 192.168.1.10 as the only DNS server to every device on my network.  On my servers (with static IP addresses), 192.168.1.10 is configured as the only DNS server available for them. 
I took the DNS servers from my Cable Provider and configured a Forwarder on my server to send name resolution requests to them only if my DNS server can not answer the request - basically for any name resolution request that does not end with ".home.acme.ca"
or ".myinf.acme.ca"
The "home.acme.ca" zone is populated with 'A' records for all of the physical and virtual servers and PC's on my network.
The "myfin.acme.ca" zone is populated with 'CNAME' records that point directly to the 'A' record in "home.acme.ca" - for example, I have a serve named s000abc123ww.home.acme.ca with an 'A' record providing an IP address of 192.168.1.20 and
I created a 'CNAME' (alias) record named 'webserver.myinf.acme.ca' which points to the 'A' record 's000abc123ww.home.acme.ca'
2 of my 6 machines can resolve the alias but not the real name of the server!
.10 is the Domain Controller.  All of the other machines (except .98) are members of the home.acme.ca domain.
I attempted to ping 's000abc123ww.home.acme.ca' AND 'webserver.myinf.acme.ca' on the following 6 computers.  I used the fully qualified name in all cases.
4 of the below machines are able to resolve BOTH names.  The other 2 can resolve the Alias but not the real name!
I don't understand how this is possible, but I would like to fix it...!!!  Please help?
.10 - Server 2012 R2 (Physical) -  Hosts Active Directory and DNS.
.20 - Server 2012 R2 (Virtual)   -  Runs SQL Server
.21 - Server 2012 R2 (Virtual)   -  Runs Apache
.22 - Server 2012 R2 (Virtual)  -   Runs Apache.  This is the device I am trying to ping (s000abc123ww)
.98 - Windows 7 (Physical)
.99 - Windows 7  (Virtual)
.21 (which is configured nearly identically to .20 and .22) can resolve and ping the Alias, but not the real name.
.98 can also resolve and ping the Alias, but not the real name.
The rest of the machines can resolve and ping both the alias and the real name.
All of the Virtual Machines are running under Hyper-V on the .10 physical server.
All the devices are on the same subnet.
Thank in advance to anyone who can help me understand and correct this problem!
Jim

Hi,
CNAME resource records are recommended for use in the following scenarios:
• When a host that is specified in an A resource record in the
same zone needs to be renamed
• When a generic name for a well-known server, such as www, must resolve to a group of individual computers (each with individual A resource records) that provide the same
service, for example, a group of redundant Web servers
Therefore please try to create your CNNAM record in the same zone and try again.
The related KB:
Adding, Changing, and Deleting Resource Records
http://technet.microsoft.com/en-us/library/cc779020(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Maybe you are looking for