Configuring Porkbun DNS for internal IPs

dontwakethetrees (she/her)@lemmy.world to Selfhosted@lemmy.world – 25 points –

Hey everyone, asking here since I've been trying (and failing) at the numerous guides online. The end goal is so that I can have proper Let's Encrypt certs for my self hosted servers to include VaultWarden (which will not work with self-signed or http) as well as have easy urls for myself and family to use.

So I am trying to setup my Porkbun domain with my Opnsense nginx plugin in order to resolve the address (such as navidrome.example.com to my local server's navidrome instance @ 192.168.1.99:4533). I attempted this guide here as well as trying to configure a separate nginx on the server itself. I haven't had much luck with these guides either.

Any address outside of router.example.com results in a connection failure. Including when I tried to route everything like navi.router.example.com. This is with and without wildcards in the A Record entries on Porkbun's DNS control panel. I've tried *.example.com, *.router.example.com, navidrome.example.com, navidrome.router.example.com.

Sorry if this seems like a simple problem or if I am missing a massive step, I am complete newbie at self-hosting/networking.

edit: Finally got it working with the simple urls resolving to the proper self-hosted services and with proper CA certs. Thank y'all for the help and advice!!

10

You are viewing a single comment
View all commentsShow the parent comment

Nope, just substituted out my domain for the post.

Ran dig +trace and my domain and it returned a 100.x.x.x#53 public domain address.

Is that expected? Otherwise check to make sure DNS settings for the domain are correct (eg ns records dig NS example.com IIRC).

So following dig ns domain in terminal vs web app on my phone (shared by another commenter and I had checked lemmy on mobile): my computer was resolving with a couple of different odd results including my public ipv6 address. On mobile it resolved properly.

Checked my DNS and my computer’s dns had my public ip in the listing. So now after removing that, the domain resolves to the wildcard (which dumps at my opnsense router and throws the dns rebind error). So I’m assuming that should be it?

Now I should only have to resolve configuring nginx properly.

Thank you for suggesting the dig command!

Excellent! Nice work.

I don’t know what dns rebind is but once DNS A records are pointed to the right place then it’s just a matter of setting up the rest of your stuff.