Isn't .local a mdns auto configured domain? Usually I think you are supposed to choose a different domain for your local DNS zone. But that's probably not the source of the problem?
this post was submitted on 15 Sep 2024
15 points (94.1% liked)
Selfhosted
39435 readers
2 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:
- 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
Changing the domain does not change the problem sadly. I thought .local is a safe one to use
There was a post recently about ".LAN" recently being added to the DNS spec
what does not work:
- i can not ping server.local (- for testing i have to stop the systemd-resolved.service to run the dnsmasq server, or else there are port collisions, but that should not be the problem i guess. I am happy to hear your solution :))
- i can also not use ssh to log in to server.local, ip address works
Have you added "server.local" as a DNS record in your dnsmasq container, pointing to your servers LAN IP? Sounds like dnsmasq isn't resolving that name, which would lead to both of these 'failures'.
So in the dnsmasq.config file is this entry: 'address=/server.local/192.168.178.10' and using nslookup it resolves it correctly
Does it resolve correctly from the laptop or the server. What about resolvectl query server.local on the laptop?
When I am on the server, it can even ping the domain. On my laptop, it can only resolve the domain to the correct ip
Could you post the specific output of the commands that don't work? It's almost impossible to help with just 'It doesn't work'. Like when ping fails, what's the error message. Is it a timeout or a resolution failure. What does the resolvectl command I shared show on the laptop. If you enable logging on the DNS server, do you see the requests coming in when you run the commands that don't work.