What’s slow about it??
{19:52}~ ➭ dig @192.168.0.1 slashdot.org | grep time
;; Query time: 10 msec
{19:52}~ ➭ dig @192.168.0.1 slashdot.org | grep time
;; Query time: 0 msec
{19:52}~ ➭ dig @192.168.0.1 bbc.co.uk | grep time
;; Query time: 300 msec
{19:53}~ ➭ dig @192.168.0.1 bbc.co.uk | grep time
;; Query time: 0 msec
It takes 10ms for it to lookup slashdot the first time, after that it’s cached and it takes 0ms.
bbc.co.uk takes 300ms first time, because it’s not in my ISPs cache. After that it caches it, again 0ms.
The 300ms is the correct time, I query my ISPs resolvers and they take ~300ms to look it up, I’m in NZ and has to go over to the US/UK to resolve.
What’s slow here? It’s just as performant as querying my ISPs namesevers, except once it’s cached it, it’s 0ms instead of the 10ms trip time it is to them each time.
This bizzare idea people seem to have that one caching nameserver is “so slow” compared to another. Even if one was 10ms slower than the other, are you really going to tell me you/your users are going to notice 10ms on each lookup?
I keep reading on multiple various forums people saying “X resolver is slow” but they never back it up with any evidence. There was a thread here that discussed it too but it never went anywhere, just someone “feeling it was slow”
I’m happy to be shown I’m wrong, by the way. But what’s slow about powerdns? How is mosdns that much faster?