troubleshooting Question
DNS Server Errors - Zone TrustAnchors secondard, Name Servers, Forwarders
jackbenson
asked on
asked on
Hi,
I am getting a lot of errors/warnings in the Server 2012 Best Practice Tool for my DNS server.
I have 2 sites:
Local Network: 192.168.16.0
-- DC/DNS Server1 (win 2012): 192.168.16.11 / fc;1234:5678:9abc::11
-- DC/DNS Server2 (win 2012): 192.168.16.21 / fc;1234:5678:9abc::21
Azure: 10.4.2.0
-- DC/DNS Server3 (win 2012): 10.4.2.5
The errors/warnings i am getting (and there alot):
Errors:
(1) Zone TrustAnchors secondard servers must respond to queries for the zone
(2) At least one name server in the list of root hiints must respond to queries for the root zone.
(3) At Least one DNS server on the list of forwarders must respond to DNS queries
Warnings:
Zone TrustAnchones secondard server 192.168.16.21 should respond to queries for the zone
Zone TrustAnchones secondard server 10.4.2.5 should respond to queries for the zone
(plus i have this for the following IP addresses: fc00:1234:5678:9abc:a42d:8
Root hint server 192.33.4.12 must respond to NS queries for the root zone
(i have this for every route hint)
Forwarding server 8.8.4.4 should respond to DNS queries.
(Also the same for 8.8.4.4
All my computers on my network are confiremd to use 192.168.16.11/192.168.16.2
When i go into DNS manager - into Root Hints, press edit - it fails to validate the root hint.
what am i doing wrong - the error message i get is:A timeout occured during validation.
i beleive i only have a primary DNS zone that is replicated to my 3 DNS servers.
Forward Lookup Zones
_msdcs.DomainName.Local
DomainName.Local
Reverse Lookup Zones:
0.0.0.1.8.7.6.54.3.2.1.0.0
16.168.192.in-addr.arp (ipv5 local network range)
2.4.10.in-addr.arpa (azure network range)
c.b.a.9.8.7.6.5.4.3.2.1.0.
can anyone help me out?
many thanks
jack
I am getting a lot of errors/warnings in the Server 2012 Best Practice Tool for my DNS server.
I have 2 sites:
Local Network: 192.168.16.0
-- DC/DNS Server1 (win 2012): 192.168.16.11 / fc;1234:5678:9abc::11
-- DC/DNS Server2 (win 2012): 192.168.16.21 / fc;1234:5678:9abc::21
Azure: 10.4.2.0
-- DC/DNS Server3 (win 2012): 10.4.2.5
The errors/warnings i am getting (and there alot):
Errors:
(1) Zone TrustAnchors secondard servers must respond to queries for the zone
(2) At least one name server in the list of root hiints must respond to queries for the root zone.
(3) At Least one DNS server on the list of forwarders must respond to DNS queries
Warnings:
Zone TrustAnchones secondard server 192.168.16.21 should respond to queries for the zone
Zone TrustAnchones secondard server 10.4.2.5 should respond to queries for the zone
(plus i have this for the following IP addresses: fc00:1234:5678:9abc:a42d:8
Root hint server 192.33.4.12 must respond to NS queries for the root zone
(i have this for every route hint)
Forwarding server 8.8.4.4 should respond to DNS queries.
(Also the same for 8.8.4.4
All my computers on my network are confiremd to use 192.168.16.11/192.168.16.2
When i go into DNS manager - into Root Hints, press edit - it fails to validate the root hint.
what am i doing wrong - the error message i get is:A timeout occured during validation.
i beleive i only have a primary DNS zone that is replicated to my 3 DNS servers.
Forward Lookup Zones
_msdcs.DomainName.Local
DomainName.Local
Reverse Lookup Zones:
0.0.0.1.8.7.6.54.3.2.1.0.0
16.168.192.in-addr.arp (ipv5 local network range)
2.4.10.in-addr.arpa (azure network range)
c.b.a.9.8.7.6.5.4.3.2.1.0.
can anyone help me out?
many thanks
jack
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 7 Comments.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.