this post was submitted on 15 Sep 2024
14 points (88.9% liked)

Selfhosted

40246 readers
845 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
14
local DNS server does not work as expected (lemmy.ml)
submitted 2 months ago by WbrJr@lemmy.ml to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

So I am working on my home server. I installed docker and use a dnsmasq container as my dns server to resolve local ip adresses.

Laptop and server are both linux (ubuntu LTS 24.4)

What works:

  • 'resolvectl status' shows the ip of my dns server
  • i can ping the ip of the dns server (that will run other stuff like nextcloud soon as well)
  • i can use nslookup to resovle server.local to the correct ip address (even after changing the entry, so its not the cache in my laptop)

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

What am i missing?

Thanks a lot already! BTW: ZFS is crazy nice :D

you are viewing a single comment's thread
view the rest of the comments
[–] catloaf@lemm.ee 8 points 2 months ago (2 children)

First, don't use .local, as it's used by mDNS. You should use .internal or a domain you own. I recommend changing before you get any more committed to your environment.

I'm not really following your post, because you're not specifying whether each point is on the server or laptop.

Personally, I dislike Ubuntu on the server because of how it runs stuff like systemd-resolvd, which as you've experienced, gets in the way of standard operation.

[–] possiblylinux127@lemmy.zip 0 points 2 months ago

Just use .lan