Reply
Highlighted
Aspirant

Nighthawk R7800 Local DNS Resolution

I had a Nightawk R7000 but upgraded to the R7800 and am having an issue with local DNS resolution.  I own a domain and am using DyDNS to direct the domain to my local IP address via my NAS and the router and would use the DNS name to access the resources from both remote and local devices. 

 

This all worked fine until i did a factory settings reset of the router and now i'm unable to access my local resources using the DNS name.  So where previously the home.mydomain.com and 192.168.1.123 worked both locally as well as from outside the network, now home.mydomain.com only works when I'm trying to connect from outside the network and 192.168.1.123 only works when i'm connecting from within the LAN.

 

Am I missing a setting or something?  Should i switch to DD-WRT?  What's going on here?

 

Model: R7800|Nighthawk X4S AC2600 WiFi Router
Message 1 of 4
Highlighted
Aspirant

Re: Nighthawk R7800 Local DNS Resolution

Oh, to note one thing, the NAS (synology) uses port 5001 for management and such, and that port is mapped to the NAS in the router using uPNP along with a handful of other ports.

Message 2 of 4
Highlighted
Sage

Re: Nighthawk R7800 Local DNS Resolution

> I had a Nightawk R7000 but upgraded to the R7800 [...]

   Firmware version(s)?

> [...] So where previously the home.mydomain.com and 192.168.1.123
> worked both locally as well as from outside the network, [...]

   A private (and non-routable) address like "192.168.1.123" could never
have worked from the outside world; it could work only from your LAN.

> [...] now home.mydomain.com only works when I'm trying to connect from
> outside the network and 192.168.1.123 only works when i'm connecting
> from within the LAN.

   If a feature called "NAT loopback" is working on your router, then
the WAN/Internet address of your router should work from your LAN as
well as from the outside world.  If your DynDNS stuff is working
properly, then that name should work the same as the router's
WAN/Internet address.

   There have been many reports about NAT loopback not working on the
D7000v2, so Netgear firmware shouldn't be trusted on this, but all I
found in my notes about an R7800 was a not very satisfying complaint:

      https://community.netgear.com/t5/x/x/m-p/1668483

   A more diligent/extensive search might find more.

Message 3 of 4
Highlighted
Aspirant

Re: Nighthawk R7800 Local DNS Resolution

Hello,

 

Thank you for reminding me of what that feature is called (nat loopback).  Using that I was able to find that my setup with Synology using UPnP to setup port forwarding on a Netgear router doesn't always work well and can cause nat loopback issues.  When i switched to manually setup port forwarding rules the nat loopback issue went away.

 

To answer your questions:

 

I'm currently using voxel's firmware version 1.0.2.62SF (www.voxel-firmware.com).  It's based on the netgear firmware but has updated packages.

 

> [...] > [...] So where previously the home.mydomain.com and 192.168.1.123
> > worked both locally as well as from outside the network, [...]

>    A private (and non-routable) address like "192.168.1.123" could never
> have worked from the outside world; it could work only from your LAN. [...]

 

Yes, you are correct that is not routable on the internet.  I meant to say I could access it via either method on my local network, and the domain name access also worked externally (besides local lan access) and now the domain name access only works when accessing it externally, not locally.  

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 2114 views
  • 0 kudos
  • 2 in conversation
Announcements