DNS servers on Local Area Connection should include the loopback address, but not as the first entry.
Hello,
I'm getting these errors when I perform Best Pratice Analyser.
Title:
DNS: DNS servers on Local Area Connection should include the loopback address, but not as the first entry.
Severity:
Error
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
The network adapter Local Area Connection does not list the loopback IP address as a DNS server, or it is configured as the first entry.
Impact:
If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.
Resolution:
Configure adapter settings to add the loopback IP address to the list of DNS servers on all active interfaces, but not as the first server in the list.
I tried Resolution and added Loopback address as secondary server. Still same error.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=121980
Title:
DNS: More than one forwarding server should be configured.
Severity:
Warning
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
There is only one forwarder configured on the DNS server.
Impact:
The forwarder 4.2.2.2 is a single point of failure.
Resolution:
Configure additional forwarders on the DNS server.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=188788
Title:
DNS: Root hint server 198.32.64.12 must respond to NS queries for the root zone.
Severity:
Warning
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
The root hint server 198.32.64.12 is not responding.
Impact:
The DNS server might be unable to resolve external host names.
Resolution:
Validate network connectivity to root hint servers. Remove 198.32.64.12 from the list if it is unresponsive.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=188803
I'm getting these errors when I perform Best Pratice Analyser.
Title:
DNS: DNS servers on Local Area Connection should include the loopback address, but not as the first entry.
Severity:
Error
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
The network adapter Local Area Connection does not list the loopback IP address as a DNS server, or it is configured as the first entry.
Impact:
If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.
Resolution:
Configure adapter settings to add the loopback IP address to the list of DNS servers on all active interfaces, but not as the first server in the list.
I tried Resolution and added Loopback address as secondary server. Still same error.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=121980
Title:
DNS: More than one forwarding server should be configured.
Severity:
Warning
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
There is only one forwarder configured on the DNS server.
Impact:
The forwarder 4.2.2.2 is a single point of failure.
Resolution:
Configure additional forwarders on the DNS server.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=188788
Title:
DNS: Root hint server 198.32.64.12 must respond to NS queries for the root zone.
Severity:
Warning
Date:
9/21/2011 1:48:37 PM
Category:
Configuration
Issue:
The root hint server 198.32.64.12 is not responding.
Impact:
The DNS server might be unable to resolve external host names.
Resolution:
Validate network connectivity to root hint servers. Remove 198.32.64.12 from the list if it is unresponsive.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=188803
ASKER
Yes. On my DNS/DC Network Adapter it has Alternate DNS Server: 127.0.0.1
Then I'm afraid I do not know why it is erroneously telling you to do something you've already done :)
I'd just ignore that particular part of the report.
I'd just ignore that particular part of the report.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The scans checks the NIC / s and if IPv6 is installed it will check that as well.
If you do not have IPv6 DNS rolled out in your environment, simply change the option within IPV6 Properties to "Obtain DNS Server Address Automatically". Then run the scan again.
Also as mentioned by: abhijitwaikar.....Remove the loopback address.
If you do not have IPv6 DNS rolled out in your environment, simply change the option within IPV6 Properties to "Obtain DNS Server Address Automatically". Then run the scan again.
Also as mentioned by: abhijitwaikar.....Remove the loopback address.
Ideally, your Adapter should list 127.0.0.1 as the second DNS server. If your network interface does become broken, at least your domain controller can still resolve names. Naturally, it can't talk to anything else which kind of makes it useless, but hey, it's "best practice" :)
Does your TCP/IP on your Network Adapter looks similar to the following? (Note Alternate DNS Server).