Yet another glddns.com (dynamic DNS) outage

Cloud Services
1

GLddns.com is not resolving, so dyndns is down once again. This is getting really frustrating. I’ll be switching to another more reliable service.

~$ dig glddns.com

; <<>> DiG 9.20.21-1-Debian <<>> glddns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 40697
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;glddns.com.			IN	A

;; Query time: 439 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Mar 30 13:13:12 CEST 2026
;; MSG SIZE  rcvd: 39
2

Hi,

Thank you for your feedback and apologize for any inconvenience caused.
We’ve asked the R&D team to look into it right away.

4

Same here, I’m not able to access my routers through DDNS this morning

5

Same here - can’t VPN into my home router. I worked around this by using Goodcloud to find it’s IP address, and adjusted the Wireguard hostname.

Is there a way to switch to another dynamic DNS provider on the router, using Applications? Any recommended providers?

2 Likes
6

Interested in alternatives as well

7

I’ve been using afraid.org for ages and never experienced an outage. I guess, the devil made me switch to glddns. I’m reverting right now.

8

OK, they fixed it for now. But there is a history of this happening again and again. I’ve lost trust, I have to say, and I’ll definitely be switching.

9

I use afraid.org for my DDNS service. It is free and updates reliably with a simple cron entry that runs a curl command. I have used it for more than ten years without any issues.

Everyday my remote routers email me a status update that includes their external IP address, so I always have an up‑to‑date record and I know the routers are still healthy.

I really like the reliability of GL iNet hardware. The firmware and online services, however, have been hit or miss over the last few years.

10

We sincerely apologize for the inconvenience caused by the recent service interruption.

As reported by other users, the GL.iNet Dynamic DNS (GLDDNS) service was fully restored on March 30, 2026, at 20:50.

In response to this incident, we have directed our infrastructure team to implement several improvements, including enhanced service stability, more robust failure alerting, and proactive monitoring measures to ensure a more reliable experience moving forward.

11

It looks like this service has existed in one form or another since 2018. Given that history, should the steps you outlined not already have been in place?