I tried using DNS google recently, For some reason after like 10 minutes of usage the DNSTT isn’t working anymore nor returns anytjing. So i tried testing it with Dig.
but other domain still works fine
I assume that my domain get rate-limited or something. Is there anything I can do to prevent rate-limiting? Without the use of other resolvers like 1.1.1.1, quad9, etc…
I tried using other servers too with different domain. It’s the same result.
It’s quite possible that the connection is getting rate-limited, whether by detection of the dnstt protocol encoding, or just be sheer volume of requests.
I experienced something similar with Champa (which is similar to dnstt) and the Google AMP cache. It would work OK for about 10 minutes, then get rate-limited down to almost zero. The rate limits expired after a few hours.
I don’t have a good idea for a workaround. But I would recommend trying this other DNS tunnel, which is inspired by dnstt but which the creator has measured to have better performance:
If the rate limits have to do with protocol detection, it may work, because it uses a different encapsulation protocol. But if they have to do with request volume, it probably won’t help.
