[SOLVED] AX1800 Flint: suddenly broken DDNS

Hi,

I’m running two AX1800 (Firmware 4.7.0) using VPN from outside with resolving via GL-Inet DDNS their hostname glxxxx.xxxx.com.

Nothing changes, nothing configured, but: Some days ago this resolving breaks. There is a different IP-value between provider IPO and router ip. Routers have a public IP that works (!) from outside (no NAT), but DDNS gives a wrong IP.

I did an upgrade from 4.7.0 to (beta) 4.8.2. as said in another thread. NO change.

Routers are actually not reachable via gnxxx.xxx.com hostname and e.g. VPN not usable.

… uuuups, be patient. After support calling: This seems to be an failure by my internet provider. I’m waiting for repairing their configuration. :zany_face:

1 Like

LOL! It looks like Murphy's Law is visiting 'ya. If/when you get back up & online as expected, be sure to let others know by marking the 'Solution.' Have a good one.

You’re right. Murphy said hello.
My internet provider confirmed a configuration change to CGNAT, but it wasn't actually intended or planned. This error was corrected, and a public IP address was returned again.

1 Like

Oh Gawd... if they're even looking at CGNAT I'd make preparations to test before deploying a VPS to run HeadScale or Netbird or less ideally, TailScale, if you're not into self hosting/controlling your own infra. CGNAT is a cheap way for a ISP to expand their pools — 'line must go up' after all. FWIW only Netbird seems to be able to be set to use PQC. The last time I looked @ {Head, Tail}Scale they didn't have it.

Better to have it & not need it than need it & not have it.

Here in Germany providers connecting via Fiber optic often make the cheap CGNAT pool expanding. In two cases of my managed internet connections (until now VDSL, not fibre) I get dynamic public IPs. Change to better, stable and faster fibre conntections is actually in progress (Construction work in the village). After this something like e.g. Headscale will be necesssary… or extra costs for fixed public IP (for privat/non-business mostly to expensive.)

1 Like

Maybe you'll end up with IPv6 addressing; that should also solve the CGNAT problem but GL's firmware doesn't have full support for it ATM IIRC. IPv6 can pose other problems if not properly configured, too. I just don't bother using it.

Have a good day.