NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RS300 not updating dynamic DNS
I have 2 Netgear routers on my private network, they are a R8000 and a RS300. Additionally I have 2 Hostnames purchased from NoIP.com. I can define either NoIP hostname in R8000 router, click 'Sh...
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?
No changes were made to Xfinity router setup
Netgear VPN configuration pulls DDNS host name from routers DDNS settings, would have to vpn definitions
If changes to Xfinity router were causing the issue why are two Lorex NVR's and R8000 still working?
My issue - I want to run vpn on RS300, to do so I need a valid DDNS on RS300, I can try running vpn on R8000 but shouldn't have to do that - I unplugged a working R8000 router, plugged in the RS300 router that doesn't work
I did a search on setting up DDNS on an Xfinity router and got following response (this is exactly what I'm doing/trying to do)
Xfinity (Comcast) routers typically don't allow direct configuration of Dynamic DNS (DDNS) settings within their standard interface, especially with the xFi gateway. However, you can achieve DDNS functionality by using a third-party DDNS service provider and configuring it on a separate router connected to your Xfinity modem/gateway, or by using a DDNS client on a device within your network.
I'm about ready to dump the RS300 and see if I can find another option - suggestions welcomed.
Suggestions are given and something to try. Up to you though. This is a double NAT condtion which maybe effecting the RS, especially if you have both online at the same time? Having a router behind another router can cause all kinds if problems. Just because older router works doesn't mean a new one should. FW is different and new tech and new seucurity features may cause differences as well.
No changes were made to Xfinity router setup
REALLY points at the RS300. If it can be returned, that might be the best option since there is no way to determine when (or if) Netgear will address this situation.
Just as a technical note: the DDNS process on the RS300 does not actually have to function for VPN to work. (Bear with me, please.) Once the VPN configuration file has been created, the point is to have a valid URL to resolve to the current public IP address of the RS300. With UDP ports 12973 and 12974 being forwarded through the Xfinity to the RS300, any process that updates the DDNS service when the public IP address of the Xfinity router changes. As Xfiinity says, it could be any device on the home network that can update DDNS. No-IP.com offers a Dynamic Update Client (DUC) which can be installed on Windows, Mac, and Linux https://my.noip.com/dynamic-dns/duc:
If this RS300 is less than 90 days old, it would be helpful to open a case with Netgear about it not updating DDNS. (Even if this one gets returned, other customers will face the same issues.)
While setting up VPN on a router connected to my primary network (i.e. "Double NAT on Purpose"), I noticed that VPN does not actually require use of DDNS. On the DDNS page for my RBR50 and the RBR750 I am using for this test:
Use of a Dynamic DNS service appears to be optional.
It is clearly the most convenient method to use a URL rather than a specific IP address in the VPN configuration file, but seems to be a choice, rather than a requirement.
I will complete the experiment using No-IP.com and report soon.
