Tuesday, November 17, 2026

It was DNS

My ISP provides a mini router, which does some interesting things.

It provides a .lan domain, and various DHCP computer names get into the local DNS automatically.

This works quite well, except for my Windows 11 box, for some reason it's not wanting to resolve the .lan correctly. 

After a long and meandering and fruitless conversation with ChatGPT, it became apparent that my ISP advertises IPv6 DNS as the upstream ISP DNS, but the supplied router answers IPv4 which includes local .lan stuff. My Windows 11 box is dutifully doing IPv6, so it sends the .lan query to the ISP DNS which knows nothing about .lan.

After a bunch more wrestling with ChatGPT (I was losing), I finally became annoyed and just told it to stop messing around and tell me how to get my .lan working.

The answer:

Add-DnsClientNrptRule -Namespace ".lan" -NameServers "192.168.40.1"


So basically this tells W11 to query the .lan namespace at this particular local nameserver. Anything else goes to the IPv6 DNS upstream.


No comments: