DNS resolution issues?

Host A sounds fine. So, I am thinking it might be the SRV records you are missing. This article may resolve your issue.

https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.html

If not can you post the Event log error associated with these warnings.

[WARNING] Cannot find a primary authoritative DNS server for the name
            'Serv1.Domain.'. [WSAEADDRNOTAVAIL           ]
            The name 'Serv1.Domain.' may not be registered in DNS.

I have run dc, and net diag several times over the last 2 days, and get no more events logged. so until i get an event log under dns i cannot post it.

However I do have these: 4 events
(Under Directory service)
NTDS Replication
Category: Backup
Event ID 2089

Why am i getting what looks like a Mac address in the ping, and ipconfig?

Those are IPv6 addresses, we'll have to get used to them very shortly.  In the meantime if you go into the properties of your network adapters you can probably move IPv6 and just leave the normal IPv4.

I tried forced replication and received this error on Serv4.
No errors on Serv1.

"Those are IPv6 addresses, we'll have to get used to them very shortly.  In the meantime if you go into the properties of your network adapters you can probably move IPv6 and just leave the normal IPv4."

Have disabled ipv6 in network properties, and still getting same results?

Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	4004
Date:		7/29/2008
Time:		9:36:44 AM
User:		N/A
Computer:	Serv4
Description:
The DNS server was unable to complete directory service enumeration of zone ultreyasolutionsgroup.com.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 
 
--------------------------------------------------
 
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	4015
Date:		7/29/2008
Time:		9:36:44 AM
User:		N/A
Computer:	Serv4
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 00 00 00               Q...    

Select allOpen in new window

"It looks like the records for Serv1 are missing from one or both the DNS servers, have you gone thorugh both to check for forward and reverse lookups for each servers?  Try running ipconfig /registerdns on Serv1 to try and re-register it's IP info with the DNS servers."

I have done these steps and all info is there, on both Serv1 and Serv4.
I have registered 3 times in the last 2 days.

With IPver 6 disabled, go and flush the DNS resolver cache, that was a good catch:

At the command prompt:
IPconfig /flushDNS
______________________________________________________________
Errors 4015 and 4004 can usually be ignored.
It means DNS was started before AD service. They will go away if this was upon loadup. I just helped someone with these errors.
https://www.experts-exchange.com/questions/22901131/THE-DNS-server-has-encountered-a-critical-error-from-the-Active-Directory.html

If the problem goes unresolved, you may wish to look in your reverse lookup zone.
https://www.experts-exchange.com/questions/21213433/EVENT-ID-4004-4015.html
____________________________________________________________________
Problems with DNS can result from many forms. Since things work for a couple days and stop, you might be running into network problems. Some networking issues are tough to diagnose because the server thinks it's happy, and therefore no errors. There are symptoms you should look for rather than errors in event logs for these items.

First let's explain some of the intermittant problems with a server:
1) There are issues with some service packs on the server. SP1 has a known error that shuts down because of MTU channels are offset. It can shut down any of a variety of domain services, like AD, DNS, DHCP, or WSUS  and communications can appear intermittant. So, it is important to tell us what service pack you are using.

2) The spanning tree protocol has an option called portfast. Portfast is an option that skips the discovery of a route and just sends your packets through the switches. XP boxes need portfast due to the hyped up need for a quicker connection. Older boxes are a little more patient when sending packets out. So, they don't time out as easily. So, let's say you have 30 boxes and 10 are Win 2000 boxes. If your swtiches have slowed traffic to a crawl, the 10 Win2000 boxes may be able to log on while the XP boxes are timed out.

3) Further issues with intermittant comms can, I think are Cisco specific. Managed Cisco routers and Switches have a quirk. If not on the same mode of operation, they will have intermittant comms. Let's say you have a switch on 100 Mb/Full duplex and a router set to auto negotiate traffic. You might think these would work, but they don't. Both either have to be set to auto or to 100 Mb/Full duplex.

Please ask me to elaborate if you think this might be a networking issue:
______________________________________________________________________________

When I see 4015 and 4004 errors, this usually tells me you have a multihomed domain controller and both SRV records are in DNS.

IP v 6 was enabled, I have since disabled it in the network properties. However ipconfig /all still show the adapter(s) and the ip6 address.

Error 4004 just started today and as much as I'm dinking with the servers, does not really surprise me. However you did mention a multihomed DC, I did change from one network adapter to the second built in adapter for communication reasons. Unfortunately I disabled  NIC1 Prior to enabling NIC2. So there is only 1 current active NIC on the DC.

All of my servers are up to date with Service pack2. I was receiving communication errors prior to the last update and reboot of the servers. Indicating to me that this has been going on for a bit. An issue was present prior to the last update. and An issue is present now. I can only speculate that these issues are related.
How can I determine the MTU's on an interface? Both NIC's are 1gb ports.

Elaborate on the :both SRV records are in DNS" Are you referring to the NIC address(es)¿

dcdiag /v
results

===========================================
Serv1
===========================================
C:\>DCdiag /v
 
Domain Controller Diagnosis
 
Performing initial setup:
   * Verifying that the local machine tsdsqlsvr, is a DC.
   * Connecting to directory service on server tsdsqlsvr.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 2 DC(s). Testing 1 of them.
   Done gathering initial info.
 
Doing initial required tests
 
   Testing server: Default-First-Site-Name\TSDSQLSVR
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... TSDSQLSVR passed test Connectivity
 
Doing primary tests
 
   Testing server: Default-First-Site-Name\TSDSQLSVR
      Starting test: Replications
         * Replications Check
         * Replication Latency Check
         * Replication Site Latency Check
         ......................... TSDSQLSVR passed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=ForestDnsZones,DC=tsd,DC=ultreya
            (NDNC,Version 2)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=tsd,DC=ultreya
            (NDNC,Version 2)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=tsd,DC=ultreya
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=tsd,DC=ultreya
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=tsd,DC=ultreya
            (Domain,Version 2)
         ......................... TSDSQLSVR passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... TSDSQLSVR passed test NetLogons
      Starting test: Advertising
         The DC TSDSQLSVR is advertising itself as a DC and having a DS.
         The DC TSDSQLSVR is advertising as an LDAP server
         The DC TSDSQLSVR is advertising as having a writeable directory
         The DC TSDSQLSVR is advertising as a Key Distribution Center
         The DC TSDSQLSVR is advertising as a time server
         The DS TSDSQLSVR is advertising as a GC.
         ......................... TSDSQLSVR passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default
-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Domain Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default
-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role PDC Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Rid Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Ser
vers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         ......................... TSDSQLSVR passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2109 to 1073741823
         * tsdsqlsvr.tsd.ultreya is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1109 to 1608
         * rIDPreviousAllocationPool is 1109 to 1608
         * rIDNextRID: 1213
         ......................... TSDSQLSVR passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/tsdsqlsvr.tsd.ultreya/tsd.ultreya
         * SPN found :LDAP/tsdsqlsvr.tsd.ultreya
         * SPN found :LDAP/TSDSQLSVR
         * SPN found :LDAP/tsdsqlsvr.tsd.ultreya/TSD
         * SPN found :LDAP/6b50621a-bbc7-47e1-a9fa-17beb32d73da._msdcs.tsd.ultre
ya
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/6b50621a-bbc7-47e1-a9
fa-17beb32d73da/tsd.ultreya
         * SPN found :HOST/tsdsqlsvr.tsd.ultreya/tsd.ultreya
         * SPN found :HOST/tsdsqlsvr.tsd.ultreya
         * SPN found :HOST/TSDSQLSVR
         * SPN found :HOST/tsdsqlsvr.tsd.ultreya/TSD
         * SPN found :GC/tsdsqlsvr.tsd.ultreya/tsd.ultreya
         ......................... TSDSQLSVR passed test MachineAccount
      Starting test: Services
         * Checking Service: Dnscache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: RpcSs
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... TSDSQLSVR passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         TSDSQLSVR is in domain DC=tsd,DC=ultreya
         Checking for CN=TSDSQLSVR,OU=Domain Controllers,DC=tsd,DC=ultreya in do
main DC=tsd,DC=ultreya on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya in domain CN=Configuration
,DC=tsd,DC=ultreya on 1 servers
            Object is up-to-date on all servers.
         ......................... TSDSQLSVR passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... TSDSQLSVR passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         ......................... TSDSQLSVR passed test frsevent
      Starting test: kccevent
         * The KCC Event log test
         Found no KCC errors in Directory Service Event log in the last 15 minut
es.
         ......................... TSDSQLSVR passed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... TSDSQLSVR passed test systemlog
      Test omitted by user request: VerifyReplicas
      Starting test: VerifyReferences
         The system object reference (serverReference)
         CN=TSDSQLSVR,OU=Domain Controllers,DC=tsd,DC=ultreya and backlink on
         CN=TSDSQLSVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
ation,DC=tsd,DC=ultreya
         are correct.
         The system object reference (frsComputerReferenceBL)
         CN=TSDSQLSVR,CN=Domain System Volume (SYSVOL share),CN=File Replication
 Service,CN=System,DC=tsd,DC=ultreya
         and backlink on CN=TSDSQLSVR,OU=Domain Controllers,DC=tsd,DC=ultreya
         are correct.
         The system object reference (serverReferenceBL)
         CN=TSDSQLSVR,CN=Domain System Volume (SYSVOL share),CN=File Replication
 Service,CN=System,DC=tsd,DC=ultreya
         and backlink on
         CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-First-Site-Name,CN=
Sites,CN=Configuration,DC=tsd,DC=ultreya
         are correct.
         ......................... TSDSQLSVR passed test VerifyReferences
      Test omitted by user request: VerifyEnterpriseReferences
 
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
 
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
 
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
 
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
 
   Running partition tests on : tsd
      Starting test: CrossRefValidation
         ......................... tsd passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... tsd passed test CheckSDRefDom
 
   Running enterprise tests on : tsd.ultreya
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope
         provided by the command line arguments provided.
         ......................... tsd.ultreya passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         PDC Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         Time Server Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         Preferred Time Server Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         KDC Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         ......................... tsd.ultreya passed test FsmoCheck
 
 
===========================================
Serv4
===========================================
 
 
D:\>dcdiag /v
 
Domain Controller Diagnosis
 
Performing initial setup:
   * Verifying that the local machine tsd2domsrv, is a DC.
   * Connecting to directory service on server tsd2domsrv.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 2 DC(s). Testing 1 of them.
   Done gathering initial info.
 
Doing initial required tests
 
   Testing server: Default-First-Site-Name\TSD2DOMSRV
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... TSD2DOMSRV passed test Connectivity
 
Doing primary tests
 
   Testing server: Default-First-Site-Name\TSD2DOMSRV
      Starting test: Replications
         * Replications Check
         * Replication Latency Check
         * Replication Site Latency Check
         ......................... TSD2DOMSRV passed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=ForestDnsZones,DC=tsd,DC=ultreya
            (NDNC,Version 2)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=tsd,DC=ultreya
            (NDNC,Version 2)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=tsd,DC=ultreya
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=tsd,DC=ultreya
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=tsd,DC=ultreya
            (Domain,Version 2)
         ......................... TSD2DOMSRV passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... TSD2DOMSRV passed test NetLogons
      Starting test: Advertising
         The DC TSD2DOMSRV is advertising itself as a DC and having a DS.
         The DC TSD2DOMSRV is advertising as an LDAP server
         The DC TSD2DOMSRV is advertising as having a writeable directory
         The DC TSD2DOMSRV is advertising as a Key Distribution Center
         The DC TSD2DOMSRV is advertising as a time server
         The DS TSD2DOMSRV is advertising as a GC.
         ......................... TSD2DOMSRV passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default
-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Domain Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default
-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role PDC Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Rid Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=TSDSQLSVR,CN=Ser
vers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya
         ......................... TSD2DOMSRV passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2109 to 1073741823
         * tsdsqlsvr.tsd.ultreya is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1609 to 2108
         * rIDPreviousAllocationPool is 1609 to 2108
         * rIDNextRID: 1674
         ......................... TSD2DOMSRV passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/tsd2domsrv.tsd.ultreya/tsd.ultreya
         * SPN found :LDAP/tsd2domsrv.tsd.ultreya
         * SPN found :LDAP/TSD2DOMSRV
         * SPN found :LDAP/tsd2domsrv.tsd.ultreya/TSD
         * SPN found :LDAP/d3977313-efc9-4fe2-872d-ddf52da84a9f._msdcs.tsd.ultre
ya
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d3977313-efc9-4fe2-87
2d-ddf52da84a9f/tsd.ultreya
         * SPN found :HOST/tsd2domsrv.tsd.ultreya/tsd.ultreya
         * SPN found :HOST/tsd2domsrv.tsd.ultreya
         * SPN found :HOST/TSD2DOMSRV
         * SPN found :HOST/tsd2domsrv.tsd.ultreya/TSD
         * SPN found :GC/tsd2domsrv.tsd.ultreya/tsd.ultreya
         ......................... TSD2DOMSRV passed test MachineAccount
      Starting test: Services
         * Checking Service: Dnscache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: RpcSs
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... TSD2DOMSRV passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         TSD2DOMSRV is in domain DC=tsd,DC=ultreya
         Checking for CN=TSD2DOMSRV,OU=Domain Controllers,DC=tsd,DC=ultreya in d
omain DC=tsd,DC=ultreya on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=TSD2DOMSRV,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=tsd,DC=ultreya in domain CN=Configuratio
n,DC=tsd,DC=ultreya on 1 servers
            Object is up-to-date on all servers.
         ......................... TSD2DOMSRV passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... TSD2DOMSRV passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         ......................... TSD2DOMSRV passed test frsevent
      Starting test: kccevent
         * The KCC Event log test
         Found no KCC errors in Directory Service Event log in the last 15 minut
es.
         ......................... TSD2DOMSRV passed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... TSD2DOMSRV passed test systemlog
      Test omitted by user request: VerifyReplicas
      Starting test: VerifyReferences
         The system object reference (serverReference)
         CN=TSD2DOMSRV,OU=Domain Controllers,DC=tsd,DC=ultreya and backlink on
         CN=TSD2DOMSRV,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=tsd,DC=ultreya
         are correct.
         The system object reference (frsComputerReferenceBL)
         CN=TSD2DOMSRV,CN=Domain System Volume (SYSVOL share),CN=File Replicatio
n Service,CN=System,DC=tsd,DC=ultreya
         and backlink on CN=TSD2DOMSRV,OU=Domain Controllers,DC=tsd,DC=ultreya
         are correct.
         The system object reference (serverReferenceBL)
         CN=TSD2DOMSRV,CN=Domain System Volume (SYSVOL share),CN=File Replicatio
n Service,CN=System,DC=tsd,DC=ultreya
         and backlink on
         CN=NTDS Settings,CN=TSD2DOMSRV,CN=Servers,CN=Default-First-Site-Name,CN
=Sites,CN=Configuration,DC=tsd,DC=ultreya
         are correct.
         ......................... TSD2DOMSRV passed test VerifyReferences
      Test omitted by user request: VerifyEnterpriseReferences
 
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
 
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
 
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
 
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
 
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
 
   Running partition tests on : tsd
      Starting test: CrossRefValidation
         ......................... tsd passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... tsd passed test CheckSDRefDom
 
   Running enterprise tests on : tsd.ultreya
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope
         provided by the command line arguments provided.
         ......................... tsd.ultreya passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\tsd2domsrv.tsd.ultreya
         Locator Flags: 0xe00001fc
         PDC Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         Time Server Name: \\tsd2domsrv.tsd.ultreya
         Locator Flags: 0xe00001fc
         Preferred Time Server Name: \\tsdsqlsvr.tsd.ultreya
         Locator Flags: 0xe00003fd
         KDC Name: \\tsd2domsrv.tsd.ultreya
         Locator Flags: 0xe00001fc
         ......................... tsd.ultreya passed test FsmoCheck
 
D:\Documents and Settings\wfullerton>

Select allOpen in new window

As for reverse lookup.

Both reverse lookup zones match. All SN are identical. I can add a user in AD on Serv4 and the user (eventually) shows up on Serv1. I can delete the user on Serv1, and (eventually) the user is removed from Serv4. I can create a share and use it as well. I have turned off Serv4, and had multiple machines inside the network ...
1 ipconfig /flushdns
2 ipconfig /release
3 shutdown /f
Manually start after 5 minutes, and everything works well. Shares, new users, DHCP, Mail and all other network functions are running from Serv1. I cannot shutdown Serv1 and test Serv4 this same way due to downtime.

So, you disabled NIC 1 and went to NIC 2. I think this is your issue.

Go into NIC 2's configuration. Naviagate to Local Area connection Properties>>highlight TCP/IP and select the properties button>>Select the advanced button and go to the DNS tab

Ensure that these are checked or enabled on server 1:
Step 1:
Append primary and connection specific DNS suffixes
    Append parent suffixes of the primary DNS suffix
and
Step 2:
Register this connections address in DNS

Step 3)
Now go to the command Prompt and type:
Net Stop Netlogon
Net Start Netlogon
_____________________________________________________________
Why do this:
You disabled NIC 1 and enabled NIC 2 and gave NIC2 same IP. I am thinking the SRV records of NIC2 are not on the correct IP address.

To resolve we are allowing you to dynamically reregister the SRV (Service records) in DNS. The first step above allows you to append the Domain Name as a suffix to the DNS record. Then the next part allows you to dynamically register your DNS setting. On Step 3, restarting the netlogon service registers your SRV records with DNS on that NIC.

Now, this article will not pertain to you because you have the latest SP and this problem was fixed in SP1. However, you did stop NIC 1 and enable NIC 2. That potentially caused the same problem even with SP2 installed.
http://support.microsoft.com/?id=832478

Pay more attention to the cause of the error that states:
""This problem occurs because if you clear the Register this connection's address in DNS check box under Advanced TCP/IP Settings for one of the network interfaces and then restart the Netlogon service, the Netlogon service ignores the settings. The client computer that tries to connect to one of the multihomed interfaces for the domain controller may have no valid IP route. ""

So, there may not be a valid IP route to NIC 2's SRV records. These may be registered on the IP address you had prior to changing it to NIC 2's IP address to match NIC1. That IP would probably be 0.0.0.0, (for a disabled NIC). Once you changed NIC2's IP to the same as disabled NIC 1's IP, then the route changed and may have left the SRV record on the wrong IP.

Restarting the server also restarted the Netlogon service. So, your SRV records may be straight, now.

Step 1:
Append primary and connection specific DNS suffixes
    Append parent suffixes of the primary DNS suffix

This was already set/done.

Reloaded the NIC drivers, rebooted with no change or same results. However new event recorded.

dcdiag failures on Serv1:
 
      Starting test: systemlog
         An Error Event occured.  EventID: 0xC0001B70
            Time Generated: 07/30/2008   16:58:19
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x0000168E
            Time Generated: 07/30/2008   17:11:48
            Event String: The dynamic registration of the DNS record
         An Error Event occured.  EventID: 0xC000000F
            Time Generated: 07/30/2008   17:23:06
            Event String: No adapter is configured to be the default
         An Error Event occured.  EventID: 0xC0011080
            Time Generated: 07/30/2008   17:23:11
            Event String: WINS encountered a database error. This may or
         An Error Event occured.  EventID: 0xC00110DE
            Time Generated: 07/30/2008   17:23:11
            Event String: WINS could not start due to a missing or corrupt
         An Error Event occured.  EventID: 0xC0001B70
            Time Generated: 07/30/2008   17:23:32
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0001B6E
            Time Generated: 07/30/2008   17:25:55
            (Event String could not be retrieved)
         ......................... TSDSQLSVR failed test systemlog

netdiag Failures on Serv1:

    [WARNING] The net card 'RAS Async Adapter' may not be working because it has
 not received any packets.
    [WARNING] The net card 'Microsoft Tun Miniport Adapter' may not be working.

DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '0.0.0.0'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.

As for the error. I have already done these steps with no change.

Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	6702
Date:		7/30/2008
Time:		5:12:29 PM
User:		N/A
Computer:	TSDSQLSVR
Description:
DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code. 
 
If this DNS server does not have any DS-integrated peers, then this error 
should be ignored. 
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it. 
 
To ensure proper replication: 
1) Find this server's Active Directory replication partners that run the DNS server. 
2) Open DnsManager and connect in turn to each of the replication partners. 
3) On each server, check the host (A record) registration for THIS server. 
4) Delete any A records that do NOT correspond to IP addresses of this server. 
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.) 
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00               ´...    

Select allOpen in new window

IP v 6 was enabled, I have since disabled it in the network properties.

OOPs, disabling IP6 may not cut the mustard.
https://www.experts-exchange.com/questions/22523749/DNS-FAILURE.html

Also check your time on DNS. See if you are synched up with the other servers.

Also check your time on DNS. See if you are synched up with the other servers.

I can tell you now the time doesn't synch. The time server for the domain was Serv1, and since communication issues, clients are now getting time from Serv4.

I still think this has to do with the xfer from NIC 1 to NIC 2. You might consider deleting the SRV records and restarting the netlogon service to re-register these records in DNS. Also delete the Host A, and run IPconfig /registerDNS from the command prompt. After that Flush your DNS cach by running IPconfig /flushdns at the command prompt.

I think your server is trying to go to the wrong NIC to communicate with itself.

I concur with your assessment. However since these issues were present prior to the NIC change over, I am not as optimistic as you on this resolution. I will however do these tasks, and inform you on the results. I have a couple of questions in this regard though.

1.Can I delete the reverse lookup zone and re create it with no issues? Or would there be consequences?
2.What about the DNS SOA record, Can I delete this as well as the A record(s)? and would there be consequences?

1.Can I delete the reverse lookup zone and re create it with no issues? Or would there be consequences?
2.What about the DNS SOA record, Can I delete this as well as the A record(s)? and would there be consequences?

I think there would be consequences on those: The SOA record is registered by RID and defines the primary DNS server. The reverse lookup will slow outside traffic, but you might be able to rebuild the reverse lookup zone without issues. This will create a considerable amount of traffic when replicating your DNS info to other DNS servers, depending upon your replication scope.  

I went through and reviewed what we haved done. When you pinged the server it replied came back with a IPver 6 address. This might be the address that is listed in DNS records. Therefore it may have been the primary issue.

You know, before we begin messing with the SRV records you might try a simple command utility to see if it fixes your issue. With IPv 6 disabled, your server should see the IPv4 address and start registering that in your DNS by running this at the command prompt:
Netdiag /fix:DNS
http://support.microsoft.com/kb/556002

I have gone through every dns record in reguards to the DC's (Both). All IP information contained within them are correct. I have disabled IP6 in network properties. I still get an IP6 IP when I ping Serv1 by name. Below is the current output from their respective commands from Serv1. This has got to be something simple, however evasive. I feel I'm running out of time. I realize the tombstone time has been upped to 180 days under SP2, however I can't be sure on how long this has been going on. I do not get to look over servers on a daily or even weekly basis.

Does anyone know the reprocutions to deleting the Reverse lookup zones, and recreating them? Or, Deleting the DNS A records, including the SOA, and recreating them? Should I seize roles before attempting? Since this is a SQL server as well, will this be the worst idea in the history of bad ideas? How do I get rid of the "Tunnel adapter Teredo Tunneling Pseudo-Interface:"?

It does show the DNS server '0.0.0.0'

C:\Program Files\Support Tools>ping tsdsqlsvr
 
Pinging Serv4 [fe80::1%1] from fe80::1%1 with 32 bytes of data:
 
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
 
Ping statistics for fe80::1%1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
=================================================================
netdiag /fix
=================================================================
 
Netcard queries test . . . . . . . : Passed
    [WARNING] The net card 'RAS Async Adapter' may not be working because it has
 not received any packets.
    [WARNING] The net card 'Microsoft Tun Miniport Adapter' may not be working.
 
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
    [FATAL] Failed to fix: DC DNS entry tsd.ultreya. re-registeration on DNS ser
ver '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.tsd.ultreya. re-registeration
 on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.tsd.ultreya. re-re
gisteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.tsd.ultreya. re-reg
isteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.gc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.7f007cdd-c16e-4738-9377-0e94a
310e10a.domains._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' fai
led.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry 6b50621a-bbc7-47e1-a9fa-17beb32d73da._ms
dcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.tsd.ultreya. re
-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.dc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.tsd.ultreya. re-reg
isteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.dc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.tsd.ultreya. re-registeration o
n DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.
tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._udp.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.tsd.ultreya. re-registerat
ion on 
C:\Program Files\Support Tools>ping tsdsqlsvr
 
Pinging Serv4 [fe80::1%1] from fe80::1%1 with 32 bytes of data:
 
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
 
Ping statistics for fe80::1%1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
=================================================================
netdiag /fix
=================================================================
 
Netcard queries test . . . . . . . : Passed
    [WARNING] The net card 'RAS Async Adapter' may not be working because it has
 not received any packets.
    [WARNING] The net card 'Microsoft Tun Miniport Adapter' may not be working.
 
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
    [FATAL] Failed to fix: DC DNS entry tsd.ultreya. re-registeration on DNS ser
ver '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.tsd.ultreya. re-registeration
 on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.tsd.ultreya. re-re
gisteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.tsd.ultreya. re-reg
isteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.gc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.7f007cdd-c16e-4738-9377-0e94a
310e10a.domains._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' fai
led.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry 6b50621a-bbc7-47e1-a9fa-17beb32d73da._ms
dcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.tsd.ultreya. re
-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.dc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.tsd.ultreya. re-reg
isteration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.dc._msdcs.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._
sites.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.tsd.ultreya. re-registeration o
n DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.
tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kerberos._udp.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.tsd.ultreya. re-registerat
ion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.tsd.ultreya. re-registerat
ion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.ForestDnsZones.tsd.ultreya. r
e-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.ForestDnsZones.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.DomainDnsZones.tsd.ultreya. r
e-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.DomainDnsZones.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.tsd.ultreya. re-registeration
on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry ForestDnsZones.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry DomainDnsZones.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '0.0.0.0'.
    [FATAL] No DNS servers have the DNS records for this DC registered.
 
=================================================================
netdiag
=================================================================
 
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '0.0.0.0'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.
 
=================================================================
dcdiag
=================================================================
 
All passed
 
=================================================================
nslookup
=================================================================
 
recognizes server and IP as version 4
.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.tsd.ultreya. re-registerat
ion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.ForestDnsZones.tsd.ultreya. r
e-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.ForestDnsZones.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.DomainDnsZones.tsd.ultreya. r
e-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._site
s.DomainDnsZones.tsd.ultreya. re-registeration on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.tsd.ultreya. re-registeration
on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry ForestDnsZones.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Failed to fix: DC DNS entry DomainDnsZones.tsd.ultreya. re-registera
tion on DNS server '0.0.0.0' failed.
DNS Error code: 0x00002741
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '0.0.0.0'.
    [FATAL] No DNS servers have the DNS records for this DC registered.
 
=================================================================
netdiag
=================================================================
 
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [WSAEADDRNOTAVAIL           ]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'tsdsqlsvr.tsd.ultreya.'. [ERROR_TIMEOUT]
            The name 'tsdsqlsvr.tsd.ultreya.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '0.0.0.0'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.
 
=================================================================
dcdiag
=================================================================
 
All passed
 
=================================================================
nslookup
=================================================================
 
recognizes server and IP as version 4
 
=================================================================
ipconfig /all
=================================================================
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : tsdsqlsvr
   Primary Dns Suffix  . . . . . . . : tsd.ultreya
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : tsd.ultreya
 
Ethernet adapter Local Area Connection 2:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection w
ith I/O Acceleration #2
   Physical Address. . . . . . . . . : 00-15-17-0F-7F-01
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.2.30
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1
   DNS Servers . . . . . . . . . . . : 192.168.2.30
                                       192.168.2.50
 
Tunnel adapter Teredo Tunneling Pseudo-Interface:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Disabled
 
Tunnel adapter Automatic Tunneling Pseudo-Interface:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : C0-A8-02-1E
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.30%2
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Select allOpen in new window

Awarding 50 points to Zenith63 since he saw the IP issue. To bad no follow up from him.
Thanks to ChiefIT for the follow through.