RS300 not updating dynamic DNS

Is the RS connected behind the R8000? This is a double NAT condition which may interfer with the RS updating services correctly. 

You might try the RS router in place of where the R8000 router is and check.

Have xfinity router/modem as primary, RS300 router is plugged into xfinity router, R8000 router is plugged into RS300 router - the RS300 router has a ton of definitions in it, reserved addresses, port forwarding, VPN , etc so I hesitant to do a factory reset. 

It replaced the R8000 which had all of these definitions  and working  DDNS too, As long as I keep the R8000 up it's ok, can just use the hostname for external connections

Network

                                                  in                         IP address        IP Range

xfinity modem/router   Coax                   10.0.0.1              ( 10.0.0.2 - 10.0.0.254)

RS300 router                 10.0.0.155            192.168.0.1        (192.168.0.2 - 192.168.0.254)

R8000 router                 192.168.0.200   192.168.25.1      (192.168.25.2 - 192.168.25.254)

Hope that helps

Question - does anyone have a RS300 with Dynamic DSN on with a hostname from NoIP.com where show status works?

Thanks

I have the RS500 (fw: 1.0.1.90) and can attest that a.) The status function fails 99% of the time and b.) that the router does not send periodic updates to the DDNS provider. I've reported the symptoms to NG but so far there's no fix.

Sorry I did not see this conversation earlier.  I do not see mention of ports being forwarded through the Xfinity router.

Which network(s) contain devices that are access externally?

When doing a DNS lookup on the host names defined with NoIP, is the IP address that is returned the public IP of the Xfinity router?

Perhaps it would be useful to query NoIP about how their system deals with DDNS names being updated by two separate routers.

Ports forwarded in Xfinity router

37000-37001 TCP/UDP

35000-35001 TCP/UDP

12973-12974 TCP/UDP

All port forward definitions are to the Netgear RS300 Router

Ports 12973-12974 are for VPN on RS300

Ports 37000-37001 are routed from RS300 to Lorex 16 camera NVR

Ports 35000-35001 are routed from RS300 to Lorex 8 camera NVR

R8000 is in another room to provide wifi connectivity for Generac and better wifi in front of house

Lorex has a free DDNS Service and I have 2 through them, each is up dating correctly

Before I bought the RS300 the R8000 was sitting in its place with a NO-IP DDNS definition working correctly, I replaced the R8000 with the RS300  for a faster router and 6G  wifi, I haven’t been able to get DDNS to work.

I only added the R8000 back on my network because the Generac wouldn’t connect reliably to the RS300.

Also if you look at all replies in this chain pkaytes replied that he has a RS500 with the same issue

“I have the RS500 (fw: 1.0.1.90) and can attest that a.) The status function fails 99% of the time and b.) that the router does not send periodic updates to the DDNS provider. I've reported the symptoms to NG but so far there's no fix.”

As a test I unchecked DDNS on the R8000 router then rebooted, next I tried show status on the RS300 and got same error, next I changed RS300 DDNS definitions working DDNS with working definitions from R8000, rebooted and show status failed, next I set DDNS Service Provider to NETGEAR and followed steps to create a free No-IP account, created a new DDNS host name / userid / password and tried in RS300 – Show status failed, as last test I put latest host name / userid / password in R8000 and Show status worked correctly.

Read through the DDNS section of user manual (starting on page 145) to see if there was something I missed but didn't see any thing

https://www.downloads.netgear.com/files/GDC/RS300/RS300_RS280_UM_EN.pdf

I have used the same protocol to "stack" port forwarding on several routers:

Router A, public IP with ports forwarded to local IP of router B.

Router B, same ports forwarded to local IP of router C (connected to router B)

Router C, same ports forwarded to local IP of device connected to router C.

Worked fine.  Illustrates that a determined user can connect a local resource to the internet through a Triple NAT.  

What I do NOT recall is setting up DDNS on router B or router C.  Neither of those routers know the Public IP address of router A.  (They know only the IP address assigned to them by the router they are connected to.)

The post by pkaytes​ does not indicate that his RS500 router is connected to a router.  His CM3000 is a mid-split DOCSIS 3.1 cable modem.

Questions:

• Is there a reason DDNS is not set up on the Xfinity router?
• Is there any possibility that prior to installing the RS300, the Xfinity was in "bridge" or "passthrough" mode?

The current RS300 firmware does not update the DDNS serverv periodically, and we are working to release the fixed firmware. mzeazeas32​ , I will PM you a RS300 release canddiate v1.0.5.12 that has fixed this issue, you may give it a try.

The VPN server function on the router requires the DDNS to be enabled or static public IP address to be used on the WAN side. The VPN server's certificate is bond to the static IP address or the DDNS hostname name.

If you cannot connect a VPN client from the remote to the RS300 behind an Xfinity gateway (looks you have port forwarding rules setup already), we will need to do some troubleshooting to identify where is wrong. From what mentioned here, I cannot tell if it's DDNS, VPN, or something esle.