The logged errors below are from 2012 R2 Server, just a single Server in a small medical office. It replaced a 2003 Server and AD was migrated to this machine. The old Server is gone. This Server appears to function normally but the
fix for these BPA errors that show up in the Server Manager eludes me. There is only 1 NIC configured and the Servers IP is specified as the primary DNS and the Router's IP is specified as the secondary DNS. I've done it that way for years
on many Servers so I can't understand what is happening here. The Server is doing DHCP for the work stations and DHCP is turned off in the Router.
Title:
DNS: DNS servers on NIC1 should include the loopback address, but not as the first entry.
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The network adapter NIC1 does not list the local server as a DNS server; or it is configured as the first DNS server on this adapter.
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.
http://go.microsoft.com/fwlink/?LinkId=188760
Title:
DNS: Zone TrustAnchors secondary servers must respond to queries for the zone.
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
None of the secondary servers configured for zone TrustAnchors are responding.
Impact:
Secondary servers will fail DNS queries for the zone TrustAnchors.
Resolution
Validate secondary servers for zone TrustAnchors.
http://go.microsoft.com/fwlink/?LinkId=188791
Title:
DNS: The DNS server 192.168.1.1 on NIC1 must resolve Global Catalog resource records for the domain controller
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name _ldap._tcp.gc._msdcs.BH.local.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating a Global Catalog will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to configure DNS servers that can resolve the name _ldap._tcp.gc._msdcs.BH.local.
http://go.microsoft.com/fwlink/?LinkId=121970
Title:
DNS: The DNS server 192.168.1.1 on NIC1 must resolve Kerberos resource records for the domain controller
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name _kerberos._tcp.BH.local.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating a Kerberos Key Distribution Center(KDC) will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to configure DNS servers that can resolve the name _kerberos._tcp.BH.local.
http://go.microsoft.com/fwlink/?LinkId=121967
Title:
DNS: The DNS server 192.168.1.1 on NIC1 must resolve LDAP resource records for the domain controller
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name _ldap._tcp.BH.local.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating domain controllers will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to configure DNS servers that can resolve the name _ldap._tcp.BH.local.
http://go.microsoft.com/fwlink/?LinkId=121972
Title:
DNS: The DNS server 192.168.1.1 on the NIC1 must resolve PDC resource records for the domain controller
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name _ldap._tcp.pdc._msdcs.BH.local.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating a Primary Domain Controller will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to configure DNS servers that can resolve the name _ldap._tcp.pdc._msdcs.BH.local.
http://go.microsoft.com/fwlink/?LinkId=121971
Title:
DNS: The DNS server 192.168.1.1 on NIC1 must resolve names in the forest root domain name zone
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name for the start of authority (SOA) record of the zone hosting the computer's forest root domain name.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating domain controllers will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to remove all invalid or unresponsive DNS servers.
http://go.microsoft.com/fwlink/?LinkId=121974
Title:
DNS: The DNS server 192.168.1.1 on NIC1 must resolve names in the primary DNS domain zone
Severity
Error
Date:
3/22/2016 4:27:28 PM
Category:
Configuration
Problem:
The DNS server 192.168.1.1 on NIC1 did not successfully resolve the name for the start of authority (SOA) record of the zone hosting the computer's primary DNS domain name.
Impact:
Active Directory Domain Services (AD DS) operations that depend on locating domain controllers will fail.
Resolution
Click Start, click Network, click Network and Sharing Center, and then click Change adapter settings to remove or replace all invalid or unresponsive DNS servers.
http://go.microsoft.com/fwlink/?LinkId=121973
