why windows 11 add a dns suffix to FQDN

Question

why windows 11 add a dns suffix to FQDN

BENSIALI Taryck 0

Hi all,

I've got a currious behaviour when I change my internet provider.

Windows 11 in IPV4 is adding the DNS suffix for every hostname, event if it's a FQDN (meaning including an TLD).

Why such behaviour that was not previouly the case (on my previous Internet provider)

Changing my internet proviter make me move from 10.x.x.x to 192.168.x.x

I've got a windows 10 computer on the same network that has the same DNS configuration has DNS resolution works fine.

When I ask for gmail.com IP using nslookup I get my local network IP address as DNS suffix has been added this way gmail.com.mydomain.com

Windows 11 & Windows 10 use the same DHCP. I don't know why but Windows 10 initiate both IPV4 & IPV6 (while DHCP support only IPV4) and Windows 11 initiate only IPV4.

If I revert to manual configuration the DNS suffix is clear so I loose all my local machine name.

Why this damn DNS suffix is added to a FQDN ?

1 answer

Your answer

Answer 1

Anonymous

Hello,

Please check the DNS suffix configuration on both IPv4 and IPv6 properties if they are enabled:

User's image

If you had enabled the option Append primary and connection specific DNS suffixes specifies that resolution for unqualified names that are used on this computer are limited to the domain suffixes of the primary suffix and all connection-specific suffixes. Connection-specific suffixes are configured in DNS suffix for this connection. The primary DNS suffix is configured via below setting:

User's image

I hope this helps! Please let me know if you need any further assistance.

Kind Regards,
Karlie Weng

If the Answer is helpful, please click "Accept Answer" and upvote it.

BENSIALI Taryck 0 Reputation points

2024-01-08T07:10:06.22+00:00

First of all thanks for this anwser.

My windows is in French and your screenshoot as a too low resolution or too high compression to read the english text (to try to translate into french). I guess that I could try expecting the same location.
However I don't know you you get this wifiproperties as in my windows version this is not "old" gray screen but new white screen and so the UI and the parameters do not correspond at all on you screenshoot.

It's seams to be a interesting solution but I can'f figure out where and how to apply it.

Could you tell me what you to to get this wifi propoeties screen ?
BENSIALI Taryck 0 Reputation points

2024-01-08T08:20:37.3233333+00:00

I guess I found the entry (that was not easy) :
Anonymous

2024-01-15T01:36:34.0366667+00:00

It‘s the setting. Also, please check the system configuration: All settings -> system -> about -> advanced system settings -> computer name tab -> change -> more
BENSIALI Taryck 0 Reputation points

2024-01-15T13:19:19.0466667+00:00

Hi, Thanks I do the checking. I'm on workgroup at home and no DSN suffix in computer/domain configuration.

MotoX80 36,401

If it helps you, here is what I see on my network. My default router configuration adds .Home as the DNS suffix. That doesn't show up in the GUI, but does from ipconfig. My router also registers local names. An nslookup query by either name or IP resolves names with the .Home suffix. Have you reviewed the settings in your router?


C:\Users\Admin>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Test10
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : home      <<<<<<=========

Ethernet adapter Ethernet0:

   Connection-specific DNS Suffix  . : home           <<<<<<=========
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-DA-C7-A5
   DHCP Enabled. . . . . . . . . . . : Yes            <<<<<<=========
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2600:4040:f087:b300:102a:b095:711d:e173(Preferred)
   IPv6 Address. . . . . . . . . . . : fd00::6ceb:7d24:7706:995b(Preferred)
   Temporary IPv6 Address. . . . . . : 2600:4040:f087:b300:d817:d72c:628f:dca5(Preferred)
   Temporary IPv6 Address. . . . . . : fd00::d817:d72c:628f:dca5(Preferred)
   Link-local IPv6 Address . . . . . : fe80::6eb9:5fb2:81fc:7ac4%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, January 15, 2024 8:45:36 AM
   Lease Expires . . . . . . . . . . : Tuesday, January 16, 2024 8:45:35 AM
   Default Gateway . . . . . . . . . : fe80::1a1b:ebff:fe85:288a%12
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 352324649
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-2D-EE-26-00-0C-29-DA-C7-A5
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\Admin>nslookup blackhole
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1

Name:    blackhole.home
Address:  192.168.1.2


C:\Users\Admin>nslookup 192.168.1.2
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1

Name:    Blackhole.home
Address:  192.168.1.2


C:\Users\Admin>

MotoX80 36,401

I should also note that this does not affect internet name lookup.

C:\Users\Admin>nslookup www.yahoo.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1

Non-authoritative answer:
Name:    me-ycpi-cf-www.g06.yahoodns.net
Addresses:  2001:4998:1c:800::1001
          2001:4998:1c:800::1000
          69.147.82.61
          69.147.82.60
Aliases:  www.yahoo.com

User's image

M.H.H de Haas 0 Reputation points

2025-02-20T13:23:44.2266667+00:00

Hi I have exact same issue is that all public FQDN are being prepended with the DNS suffix list which is in fact configured, so there is a lot of delay as the list is pretty long. Windows 11 client should not try to prepend FQDN, instead is should only prepend when there is something locally resolvable. The only thing i noticed is that the primary DNS suffix is not configured on the DNS of this computer.

Share via

why windows 11 add a dns suffix to FQDN

1 answer

Your answer