Asus DDNS workaround 10.x.x.x

[Chet]

Hi,

I search around the internet and SNB but I couldn't find or understand a work around to my problem. Comcast just started providing me an IP that begins with 10.0.0.x and now Asus DDNS doesn't work. I don't understand why that is and how to work around the problem. Can anyone explain the issue and how I could work around the problem and get my Asus DDNS working again.

Thank you in Advance,
Chet

 

[Grisu]

10.x.x.x or 100.x.x.x are private IP ranges, you have to ask your ISP to provide you a real public IP as before!
Seems they get out of public addresses so they use NAT like you in your own network.

 

[sfx2000]

Comcast just started providing me an IP that begins with 10.0.0.x and now Asus DDNS doesn't work

Oh wow... that's a bit of trouble, but not unexpected...

I figured they would eventually go CG-NAT, as this is less work in the long run for them to manage...

100.64.0.0/10 - Carrier Grade NAT

Comcast does support IPv6 non-NAT'ed, not sure if Asus DDNS supports that.

 

[dafergu2]

Did they replace your modem? The modem comcast gave me comes with a built in router that will issue a 10.0.0.x subnet range. This resulted in a double nat.

The fix for me was:

1) Log into your comcast modem/router by going to http://10.0.0.1.
2) Put your comcast modem/router into bridge mode

I was told by the installer that nothing worked if the comcast router/modem was in bridge mode, but I crossed my fingers about 20 minutes ago and swapped it to bridge mode (ironically because my RT-AC5300 was complaining about DDNS not being compatible). Everything seemed fine to me and I have a public IP on my WAN interface for my ASUS router.

The biggest problem I see is that the firmware for the ASUS router expects the WAN IP to be a public IP. Realistically, the ASUS firmware should query an external web api or website, such as https://www.whatismyip.com to discover the external IP address and use that when it updates DDNS. My Synology NAS does just that.

 

[Grisu]

The biggest problem I see is that the firmware for the ASUS router expects the WAN IP to be a public IP. Realistically, the ASUS firmware should query an external web api or website, such as https://www.whatismyip.com to discover the external IP address and use that when it updates DDNS.

Asus writes sinces 5 years that DDNS with private IP is under development and coming soon ...