DDNS name does not resolve

Technical Support for Routers
1

Hello, I have a Flint router set up at my home, and I am currently in another country using a Beryl router to tunnel into my home internet via Flint. This setup has worked flawlessly for months, but suddenly, today, I started receiving a 'DDNS name does not resolve' error. I’ve included the logs below. Could someone please assist me urgently? I rely on this setup for remote work. Thank you!

Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Rule 'safe_mode_mark'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Rule 'safe_mode_mark_save'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Zone 'lan'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Zone 'wan'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Zone 'guest'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Zone 'wgclient'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Set tcp_ecn to off
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Set tcp_syncookies to on
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Set tcp_window_scaling to on
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Running script '/etc/firewall.nat6'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Running script '/etc/firewall.vpn_server_policy.sh'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Running script '/var/etc/gls2s.include'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): ! Skipping due to path error: No such file or directory
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): * Running script '/usr/bin/gl_block.sh'
Sat Dec 7 12:56:18 2024 daemon.notice netifd: wgclient (30378): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Sat Dec 7 12:56:18 2024 daemon.notice netifd: Interface 'wgclient' is now down
Sat Dec 7 12:56:18 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Sat Dec 7 12:56:19 2024 daemon.notice netifd: wgclient (30470): Name does not resolve: `xxxxxxx.glddns.com:51820'
Sat Dec 7 12:56:19 2024 daemon.notice netifd: wgclient (30470): Configuration parsing error

2

You need to disable & re-enable GLDDNS on your Flint.

Hopefully you have enabled GoodCloud - or somebody needs to fix it at your place.

3

Unfortunately, there is no one at home, and I am currently on a different continent. I don't believe I enabled GoodCloud. However, I do recall enabling HTTP/HTTPS remote access for DDNS, although I’m unsure of its purpose. Could you please advise?

4

Without knowing the current IP it's not possible, I am sorry.

You might refer to this:

5

I have obtained my current IP address from my ISP and can now tunnel using it instead of DDNS. However, I’m concerned that the IP address might change. Could you please advise on what steps I can take remotely to fix the DDNS issue?

6

There's nothing stopping you from setting up a second DDNS provider and having two different domain names for your routers. Just Google ddns service providers for a list of options. I use FreeDNS because they have a great free tier, but there are many other good free or cheap DDNS providers.

Companies that focus on providing DDNS usually have good redundancy in their server configurations. GL iNet is a router company that gives away DDNS services for free. However, based on past forum posts, they seem to have more downtime than companies dedicated to this service. I do not use GL iNet DDNS as my primary DDNS service.

7

Thank you for the suggestion! Unfortunately, I’m unable to access the Flint router remotely at the moment since I’m on a different continent, and there’s no one at home. I’m currently using my ISP’s public IP to establish a tunnel. I’m unsure if the DDNS provided by GL.iNet will resolve the issue on its own.

@alzhao

8

Disable and Enable the DDNS on the router.

9

Unfortunately, I can't do that because I’m unable to connect to my router remotely.

10

But you said your tunnel is working?!

11

yes but the Flint router UI is not opening up.

12

You should try the VPN IP of your router instead of the LAN IP.

13

how can I get the VPN IP of my flint router?

14

It's the VPN network (so do ipconfig for example on your PC) but the address ending with .1

15

I'm not able to find the VPN IP. None of the below work.

Windows IP Configuration

Unknown adapter flint_with_ip:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.0.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : ::
0.0.0.0

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter vEthernet (Default Switch):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::9845:2010:14b5:1ac5%24
IPv4 Address. . . . . . . . . . . : 172.19.128.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : lan
Link-local IPv6 Address . . . . . : fe80::484b:6b9:a5b8:a952%18
IPv4 Address. . . . . . . . . . . : 192.168.11.167
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.11.1

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:2841:f634:1096:2404:b3bb:50d6
Link-local IPv6 Address . . . . . : fe80::1096:2404:b3bb:50d6%13
Default Gateway . . . . . . . . . : ::

16

I had a similar issue.
Try disabling the IPv6. For some reson the DDNS domain will prefer ipv6 if is enabled on the server and client only work with ipv4.

17

I suppose I'll need to wait a few months since the server is 12,000 km away. In the meantime, I'll have to manage with the dynamic IP instead of using DDNS.

18

Have you registered it with GoodCloud?
If you registered it and enabled remote configuration, you can access the remote GUI from there.

Or if you are configuring the VPN manually, you can access the GUI through the VPN IP address.

19

It's funny you mention this because that's the conclusion I also came to today as well as my own post: DDNS throwing error when VPN Client is enabled - #27 by MowMdown

20

Unfortunately, I haven't registered with GoodCloud, and I can't figure out the VPN IP of the server to access the GUI. I couldn't find the VPN IP using ipconfig. Is there another way to retrieve it?