| ▲ | gumby 5 hours ago | |||||||||||||||||||||||||||||||||||||
We used to just leave that responsibility to the querying host’s own resolver. I don’t fetishize the end-to-end principle (though I come close) so I suppose a recursive resolver service could be a sort of optimization (plenty of ppl look up, say, gmail.google.com so why not cache it). In any case, if all resolvers these days are recursive why mention it? I know this is far from the most important question on the topic of this thread! | ||||||||||||||||||||||||||||||||||||||
| ▲ | toast0 5 hours ago | parent [-] | |||||||||||||||||||||||||||||||||||||
> We used to just leave that responsibility to the querying host’s own resolver. When? I didn't get online until the 90s, but resolv.conf delegating recursion to some other node was the way of the world back then. And still is. Some people do run a recursive resolver locally, but it's not so common afaik. > In any case, if all resolvers these days are recursive why mention it? Quad9 is named as a recursive resolver in contrast to being an authoritative server. Quad9 and the server I run for my domain are both DNS servers, both provide name resolution, but one is recursive and the other isn't. Used to be, you might run one server for both jobs, but that fell out of fashion for good reasons. | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||