Hello!
I want to set up a pi-hole on my home and connect from my parent’s.
Both setups have a dynamic IP assigned by my isp and are different networks.
I have a couple of questions:
I can get a domain that updates automatically. But how would I resolve it on the client side?
Is there any way to authenticate on the server? By Mac maybe? That can be spoofed right?
Edit: my bad, thanks for correcting me, Mac is another layer completely
DynDNS. That will give you a hostname, but check if your ISP offers a static IP tbh. Client side shouldn’t matter overmuch if you’re returning requests it’s made
I’ll second this recommendation and add a bit more. I’d recommend using DuckDNS’s dynamic DNS service. It’s free (donate if you can!) and fairly simple to set up. I run it on my router since it supports it but it’s easy to run in a docker container too.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
DynDNS. That will give you a hostname, but check if your ISP offers a static IP tbh. Client side shouldn’t matter overmuch if you’re returning requests it’s made
I’ll second this recommendation and add a bit more. I’d recommend using DuckDNS’s dynamic DNS service. It’s free (donate if you can!) and fairly simple to set up. I run it on my router since it supports it but it’s easy to run in a docker container too.
I recommend DuckDNS as well, you can run it both sides and set up a daemon to update the domain when there is an IP change automatically.
And with Wireguard you can set up a tunnel between both locations so you can share anything you need.