Windows 10: Windows DNS Client Not Querying Specified DNS Server Without Connection Specific Suffix

We have 3 DCs, all running the DNS role. These servers hold the records for the domain itself but also "external" records using split-horizon DNS. IP Addresses for the servers are all static whereas the clients all have DHCP-assigned addresses.Currently, we are testing a new subdomain we'll call this timesheets.domain.co.uk, internal IP is 10.2.2.21, and this is hosted on DC04.domain.local. We also have remote.domain.co.uk which is also using split DNS, external DNS is in Cloudflare, internal record points to 10.2.2.102.If relevant, the DHCP server assigned domain.local as a DNS suffix. But w

:)

 

What is "Connection-specific DNS Suffix:" for and how to change it

I have a netgear DSL modem which has hardcoded into it a domain name "netgear.com". When I run IPCONFIG /all I see that the domain name from the modem is showing up in the "Connection-specific DNS Suffix:" field and the "DNS Suffix Search List. . . . .
. :" field as "netgear.com". The "netgear.com" info is also used in the "Tunnel adapter isatap.netgear.com:. Here is the rest of the adapters info:

Windows IP Configuration

Host Name . . . . . . . . . . . . .....: MARK-PC

Primary Dns Suffix . . . . . . . .:

Node Type . . . . . . . . . . . . ......: Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . : No

DNS Suffix Search List. . . . . . : netgear.com <<<<<<<<<<<<<<<<<<<<<<<<<What does this do?

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : netgear.com <<<<<<<<<<<<<<<<<<<<<<What does this do?

Description . . . . . . . . . . . ...................: Intel(R) I211 Gigabit Network Connection

Physical Address. . . . . . . . ................ : D0-50-99-85-E0-81

DHCP Enabled. . . . . . . ................ . . . : Yes

Autoconfiguration Enabled . . ...... . : Yes

IPv6 Address. . . . . . . . . . .................... : 2602:306:c48d:5ad9:78fd:cb55:887d:86c1(Preferred)

Temporary IPv6 Address. . . ........ . . : 2602:306:c48d:5ad9:1166:7e10:fca3:f698(Preferred)

Temporary IPv6 Address. . . . . . .......: 2602:306:c48d:5ad9:d018:4158:2f6d:be2f(Deprecated)

Link-local IPv6 Address . . . . ............ : fe80::78fd:cb55:887d:86c1%5(Preferred)

IPv4 Address. . . . . . . . . . . ....................: 192.168.0.173(Preferred)

Subnet Mask . . . . . . . . . . . ...................: 255.255.255.0

Lease Obtained. . . . . . . . . . ..................: Thursday, December 10, 2015 12:27:59 AM

Lease Expires . . . . . . . . . . ......................: Thursday, December 17, 2015 12:28:02 AM

Default Gateway . . . . . . . . . ..................: fe80::6e72:20ff:fe3e:c1aa%5

192.168.0.1

DHCP Server . . . . . . . . . . ....................... : 192.168.0.1

DHCPv6 IAID . . . . . . . . . . ....................... : 63983769

DHCPv6 Client DUID. . . . . . . . ...............: 00-01-00-01-1D-CC-29-77-D0-50-99-85-E0-83

DNS Servers . . . . . . . . . . . .......................: 2001:4860:4860::8888

2620:0:ccc::2

8.8.8.8

208.67.222.222

NetBIOS over Tcpip. . . . . . . ................... : Enabled

Tunnel adapter isatap.netgear.com: <<<<<<<<<<<<<<<<<<<<<<<<<<<What does this do and what is it?

Media State . . . . . . . . . . ................. : Media disconnected

Connection-specific DNS Suffix : netgear.com

Description . . . . . . . . . . .................. : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . ............: 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . ............: No

Autoconfiguration Enabled . . . . ..: Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

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

IPv6 Address. . . . . . . . . . .................. : 2001:0:5ef5:79fb:8b2:2d16:933a:9fea(Preferred)

Link-local IPv6 Address . . . . . .........: fe80::8b2:2d16:933a:9fea%7(Preferred)

Default Gateway . . . . . . . . . :

DHCPv6 IAID . . . . . . . . . . . ................: 134217728

DHCPv6 Client DUID. . . . . . . ........... : 00-01-00-01-1D-CC-29-77-D0-50-99-85-E0-83

NetBIOS over Tcpip. . . . . . . . ............: Disabled

The internet has been a little slower and I occasionally get DNS errors, but in general things are OK. Do I need to be concerned about the "netgear.com" entry? What would you recommend?

 

DNS Client

Log Name: System

Source: Microsoft-Windows-DNS-Client

Date: 16-04-2020 15:47:58

Event ID: 8020

Task Category: (1028)

Level: Warning

Keywords:

User: NETWORK SERVICE

Computer: Hostname

Description:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter

with settings:

Adapter Name : {XXXXXXXXXXX}

Host Name : Hostname

Primary Domain Suffix : Domain

DNS server list :

10.10.10.10

Sent update to server : <?>

IP Address(es) :

10.10.10.11

The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems
still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

System is not registering its A Record in DNS Zone. Above log generated post running ipconfig /registerdns.

System is connected over VPN.

 

AnyConnect down loaded from Microsoft no DNS server

Hi,

I have similar issues.

Using the standalone Cisco Anyconnect - it works fine.

Using the Anyconnect VPN from the Windows App store - is slightly different.

The latter does not adds the DNS server definitions, so you cannot see it with "ipconfig /all" - but: it still resolve DNS names on that DNS suffix which is on the connection specific DNS Suffix Search List.

My issue was, that the same DNS (on the VPN) should also resolve names which are not on that list.

I manages to add the DNS server IP addresses to the adapter, after the connection was established.

I used the Set-DnsClientServerAddress powershell command for that.

Hope that helps...