Selfhosted

52744 readers

504 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Local dns rewrite problems on android (lemmy.world)

submitted 1 week ago by marci@lemmy.world to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

I have some services set up which i make available with tailscale and a domain name outside my lan. Inside my home network i set up adguard dns rewrites to use the same domain for devices which are not on my tailnet. I disabled dns rebind protection in my fritzbox for these domains.

Now my problem: I don't leave my phone connected to tailscale all of the time because of high battery drain. Inside of my wifi the phone should still be able to access my services using the domain, but it is only able some of the time. My work laptop (not on my tailnet) is able to access the services.

Is the dns cached somehow in android? Is the private dns setting of android overwriting the dns i configured in my router? Where else could the problem lie? Any hints are appreciated :)

top 8 comments

sorted by: hot top controversial new old

[–] rtxn@lemmy.world 2 points 1 week ago (1 children)

private dns setting of android

Probably. If that setting is enabled, Android (including Graphene) defaults to 8.8.8.8 if the higher-priority DNS servers (manual or received from DHCP) don't support DNS-over-TLS or DNS-over-HTTPS.

[–] marci@lemmy.world 1 points 1 week ago (1 children)

I disabled private dns and it seemed to work yesterday, but today i can not connect to my services again. Any other ideas on how to pin down the issue?

[–] rtxn@lemmy.world 2 points 1 week ago (1 children)

Install Termux, then use either the dig or nslookup command to query the DNS name, and check which DNS server is queried. If it's the private server's address, you might be having connectivity issues. If it's 100.100.100.100, the resolver is still trying to query Tailscale's MagicDNS.

[–] hexagonwin@lemmy.sdf.org 2 points 1 week ago* (last edited 1 week ago) (2 children)

doesn't termux always default to 1.1.1.1?

edit: https://old.reddit.com/r/pihole/comments/iivdgq/psa_termux_on_android_does_not_use_system_dns/ maybe its 8.8.8.8, don't have my phone so can't check rn

[–] marci@lemmy.world 1 points 1 week ago

Yes no matter if it works or not, it always returns the tailscale ip I configured with cloudflare, saying it is using 8.8.8.8 as the dns server.

[–] rtxn@lemmy.world 1 points 1 week ago

Right... my mistake, I guess I had SSH config entries in Termux and never questioned whether SSH was using those or DNS.

Still, try to find some way to check which server is being queried. It might reveal connectivity problems with the local DNS server.

[–] kossa@feddit.org 1 points 1 week ago (1 children)

I kinda had a similar problem. Never found the root cause, but what did the trick for me was to put an OpenWRT Router between the default ISP router and my home network.

As I said, I never figured out, why Android did not respect the DHCP settings of the default router, but here we are. Maybe it was some DNS shenanigans by the ISP's config, maybe it was a wrong DNS/DHCP configs from my side, maybe it was IPv6 shenanigans. Those are the culprits I would investigate from your side.

[–] marci@lemmy.world 1 points 1 week ago

I configured Adguard now as the ipv6 dns server in the fritzbox as well. For now it seems to work, under settings > network & internet > network details for my home network it shows the right dns addresses now. Thanks!