glddns.com not resolving my entry

Hello,

I have several VPN endpoints that have been resolving using GLDDNS without issue for over a year. However, in the past few days, one of them has stopped resolving, even though the unit itself is up and functioning correctly. Some remote users are still able to access it, likely due to cached DNS records.

When I run an nslookup from the command line, the resolution fails. I’ve also been unable to locate a GLDDNS management console to troubleshoot further.

% nslookup

server 64.6.64.6
Default server: 64.6.64.6
Address: 64.6.64.6#53

zza7929.glddns.com. <>
Server: 64.6.64.6
Address: 64.6.64.6#53

** server can't find zza7929.glddns.com: NXDOMAIN. <>

google.com
Server: 64.6.64.6
Address: 64.6.64.6#53
Non-authoritative answer:
Name: google.com
Address: 142.251.221.78

Could you please advise if this is a known issue or provide guidance on how to restore resolution? As a last resort, I can update all remote devices with direct IP addresses, but that’s not an ideal solution.

Thanks,
M

Hello,

Try to change the DNS server, like Google 8.8.8.8, or CloudFlare 1.1.1.1.

How about ping glddns.com or nslookup glddns.com?

Thanks for the response. I did try changing the DNS prior to both Google and CloudFlare but no luck. When I do an nslookup using ns1.glddns.com or ns2 it can't resolve zza7929 but it still can resolve my other GL device lf2ad58. It's as if the entry was deleted.

Hello,

If possible, please share the 2 routers with us through GoodCloud, we would like to check this in your router, as we did not reproduce the issue in our routers. Thanks.

May I know are these 2 routers in same one WAN source?

Please PM me the router MAC address and login Web UI password.

Hi Bruce,

For some reason, it's now resolving again. There was an intermittent power outage at the location in San Francisco, causing a reboot of the device, but as mentioned I was always able to connect to it using the IP (during the offline period in the timeline attached). When I tried to do an nslookup, attaching to either ns1.glddns.com or ns2, only the Australia device (lf2ad58) would resolve. It couldn't return an IP for the US device (zza7929). Are your DNS servers using DDNS so if a host is not reachable by the server, the host entry is removed? What else could have caused this issue?

Thanks,

If report (renew) the IP is timeout from router DDNS, the DDNS server will remove this record.
For example, if the US device zza7929 is not reported, the entry of zza7929.glddns.com will be remove, nslookup may could not resolve the IP.
Waiting for the router to report IP again, DDNS server will record the IP again.