Weird domain resolution behaviour with tailscale

Hello! I have a mt3000 and using tailscale with my vps as exitnode

now I have to say that on every device (android, windows…) is working great

When I configured tailscale on the router I have a very weird behaviour: only SOME domains get resolved, for instance google.* works, duckduckgo.* doesnt

I would not even know how to debug this and what/why is happening but only under the router this problem occures, I accepted all the advised subnets from the admin panel too

The domains I reported are only an example, for instance instagram, facebook all work while my university website doesnt, or this forum works too!
I know it sounds absurd but how can this be possible

If you manually set the dns of your computer to, can you resolve domain names normally?

You can use to check what dns server you are using. It is possible that tailscale’s dns server is causing some domain names to fail to resolve.

I changed to cloudflare (attached the dns leak results) and still nothing, some random domains are unreachable

and ping-ing these domains works

I’m just chiming in to say that you’re not the only one seeing this problem. There’s definitely something weird going on. I’m using Tailscale on a GL-AXT1800 (Slate AX) with Admin Panel v4.5.0 and a manually upgraded Tailscale version 1.62.0 through the script on this forum post.

I also cannot see through a browser or curl, but can ping the hosts no problem.

$  dig a

; <<>> DiG 9.10.6 <<>> a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11243
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 1232
;			IN	A


;; Query time: 502 msec
;; WHEN: Fri Apr 12 17:02:09 EDT 2024
;; MSG SIZE  rcvd: 59
$ curl
[operation times out]

However, I can ssh into my GL-AXT1800 and run the curl command just fine.