{"items":[{"children":[{"children":[{"properties":{"category":["tailscale","network","local","dns"],"content":[{"html":"

We recently got a new-internet, and with it a strange error returned I thought I fixed long ago.

\n

I have a subdomain of inhji.de which resolves to a address in my local network. This way I can have an domain like jellyfin.nas.inhji.de with a valid certificate and have it resolve to a local address.

\n

When I set up the new modem, I realized that the default address space is 192.168.2.0/24, whereas before it was 192.168.1.0/24. This meant I needed to setup all devices again with new ip addresses.

\n

\"Nginx\nNginx Proxy Manager Hosts

\n

So I updated the Hosts on my Nginx, and thought everything would just work. And it did. But only sometimes. Sometimes the names would just not resolve.

\n

\"DNS\nAdGuard DNS Rewrites

\n

So I started looking for solutions:

\n\n

After a few days, I suddenly remembered that it could have something to do with my tailscale network. I quickly checked the settings and found the problem.

\n

\"Tailscale

\n

In tailscale I had added a custom nameserver to resolve my 'local domain' with my local DNS server. That entry still had an address in my old ip range. Which made all lookups fail. No idea why it worked sometimes, but after I added the correct address of my DNS server here, the problem was solved!

","value":"We recently got a new-internet, and with it a strange error returned I thought I fixed long ago.\nI have a subdomain of inhji.de which resolves to a address in my local network. This way I can have an domain like jellyfin.nas.inhji.de with a valid certificate and have it resolve to a local address.\nWhen I set up the new modem, I realized that the default address space is 192.168.2.0/24, whereas before it was 192.168.1.0/24. This meant I needed to setup all devices again with new ip addresses.\nNginx Hosts\nNginx Proxy Manager Hosts\nSo I updated the Hosts on my Nginx, and thought everything would just work. And it did. But only sometimes. Sometimes the names would just not resolve.\nDNS Rewrites\nAdGuard DNS Rewrites\nSo I started looking for solutions:\n\nI added a DNS Rewrite in my AdGuardHome, which serves as my DNS and DHCP Server\nI double-checked if my modem was not still running a DHCP server\n\nAfter a few days, I suddenly remembered that it could have something to do with my tailscale network. I quickly checked the settings and found the problem.\nTailscale Nameservers\nIn tailscale I had added a custom nameserver to resolve my 'local domain' with my local DNS server. That entry still had an address in my old ip range. Which made all lookups fail. No idea why it worked sometimes, but after I added the correct address of my DNS server here, the problem was solved!"}],"name":["This one weird trick fixed my DNS (clickbait)"],"published":["2026-04-26T23:04:18+02:00"],"summary":["We recently got a new-internet, and with it a strange error returned I thought I fixed long ago.\nI have a subdomain of inhji.de which resolves to a address in my local network. This way I can have an domain like jellyfin.nas.inhji.de with a valid certificate and have it resolve to a local address.\nWhen I set up the new modem, I realized that the default address space is 192.168.2.0/24, whereas before it was 192.168.1.0/24. This meant I needed to setup all devices again with new ip addresses.\nNginx Hosts\nNginx Proxy Manager Hosts\nSo I updated the Hosts on my Nginx, and thought everything would just work. And it did. But only sometimes. Sometimes the names would just not resolve.\nDNS Rewrites\nAdGuard DNS Rewrites\nSo I started looking for solutions:\n\nI added a DNS Rewrite in my AdGuardHome, which serves as my DNS and DHCP Server\nI double-checked if my modem was not still running a DHCP server\n\nAfter a few days, I suddenly remembered that it could have something to do with my tailscale network. I quickly checked the settings and found the problem.\nTailscale Nameservers\nIn tailscale I had added a custom nameserver to resolve my 'local domain' with my local DNS server. That entry still had an address in my old ip range. Which made all lookups fail. No idea why it worked sometimes, but after I added the correct address of my DNS server here, the problem was solved!"],"updated":["2026-04-26T23:04:18+02:00"]},"type":["h-entry"]},{"id":"main-sidebar","properties":{"name":["Jonathan"],"nickname":["inhji"],"note":["Jacked in since 1996."],"url":["https://inhji.de/"]},"type":["h-card"]}],"properties":{},"type":["h-screen"]}],"properties":{},"type":["h-screen"]}],"rel-urls":{"https://aperture.p3k.io/microsub/171":{"rels":["microsub"]},"https://bandcamp.com/inhji":{"rels":["me"],"text":"\n Bandcamp\n "},"https://chaos.social/@inhji":{"rels":["me"],"text":"\n Fediverse\n "},"https://codeberg.org/inhji":{"rels":["me"],"text":"\n Codeberg\n "},"https://git.inhji.de/inhji":{"rels":["me"],"text":"\n Git Server\n "},"https://github.com/inhji":{"rels":["me"]},"https://indieauth.com/auth":{"rels":["authorization_endpoint"]},"https://inhji.de/":{"rels":["me"],"text":"\n Jonathan\n "},"https://inhji.de/assets/css/app-1f12478d5a9377a7a35f1a48326d8f64.css?vsn=d":{"rels":["stylesheet"]},"https://listenbrainz.org/user/inhji":{"rels":["me"],"text":"\n ListenBrainz\n "},"https://musicbrainz.org/user/inhji":{"rels":["me"],"text":"\n MusicBrainz\n "},"https://tokens.indieauth.com/token":{"rels":["token_endpoint"]}},"rels":{"authorization_endpoint":["https://indieauth.com/auth"],"me":["https://github.com/inhji","https://inhji.de/","https://bandcamp.com/inhji","https://listenbrainz.org/user/inhji","https://codeberg.org/inhji","https://chaos.social/@inhji","https://musicbrainz.org/user/inhji","https://git.inhji.de/inhji"],"microsub":["https://aperture.p3k.io/microsub/171"],"stylesheet":["https://inhji.de/assets/css/app-1f12478d5a9377a7a35f1a48326d8f64.css?vsn=d"],"token_endpoint":["https://tokens.indieauth.com/token"]}}