D7000v2 Dynamic DNS not working locally

[SimonFx]

Netgear D7000v2 (firmware V1.0.0.51_1.0.1)
On my old router (Netgear R6220) had dynamic DNS set (e.g. abc.mine.nu) via DynDNS.org. On any local machine (connected to the router) if I accessed abc.mine.nu then it would translate to the relevant local computer according to port forwarding set up on the router (e.g. web went to my NAS). The Netgear D7000v2 dynamic DNS works fine for sites external to the router, but does not work for any computer using the router (note: DNS set to router). Is there a setting on the D7000v2 that I must activate to make this happen or is this feature not available yet?

[antinode]

> [...] The Netgear D7000v2 dynamic DNS works fine for sites external to
> the router, but does not work for any computer using the router (note:
> DNS set to router).

   Dynamic (or any other) DNS simply translates a name to an IP address.
Does "abc.mine.nu" get translated to your external/public IP address on
one of your LAN systems (as it seems to do on your "sites external"
systems)?  A command like "nslookup abc.mine.nu" should show this.

   You could try a test using your external/public IP address instead
of your DDNS name; the results should be the same (as with the DDNS
name) in both the local- and external-client cases.

   If name-to-address translation works everywhere, then dynamic DNS is
not the problem.  If your external/public IP address (as shown by
"nslookup") is the WAN/Internet address of the D7000v2, which it should
be, and your port-forwarding set-up works for external clients but not
for local clients, then the most likely explanation would be that a
feature called "NAT loopback" is not working on the D7000v2.

   There have been other reports of such a problem with the D7000v2, but
they tended to be short on details, making the possible problem hard to
confirm.

   If it makes you feel any better (or worse), I use a D7000[v1]
(currently at V1.0.1.64_1.0.1) and have seen no such problem (back so
far as V1.0.1.48_1.0.1).  (Different hardware, different firmware.)

[amistry]

Hi,

Just wondering if you've had any support from NETGEAR regarding this issue?

[SimonFx]

This problem continues.

I checked my old setup on the Netgear R6220 hardware and this feature works perfectly. However, even with the latest BIOIS update (V1.0.0.51_1.0.1), the D7000v2 continues to fail.

External web access to the ddns address of abc.mine.nu is directed to the correct device. Internal web access is incorrectly sent to the Netgear setup page.

I host game days where we need to access web resources, so when the venue is my house, I have to bad mouth Netgear; and get people to use the IP address of the web server.

[SimonFx]

<deleted>

[SimonFx]

<deleted>

[SimonFx]

Sorry for the repeats. Netgear community site claimed it could not post at the moment, I had to retry in a few minutes!

[antinode]

> [...] and get people to use the IP address of the web server.

   Just to be clear, that'd be the LAN "IP address of the web server"
(rather than the WAN/Internet IP address of the router).

[SimonFx]

Yes.

On the local network, users need the LAN IP address of the web server 192.168.0.xxx, using the DynDNS domain name locally gets the router admin web.

Externally, just the DynDNS domain name works fine, NAT fowarding to the server above (192.168.0.xxx).