Selfhosted

39921 readers

304 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Issue with local DNS and Android (feddit.it)

submitted 2 months ago by Shimitar@feddit.it to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

I have a home network with an internal DNS resolver. I have some subdomains (public) that maps to a real world IP address, and maps to the home server private address when inside home.

In short, i use unbound and have added some local-data entries so that when at home, those subdomains points to 192.168.x.y instead.

All works perfectly fine from Windows and from Linux PCs.

Android, instead, doesnt work.

With dynamic DHCP allocation on android, the names cannot be resolved (ping will fail...) from the android devices. With specific global DNS servers (like dns.adguard.com) of course will always resolve to the public IP.

The only solution i found is to disable DHCP for the Wifi on android and set a static IP with the 192.168.x.y as DNS server, in this case it will work.

But why? Aynbody has any hints?

It's like Android has some kind of DNS binding protection enabled by default, but i cannot find any information at all.

you are viewing a single comment's thread
view the rest of the comments

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

Strange, have you checked the interface info on Android to see what DNS info it's getting from the DHCP server?

Also check that it's getting an IP on the 192.168.x.y network, and not some other subnet if the AP is doing funky things.

[–] Shimitar@feddit.it 2 points 2 months ago (1 children)

It's blatantly ignoring the DNS i set via DHCP it seems. Only if i set it manually (static) it will use it! I have no subnets

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

Does a PC connected to the same wifi network as the phone get the proper DNS servers and work like it should?

[–] Shimitar@feddit.it 1 points 2 months ago (1 children)

Yes, perfectly... My guess is android bypass local resolver and goes via DoH l, which sucks hard

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

If you have private DNS turned off it doesn't, unless maybe you have some manufacturer specific weirdness going on with extra software.

[–] Shimitar@feddit.it 1 points 2 months ago (1 children)

Well, my experience is that unless you set static IP+DNS in android WiFi advanced networks, it will not obey the dhcp option 6.

LineageOS, vanilla with mind the gapps

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

Odd, I've had a Pixel, Oneplus 7 pro, and now a Galaxy S21 and they all pick up my DNS server from DHCP without any issues.