DNS issues on windows server

Question

DNS issues on windows server

dss ds 531

Running DCDIAG to teat health of domain fails at "DNS lookup fails"

I have 2 VM in (both DC, as one migrated to the other, in host-only environment, but no forwarders listed..) nor conditional.

AD/DNS is on same VM so dns is
Ipv4 Properties : 172.16.245.130 (Primary)
DNS : 172.16.245.130 (1st DC)
Alternative DNS : 172.16.245.132. (2nd DC)

Host A records are entered correctly and IP, via nslookup, resolves fine but domain name does not

What else could be the issue?

Ping resolves fine between servers via ip and domain name.

Rafael da Rocha 5,251 Reputation points

2022-07-17T02:48:24.93+00:00

each dc should point to the other as primary and itself as secondary

dss ds 531

done, but still fails

When running DCDIAG /test:dns i get:

           TEST: Forwarders/Root hints (Forw)  
              Error: Both root hints and forwarders are not configured or  
              broken. Please make sure at least one of them works.  

     Summary of test results for DNS servers used by the above domain  
     controllers:  

        DNS server: 128.63.2.53 (h.root-servers.net.)  
           1 test failure on this DNS server  
           PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN

S server 128.63.2.53

This is expected on internal only network?

last line:

                                       Auth Basc Forw Del  Dyn  RReg Ext  
       _________________________________________________________________  
       Domain: skypub.com.au  
          mail                         PASS PASS FAIL PASS PASS PASS n/a  

    ......................... skypub.com.au failed test DNS

Rafael da Rocha 5,251 Reputation points

2022-07-17T03:59:23.097+00:00

If forwarders and root hints are disabled or inaccessible, the error on dcdiag is expected. shouldn't be a problem for local resolution

ping to skypub.com.au resolves to one of the DCs?

If you change the server to the second DC, does nslookup resolve?

DNS console on both servers shows consistent data indicating correct replication?
dss ds 531 Reputation points

2022-07-17T11:06:02.5+00:00

ping to skypub.com.au resolves correctly IP

2nd DC nslookup resolves.

I think the problem is 1st DC, because i get no dns time out on 2nd,, only on 1st...

No DNS replication errors.

Screenshot is from 1st DC

DC1: mail.skypub.com.au
DC2: mail2.skypub.com.au

DC 2 (nslookup) no issues.

(command prompt vs dns manager)

Bottom screenshot started from DNS Manager: Top left is command prompt, with slightly different results. (DC1)

Sorry about IP's... Had to switch to Bridge mode to get external access. in/out.

Answer accepted by question author

2 additional answers

Your answer

Rafael da Rocha 5,251 Reputation points

2022-07-17T02:48:24.93+00:00

each dc should point to the other as primary and itself as secondary
dss ds 531 Reputation points

2022-07-17T03:16:53.413+00:00

done, but still fails

When running DCDIAG /test:dns i get:

TEST: Forwarders/Root hints (Forw) Error: Both root hints and forwarders are not configured or broken. Please make sure at least one of them works. Summary of test results for DNS servers used by the above domain controllers: DNS server: 128.63.2.53 (h.root-servers.net.) 1 test failure on this DNS server PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN

S server 128.63.2.53

This is expected on internal only network?

last line:

Auth Basc Forw Del Dyn RReg Ext _________________________________________________________________ Domain: skypub.com.au mail PASS PASS FAIL PASS PASS PASS n/a ......................... skypub.com.au failed test DNS
Rafael da Rocha 5,251 Reputation points

2022-07-17T03:59:23.097+00:00

If forwarders and root hints are disabled or inaccessible, the error on dcdiag is expected. shouldn't be a problem for local resolution

ping to skypub.com.au resolves to one of the DCs?

If you change the server to the second DC, does nslookup resolve?

DNS console on both servers shows consistent data indicating correct replication?
dss ds 531 Reputation points

2022-07-17T11:06:02.5+00:00

ping to skypub.com.au resolves correctly IP

2nd DC nslookup resolves.

I think the problem is 1st DC, because i get no dns time out on 2nd,, only on 1st...

No DNS replication errors.

Screenshot is from 1st DC

DC1: mail.skypub.com.au
DC2: mail2.skypub.com.au

DC 2 (nslookup) no issues.

(command prompt vs dns manager)

Bottom screenshot started from DNS Manager: Top left is command prompt, with slightly different results. (DC1)

Sorry about IP's... Had to switch to Bridge mode to get external access. in/out.

Answer 1

Anonymous

On mail I'd add server's own static ip address (192.168.1.106) listed for DNS, then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

(not sure why the addressing is different than in original post)

The dcdiag renders limited info from the event logs for last 24 hrs so it difficult to get a complete picture but I'd try to cleanup any system and DFS Replication event log errors before trying to add again.

If problems persist then put up a new set of files to look at.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Anonymous

2022-07-18T12:00:45.693+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Anonymous

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt

then put unzipped text files up on OneDrive and share a link.

Answer 3

dss ds 531

link : https://1drv.ms/u/s!AqTRavx4TSm4ccohWcQPw5VKtAQ?e=4TLw8E

Share via

DNS issues on windows server

2 additional answers

Your answer