State of DNS after Domain rename

Question

Hi all
Still learning DNS and want to add secondary DC
I initially set this up as a mydomain.local as I believed that was best practice. When researching SSL certificates I realised that it was now supposedly best practice to use mydomain.com. I did a Domain rename which was interesting and seemed to work reasonably
well.
2012 AD DC is :
IPv4: 192.168.1.105
Computer name: name
Full Computer name: name.mydomain.local
Domain name is: mydomain.com
2012 Server RDS is: (was secondary DNS when .local)
IPv4: 192.168.1.100
Computer name: remote
Computer name: remote.mydomain.com
Domain name is: mydomain.com
I want to install Secondary DNS to the RDS server or maybe a VM on it for redundancy but am concerned my DNS is possibly a little bit dodgy.
Only issues I have is sometimes from remote “mydomain.com” will resolve to 192.168.1.100 and don’t believe this should happen but may be wrong.
Every now and again from Remote Desktop which is on 192.168.1.100 (remote.mydomain.com) web sites won’t load and you need to refresh which will normally then resolve and load.
The only other issue is every now and again autodiscover will take a while to resolve and troubleshooting that implies a timeout. MS have looked at this and didn’t see any issues in my DNS however I think that was just due to the fact that it resolved eventually.
I have include some info ipconfig on 192.168.1.100 shows DNS 192.168.1.105.
NSLOOKUP
Name:    mydomain.com
Addresses:  192.168.1.100
          192.168.1.105
> remote.mydomain.com
Server:  UnKnown
Address:  192.168.1.105
Name:    remote.mydomain.com
Address:  192.168.1.100
> mydomain.local
Server:  UnKnown
Address:  192.168.1.105
Name:    mydomain.local
Address:  192.168.1.105
Pings from RDS
C:\Users\administrator.MD>ping mydomain.local
Pinging mydomain.local [192.168.1.105] with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
C:\Users\administrator.MD>ping mydomain.com
Pinging mydomain.com [192.168.1.100] with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
C:\Users\administrator.MD>ping mydomain.com
Pinging mydomain.com [192.168.1.105] with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
DCDIAG
         The DFS Replication Event Log.
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         A warning event occurred.  EventID: 0x800008A5
            Time Generated: 05/14/2014   01:30:50
            Event String:
            The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the
files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
            Additional Information:
            Volume: C:
            GUID: A3ABE3A7-A0E5-11E2-93E8-806E6F6E6963
            Recovery Steps
            1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
            2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
            wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="A3ABE3A7-A0E5-11E2-93E8-806E6F6E6963" call ResumeReplication
* Replication Latency Check
            DC=ForestDnsZones,DC=mydomain,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no
latency information (Win2K DC). 
            DC=DomainDnsZones,DC=mydomain,DC=com

Answer 1

Hi,
If I understand correctly, you have two computers with the following host names and IP addresses:
1. name (192.168.1.100)
2. remote (192.168.1.105)
The first server is a domain controller. The second server is a domain member server.
Your Active Directory domain was 'mydomain.local' and you changed this to 'mydomain.com'
DNS is installed on server #1.
To avoid confusion when talking about DNS and Active Directory, you can refer to mydomain.com as your Active Directory domain, which has users and groups in it and is hosted on a domain controller. You also have a DNS forward lookup zone mydomain.com that
is used to dynamically register computers that are members of the Active Directory domain. So - when referring to Active Directory - it is a domain but when referring to DNS it is a zone. These are two separate things that are linked.
The DNS zone should have at least three A (address) records:
mydomain.com (the root of the zone)
name.mydomain.com (the DC)
remote.mydomain.com (the member server)
You should see the .100 address for the first two and the .105 address for the third. Open up DNS Manager and view the zone to check it.
The pings you have listed in your post don't all make sense. Two of them are pinging the same FQDN but give different IP addresses (below):
What problem are you trying to solve?
-Greg