Hi. Is there any update on the ETA for fixing the GL DDNS servers?
NS1 an 2 have been down for nearly 5 hours and I'm getting dozens of calls from clients not able to connect to their VPNs.
https://glinet-status.admon.in.ua/
Thank you!
2 Likes
Guess it was a bigger issue since the forum was offline as well.
Maybe @alzhao can give us some post mortem report later.
1 Like
@admon Thanks for the feedback, but it's still offline so no one running self-hosted is able to connect right now. I've barely slept trying to get people back online using temp static IP configs so people can work. An ETA would be sincerely appreciated.
As part of post mortem, it would be good to understand if NS1 and 2 are actually co-hosted? Typically NS servers would always be on entirely separate infrastructure and data centers to prevent what's happening now.
1 Like
Since I don't work for GL, I can't help.
ETA is "if it works again, it works again" - at least from my side 
1 Like
@admon Ah.. gotcha. Figured since you hosted the status page that you were connected. Thanks for the response.
I have been in contact with GL direct and they're hoping within "a couple hours". (fingers crossed)
@alzhao - any updates would be appreciated.
I guess I need to make it more clear. Currently it shows "This inofficial status page shows..." 
I might just remove the GL logo, hopefully people don't get confused then anymore.
1 Like
Yeah, it was based on you hosting that, and that you're always so helpful & knowledgeable on here. Just made an assumption. Thank you though.
1 Like
Thanks for the flowers 
Let's hope the GLDDNS will come back soon - right now it flip-flaps...
1 Like
Hi, I am having this problem too. I bought a flint 2 yesterday and thought it was my problem with the configuration.
Are these DDNS problems common? Is there any way to configure an external DDNS like in openWRT?
DDNS was just fixed. Takes a little while so that everyone's ddns is updateed.
6 Likes
Thanks @alzhao ! I'm starting to see them come back online as well. Appreciate the work and the update!
1 Like
If the nslookup my-id.glddns.com says that "server can't find my-id.glddns.com: NXDOMAIN" does it mean that I should wait a bit longer to get everything updated or can it be another issue? (I set up my WireGuard server on a brand-new Flint 2 router yesterday and it worked smoothly that time, my backup client config with the public IP still works)
Have a check of your ddns using https://dnschecker.org/ to see if it is updated in other places.
1 Like
Hey all,
I am having issues still. Anyone else?
It hasn't worked for me all day and it's still the same
My GL-MT6000 is not yet able to register the public IP on GL-iNet DDNS:
glddns: Get registered/public IP for 'xxxxxxx21.glddns.com' failed - retry 89/0 in 60 seconds
glddnsv6: Get registered/public IP for 'xxxxxxx21.glddns.com' failed - retry 89/0 in 60 seconds
@Banerjee @pfriezas @wrapozo @Benco - I'm finding with a lot of my clients that I've had to restart the DDNS client on the home/server router to get it to update again. Somehow it seems to be "stuck" and wouldn't start updating the DDNS server again until it got a kick.
EDIT - After restarting on the home/server router, then give it 5 minutes and restart the VPN client on the travel router again.
@alzhao FYI.
2 Likes
After the 3rd restart of gl_ddns service on my home router, it worked for IPv4.
IPv6 is not yet available, but by now I don't need IPv6 ddns.
I as able to connect a client to my home router via wireguard using ddns.
1 Like
Restarting the service worked like a charm!
Thanks!
2 Likes