Setting Up External Domain Access with Reverse Proxy Configuration

Other Questions NPM
1

Hi everyone,

I’m working on a learning project to better understand how reverse proxies and DNS work together for external access.

What I want to achieve: Access my media server by typing “mediaserver.mydomain.com” on my phone while using cellular data.

Current setup:

  • Purchased domain and created DNS A record pointing to my public IP address
  • Configured firewall rules on my router to forward incoming HTTPS requests to my reverse proxy container
  • Created proxy host entries for my services (like mediaserver.mydomain.com) and matching DNS entries in my local DNS server
  • Local testing works perfectly fine
  • Added NS record in my domain registrar pointing to my local DNS server
  • Opened port 53 traffic to my DNS server

The problem: Still getting DNS resolution errors when testing from outside my network.

Anyone have suggestions on what might be wrong with my configuration?

Note: I understand this setup has security implications and it’s just for educational purposes to learn how public DNS resolution works.

2

i think ur ns record might b off. lots of ISPs block port 53 from outside, so ur local dns ain’t reachable. maybe try a public dns like cloudflare or google? should help with that resolution issue.

3

Your config looks mostly right, but there’s a big problem with using your home DNS server as the authoritative nameserver. Most ISPs block port 53 traffic coming in, and even if yours doesn’t, your home connection isn’t reliable enough for public DNS. That NS record you made is basically telling everyone that your home server handles your domain’s DNS - that’s a single point of failure waiting to happen. Don’t fight this battle. Just use your registrar’s DNS service or something free like Cloudflare. Keep your local DNS for internal stuff and let the public DNS handle everything else. Way more stable and you don’t have to expose extra ports.

4

Been there, done that. You’re overcomplicating this DNS setup massively.

Everyone’s right about the NS record being problematic, but here’s what works better. Skip fighting with DNS configs and firewall rules - just automate everything.

I use Latenode for similar setups to manage domain records when my public IP changes. Create a scenario that watches your IP, catches changes, and updates A records through your DNS provider’s API. No more manual NS records or exposing your home DNS server.

For reverse proxy stuff, Latenode can watch your services and update proxy configs when you add containers or services. Mine watches Docker events and updates proxy rules automatically - zero manual work.

The big win? Reliability. Your current setup has way too many moving parts. One automation workflow handles IP changes, DNS updates, and proxy config. Way cleaner than exposing port 53 and hoping your home connection doesn’t crap out.

Trust me, automation crushes manual config every time, especially for learning projects where you want to focus on concepts instead of troubleshooting.

5

You’re mixing local and public DNS infrastructure, which creates problems. That NS record makes external clients query your home server directly - but home internet wasn’t built for authoritative DNS hosting. ISP port blocking is just one issue. You’ve also got dynamic IP changes, uptime problems, and zone config headaches that home setups can’t handle reliably. I learned this the hard way. Here’s what works: Skip the NS delegation completely. Just create an A record for mediaserver.mydomain.com at your registrar (or use a real DNS provider) and point it to your public IP. Your reverse proxy will still work fine - it routes based on the Host header, not DNS. This separates everything properly and actually works for external access.