How do I resolve my domain name?
Comment on Public DNS server with gui
AtariDump@lemmy.world 8 months ago
Do. Not. Open. Port. 53. To. The. Internet.
Just Don’t.
possiblylinux127@lemmy.zip 8 months ago
ikidd@lemmy.world 8 months ago
From outside? Set up a Cloudflare account and point the NS from your registrar to it.
From inside? Set up unbound on a docker host and don’t open it to the internet. Use that one when you’re local and the normal public DNS when you’re outside. But everything I’m seeing in here makes me sure you shouldn’t even consider opening ports in your firewall to expose inside host services. Use a VPN when you’re roaming, and only use your DNS for local servers/hosts via that VPN. The only use for your outside domain name should be to point a single hostname to your outside IP address so you can use it for your VPN endpoint.
AtariDump@lemmy.world 8 months ago
DynDNS
Rootiest@lemmy.world 8 months ago
I use a DNS server on my local network, and then I also use Tailscale.
I have my private DNS server configured in tailscale so whether on or off my local network everything uses my DNS server.
This way I don’t have to change any DNS settings no matter where I am and all my domains work properly.
The other advantage is you can configure the reverse proxy of some services to only accept connections originating from your tailscale network to effectively make them only privately accessible or behave differently when accessed from specific devices
Gooey0210@sh.itjust.works 8 months ago
Or use encrypted dns 😕 it’s 2024, time to use encryption
AtariDump@lemmy.world 8 months ago
That wouldn’t help with an open resolver.
Gooey0210@sh.itjust.works 8 months ago
Use encryption, using vpns for such a trivial task is a “really bad idea”
There are many cases when somebody wants to have their dns public, maybe they want to share with their friends, family, community, audience (not everyone is a solo server user)
Also, it’s good to use your dns even before connecting to the vpn. Just use encryption, it’s safe and nice
Keeping 53 opened is not that bad, the only thing you will notice is an increased load on your server if somebody tried to ddos somebody’s server using your dns
atzanteol@sh.itjust.works 8 months ago
Use a public dns provider. Cloudflare, route53, dyndns (are they still around?), etc. Cheap, reliable, no worries about joining a ddos by accident. Some services are better left to experts until you really know what you’re doing.
nik282000@lemmy.ca 8 months ago
I ran my ssh behind 53 for a while because it’s rarely blocked. A few bots even got it right and figured out it was ssh.
EncryptKeeper@lemmy.world 8 months ago
This is why the concept of running services until different ports than default isn’t a real security measure, it doesn’t actually take any effort to figure out what kind of service is running on a port.