[zirror]

I can't reproduce the "worst case" i.e. that if I ping "google.com" it gets first sent to "google.com.fritz.box". I'm on windows 10 and have a FRITZ!Box 7590.

If I ping "google.com" It just queries google.com If I ping a domain I have never visited it just does a query for that domain.

It only appends .fritz.box if I, e.g. only ping "google".

So maybe they fixed it? I also changed quite a lot of settings throughout the years.

[qilo]

There's a registry key

  HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient\AppendToMultiLabelName
  [default value - 0 (Do not Append Suffix)]

which resolver built into Windows (DNS Client) respects.

nslookup contains its own DNS resolver and does not rely on the resolver built into the operating system. The DNS (multi-label) query packets sent by the nslookup tool will append the domains listed in the suffix search order (or primary DNS suffix if the list is empty) irrespective of that registry key.

In summary, don't use nslookup to try to get insight into what actually happens when apps/services try to resolve names. ping is probably a better bet, at least it uses Windows resolver which honours the above registry key.

[r9295]

Cache perhaps?

[zirror]

No, I think windows by default only applies suffixes to Domains with 0 dots maybe?