 |
Post Axb1y5YtoQ5utUgRcm by [email protected] |
 |
More posts by [email protected] |
|
Post #AxYvkCq6yAONMzoNtI by [email protected] |
|
0 likes, 2 repeats |
|
|
|
Absolutely disgusting that resolving DNS via 1.1.1.1 is quicker by 9ms than usi… |
|
|
|
Post #AxYyP3d4Jm6AaNJn5k by [email protected] |
|
0 likes, 2 repeats |
|
|
|
@theodric dnsmasq does itself need to resolv.Try to resolv something that is ca… |
|
|
|
Post #Axb1y5YtoQ5utUgRcm by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@selea it's set up for caching, and I was using dnspyre to repeatedly check… |
|
|
|
Post #Axb282hPJKViuYPS2y by [email protected] |
|
0 likes, 0 repeats |
|
|
|
No way, @theodric, querying names from my local resolver takes 0 ms, and it'… |
|
|
|
Post #Axb282o8uHtlFRYpXs by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@cnx if you're seeing 0ms then it's local memory cache on your host. Ev… |
|
|
|
Post #Axb2T8N5PtRkaIxgy8 by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@theodric Did you try to disable DNSSEC? |
|
|
|
Post #Axb5HsyacAopVxpcYq by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@selea not explicitly, but I did try upstream resolvers that don't support … |
