DNS Problems SBS 2011

Topic

New Reply

So I am having issues with client PCs occasionally losing connection to the DC. In event viewer what appears is …
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.

On the SBS 2011 server I ran the BPA and two ERRORS show up.
DNS: a resource record points to an incorrect address
The internal network adapter is not configured to register in DNS

I have only one network connection, static IP, and the box is checked to register in DNS. This server is also the DNS/DHCP server and it only looks to itself for DNS.

I have run dcdiag /test:registerindns /domain:FQDN and it fails. The error message is

Starting test: RegisterInDNS
This domain controller cannot register domain controller Locator DNS
records. This is because it cannot locate a DNS server authoritative for
the zone XXXX. This is due to one of the following:

1. One or more DNS servers involved in the name resolution of the
snowflake name are not responding or contain incorrect delegation of the
DNS zones; or

2. The DNS server that this computer is configured with contains
incorrect root hints.

The list of such DNS servers might include the DNS servers with which
this computer is configured for name resolution and the DNS servers
responsible for the following zones: XXXX

Verify the correctness of the specified domain name and contact your
network/DNS administrator to fix the problem.

You can also manually add the records specified in the
%systemroot%system32confignetlogon.dns file.

……………………. XXXX failed test RegisterInDNS

Does anyone have any ideas to fix this problem? Thanks

Reply | Quote

Replies

If Windows cannot find an authoritative DNS server then something is not configured correctly.
In your DNS server is the local domain listed and is your server IP address in the range?
Is the server IP and DNS server IP the same – run “ipconfig /all” to check?

cheers, Paul

Reply | Quote

If Windows cannot find an authoritative DNS server then something is not configured correctly.
In your DNS server is the local domain listed and is your server IP address in the range?
Is the server IP and DNS server IP the same – run “ipconfig /all” to check?

cheers, Paul

Here
is ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SNOWFLAKE
Primary Dns Suffix . . . . . . . : catamountski.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : catamountski.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client)
Physical Address. . . . . . . . . : 78-2B-CB-43-0C-04
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a0a7:84e4:8ef0:b1b%10(Preferred)
Link-local IPv6 Address . . . . . : fe80::ed51:4617:45e0:30%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.254
DHCPv6 IAID . . . . . . . . . . . : 175647691
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-F9-A2-E4-78-2B-CB-43-0C-04

DNS Servers . . . . . . . . . . . : fe80::a0a7:84e4:8ef0:b1b%10
192.168.2.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{0C66DA26-90A4-4747-A0AC-A901CBBA2914}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

And yes the server is listed in DNS and is in the range

Reply | Quote

It seems the DNS doesn’t contain an entry for the server “snowflake”. Check the DNS entries and see if it exists?
You can create the entry manually to get around the issue, but in AD you need more than just the “name to IP” entry.
Have you changed the network adapter recently?

cheers, Paul

Reply | Quote

What I did was set an alternate DNS server to 8.8.8.8 until I realized that was probably a bad idea. I changed it back to only look to itself.

Reply | Quote

You need to set “root hints” to allow it to resolve external addresses, although I am not a fan of allowing your DC to have internet access.

cheers, Paul

Reply | Quote