DDNS Domain Resolution errors

Technical Support for Routers
1

When I go into the GL iNet DDNS settings and do the DDNS test, I get

“The IP from DDNS domain resolution is not the same as the WAN IPs of the device. You need an Internet Public IP address to use the Dynamic DNS. If this router is behind NAT, you may need to set up port forward in your ISP router. If you have VPN Client enabled, please disabled “Services from GL.iNet Use VPN” in the global options.”

I have a public IP address and I believe port forwarding is set up as my Wireguard VPN client correctly connects to the Wireguard VPN server. I also disabled the services from GLiNet use VPN.

I manually checked the DDNS as shown here:

and both addresses were the same. I am confused what may be the issue.

2

The GL.iNet DDNS test is known to be not reliable.

It is more reliable to check that the IP address from nslookup on the DDNS domain name matches the IP address from whatismyip.com.

I do not work for and I do not have formal association with GL.iNet

3

What’s your router model and firmware version? This may be a bug.
To confirm the DNS record is informed to ddns server correctly, issue command:

nslookup xxxxxxx.glddns.com ddns.glddns.com

If that returns your public IP correctly, then wait a minute for DNS sync between servers.

1 Like
4

I get

Server: ddns.glddns.com

Address: [server Address]

Name: xxxxxx.glddns.com

Address: [ my IP from DDNS Domain Resolution in DDNS test]

5

model mt-3000, version 4.20

6

If you need to use port forward to make the Wireguard server work, then mt-3000 is under NAT.
So I think it’s normal.

7

Hi there. I have exactly the same issue. I setup port forwarding on my ISP router. And have a GL.iNet Slate Plus plugged into the ISP router which is supposed to function as my Wireguard Server.

I did try your command: nslookup myDNS.glddns.com ddns.glddns.com

And I am getting a request timed out. What does that mean now?

8

Does ping response? seems the server is unreachable.

C:\Users\handongming>ping ddns.glddns.com

Pinging ddns.glddns.com [44.235.104.247] with 32 bytes of data:
Reply from 44.235.104.247: bytes=32 time=211ms TTL=41
Reply from 44.235.104.247: bytes=32 time=211ms TTL=41