What's new

Solved How to configure DNS when behind ISP's DMZ [1:1 NAT]? RT-AC88U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ags

Regular Contributor
I've recently switched ISPs. Previously Comcast provided a dynamic public IP address (which actually never changed in over 5 years). I configured it to use dns-o-matic to update a dns service and port forwarding for a few ports to access services on devices on my LAN. This setup worked fine for me.

Now I've changed to a new (fixed wireless) ISP, and for some reason they have me behind equipment that results in my router WAN IP address being a private address (192.168.1.*). I was told this is setup as a DMZ address, with all traffic to my (static) public IP address being forwarded to this private address (like a 1:1 NAT). I am guessing they do this to multiplex a single public IP address to multiple users - but that's just a guess. To work in this new environment I've disabled the router's DDNS client and manually set my static public IP address. I can access the internet, but still cannot access anything on my LAN from the WAN using either the public IP address or my domain name.

I'm stumped and would appreciate ideas on what to check.
 
Last edited:
It turns out that I had multiple problems contributing to this problem. Ultimately, I resolved them with router settings, so I can access my LAN from the WAN. DDNS is still disabled, and I cannot access my LAN from my LAN using my domain name or public IP; I can access with the local LAN IP address, but then get an invalid certificate warning. I've taken that to a separate thread here.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top