MIS_Nole
asked on
Forwarders list has invalid forwarder
We seem to be having issues on our network so I was running some tests and was wondering about this error message when I run "dcdiag /test:dns"
Any suggestions on what to do with this error?
Any suggestions on what to do with this error?
C:\Program Files\Support Tools>dcdiag /test:dns
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\RENEGADE
Starting test: Connectivity
......................... RENEGADE passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\RENEGADE
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : scbcinfo
Running enterprise tests on : xxxx.local
Starting test: DNS
Test results for domain controllers:
DC: renegade.xxxx.local
Domain: xxxx.local
TEST: Forwarders/Root hints (Forw)
Error: Forwarders list has invalid forwarder: 216.173.160.3 (<name unavailable>)
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 216.173.160.3 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 216.173.160.3
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: xxxx.local
renegade PASS PASS FAIL PASS PASS PASS n/a
......................... xxxx.local failed test DNS
ASKER
The 216.173.160.3 DNS server is our ISP's and we are having no issues reaching the Internet, but we are having issues elsewhere so I'm trying to eliminate possible errors that I find.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looks like we have resolved the other issues. A couple of stray DNS records pointing to an old DC looks to have caused the problem.
To comply with RFCs DNS servers should have a lookup zone for localhost, and should have a PTR record so you can resolve the name from the IP address.
There's little you can do if it's not yours and you have no control of it. Provided the DNS server responds it's nothing more than an aesthetic error and can be ignored.
Chris