That matches my observation on Windows 11. Looking at wireshark while doing the resolution I see the following: Normal queries never use the the suffix. nslookup does, which the resolver answers with NXDOMAIN
Fritz box allows you to capture traffic towards the ISP too and there I never see such a suffix query in either case. So I assume the fritz resolver directly responds to those.
That does not really match the behavior described in the OP but I would be very surprised if the behavior described there wouldn't have lead to a big outcry much earlier.
Can we be absolutely sure the "normal resolution mode" is always used? I'm happy to accept that impact might be not as severe as stated, but to me it's very scary that a simple nslookup for google.com returns the IP address of fritz.box.
Re:All Fritz Box modems have been hijacked
by freitasm on Sunday April 21, 2024 @03:33PM
(#40108517)
I replaced a Fritz.Box many years ago and a Windows-based laptop I have here still tries a lookup to frit.box every few seconds.
It's Monday morning here and I just started the laptop. It's still doing lookups on fritz.box.
Does anyone know where and why Windows is requesting this?
So this shouldn't really be an issue for most people, but highlights once again that you should never ever use a domain in your infrastructure that you do not own or at the very least use one of the suffixes from https://www.rfc-editor.org/rfc/rfc6762#appendix-G