Use GL.iNet DDNS to access local network

Routers VPN, DNS, Leaks
1

Hello everyone!

If i set in my domain DNS zone an A record pointing to my public IP I can reach my homeserver thanks to the port forwarding I set up in the router.

But if I set a CNAME record with the GL.iNet DDNS (xxxx.glddns.com), when I go to my domain I reach the Flint dashboard and not my server.

So, my question is: is GL.iNet DDNS only for router management or can I use it also as a normal DDNS to access my network? If yes, how can I do it?

Port forwarding is set up correctly because with A record pointing to the IP everything works fine.

Thanks!

2

GLDDNS is just DNS, so it does not take setting up any routes or something else.
Server access should be fine as long as port forwarding is correct. Are you sure that the records are correct and your port forwarding is working as expected?

3

Port forwarding is correct because if I set an A record with my public IP I can reach my server.
Actually I have port 80 WAN ā†’ port 80 LAN (of my nginx server), but if i set 8080 WAN ā†’ 80 LAN and i go to mydomain.it:8080 I reach my server.

If I change the webui port to 8040 I can reach my server directly with mydomain.it, using port 80.

My guess is that Flint on port 80 favours its webui, ignoring port forwarding settings. Can I change this behaviour?

4

What router and firmware are you using?

I just checked it on my Flint3e and TCP/80 was working as expected.

5

Iā€™m using Flint 3 with 4.8.3 relase.

What do you mean exactly with

If you do a port forwarding from 80 WAN to 80 LAN it works and do not redirect you to Flint webui?