DNS Takes too Long to Resolve via CLI, Scripts Time Out - Fine with Clients

Routers
1

GL-A1300 running 4.5.22 and Tailscale.

Devices connected to this router work just fine - all is great. If, however, I try to run something FROM there router, there seems an odd DNS issue.

For example, if try to update Tailscale via a commonly-used scrip (below), it won't resolve raw.githubusercontent.com. It's not just that name, however - if I try a wget from anywhere remote I have that issue. Similarly, when I updated to 4.5.22 recently, I had to do so manually, as it failed to download the update.

If I do an nslookup, it eventually works...but takes a good 30 seconds. That delay, nor any of these issues exist on clients.

I've manually specified the DNS (used Google DNS) rather than have it assigned with DHCP, but that didn't make a difference. I've poked around other DNS settings in LuCI but nothing sticks out.

Any ideas?

wget -O update-tailscale.sh https://raw.githubusercontent.com/Admonstrator/glinet-tailscale-updater/main/update-tailscale.sh \
&& sh update-tailscale.sh
2

Hello,

You can manually configure the custom DNS server for the LAN (including the Router itself) in Luci, here:

image
image896×741 30.4 KB

1 Like
4

Did the trick, thanks so much! I'll need to see why this isn't an issue on the other units I'm running. I recall one or two needed to have the have the routing set manually (bug in the Tailscale setup it seems) and I'm guessing that's the reason.

Either way, thanks a bunch!

1 Like