this post was submitted on 22 Apr 2025
12 points (100.0% liked)

Homelab

914 readers
2 users here now

Rules

founded 2 years ago
MODERATORS
 

I just set up a local DNS server in my LAN with a custom domain "jellyfin.local". I set my router up to advertise this DNS server via DHCP. This seems to work for my Linux laptop. But neither my windows machine nor my android phone use my local DNS server.

I believe the issue may be that my router is crappy, and while it does announce my DNS server correctly for IPv4, I am unable to stop it from announcing some other DNS server for IPv6. I believe that this may confuse my Windows and Android devices, which probably prioritise DNS via IPv6, and hence use the wrong DNS server.

I could now buy a better router. But before I do that, I wanted to know if someone else successfully uses a local DNS server with Windows devices, Android devices, Smart TVs, and so on. Specifically, with a properly configured DHCP server, will all modern devices use the correct DNS server?

Update

Thanks for all the informative comments! I have now resorted to using a global DNS record (jellyfin.mydomain.de) to point to my local server. That seems to work and the easiest option.

top 10 comments
sorted by: hot top controversial new old
[–] Blaster_M@lemmy.world 6 points 2 months ago* (last edited 2 months ago) (1 children)

I use a pfSense router and using the DNS Resolver, I get local dns just fine (and it relays DoH or DoT for even more security), but you can install OPNSense (or even pfSense CE) on any computer with at least two ethernets for the same functionality.

Android is a rough one, because often it doesn't use local dns and prefers to use google dns directly unless you manually specify a dns.

[–] Sibbo@sopuli.xyz 1 points 2 months ago

Thanks! I now went with a global DNS record. It's very simple, given that I already have a domain.

[–] MangoPenguin@lemmy.blahaj.zone 3 points 2 months ago (1 children)

Make sure your devices/browsers don't have "private DNS" or "secure DNS" or something like that enabled, it will bypass your DNS server.

[–] Sibbo@sopuli.xyz 2 points 2 months ago (1 children)

Thanks! It's really disappointing that devices nowadays come with these restrictions. This way, guests can't easily use local services on my network.

[–] MangoPenguin@lemmy.blahaj.zone 2 points 2 months ago (1 children)

Its a feature! If you're on public WiFi or something it's handy to be able to route your DNS securely somewhere else.

[–] Sibbo@sopuli.xyz 1 points 2 months ago

Yeah I understand. Maybe someone will at some point invent a standard to have this kind of local DNS securely as well.

[–] sanzky@beehaw.org 3 points 2 months ago

i mostly have no issues. I even block all traffic on port 53 on my router with the exception of a school provided laptop that has DNS enforced through MDM.

all other devices listen on my DNS as far as I can tell.

[–] taaz@biglemmowski.win 2 points 2 months ago* (last edited 2 months ago) (2 children)

.local is special, it's for mDNS/zeroconf.

https://en.wikipedia.org/wiki/.local

Try using .lan or .home

[–] sik0fewl@lemmy.ca 3 points 2 months ago

Or .internal if you never want to have to change it again.

[–] Sibbo@sopuli.xyz 1 points 2 months ago

Actually, I tried .home and it also fails ... Well, I went with a global DNS record now.