Question : HOST A Records in DNS MGMT

We currently have 3 host A records pointing to FQDN of ACME.com

2 of the host A records point to internal domain controllers and 1 pointing to our web hosting public ip address.

This is how the environment was setup before I got here so I'm not sure why they have 3 ip addresses pointing to the same FQDN.  So when I do an NSLOOKUP of ACME.com I get back a response of the ip addresses that are listed in the host A records.

So here is the issue....when people who are outside of our network type in acme.com on there browser is resolves to www.acme.com which is what should happen.  But users that are in our network tries to go to acme.com it doesn't resolve to www.acme.com. We want it to resolve to www.acme.com just like they were outside of our network.

I was wondering how we can get that to resolve on the dns server.  I thought adding a CNAME record  would work but that does seem to help.  

Anyone have any ideas....maybe I'm doing the CNAME entry incorrectly?

Answer : HOST A Records in DNS MGMT

The two DC entries are used for group policies, DFS, etc, etc. It's why AD really needs to hang onto it.

The third entry, if that one points to your web site, should be removed. These are the "same as parent folder" Host (A) records in your DNS console.

Chris