I was wondering what kind of tests are of interest in investigating resolver behaviour. I appreciate any feedback on how to begin conducting the tests. Best Regards, Paul Muchene
The first thing that the RSSAC wanted to know was how the various implementations responded to the priming query. But that is very much a surface question. I think the broader question included "what might we learn from looking at the various implementations, how they differ and how they are the same?" For example, if a bug or incompatibility were to surface, we might want to advise the developers or the operators that deploy the code.
On Sep 19, 2019, at 9:52 AM, Paul M <paulitrix@gmail.com> wrote:
I was wondering what kind of tests are of interest in investigating resolver behaviour. I appreciate any feedback on how to begin conducting the tests.
Best Regards,
Paul Muchene _______________________________________________ rssac-caucus mailing list rssac-caucus@icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
Hi Fred, On 19 Sep 2019, at 05:04, Fred Baker <fred@isc.org> wrote:
The first thing that the RSSAC wanted to know was how the various implementations responded to the priming query.
Do you mean how the various resolver implementations form a priming query, or how they interpret the response? The implementations that respond to a priming query are surely just those that are in use in {A...M}-Root.
But that is very much a surface question. I think the broader question included "what might we learn from looking at the various implementations, how they differ and how they are the same?" For example, if a bug or incompatibility were to surface, we might want to advise the developers or the operators that deploy the code.
Is there a list of implementations already in existence, perhaps sorted by some measure of relevance (traffic, end-user population, etc)? If so, has there been any effort to compare the list (or the sorting) with the analogues constructed using traffic received at TLD servers? It seems like the difference, if there is any, might indicate a subset of root-specific concerns. I appreciate if I had been paying attention recently I might already know the answers to these questions, so sorry about that :-) Joe
I've been designing a framework called DNSCatcher that does exactly this. It's been a spare time project but I'm hoping to get funding and a grant to basically determine how recursive resolvers behave, as well as understand how DNS looks from Internet end points: https://github.com/DNSCatcher/DNSCatcher/blob/master/doc/technical_overview.... At the moment, I've been dealing with some serious health issues since ICANN65 concluded and only now just beginning to get back on my feet and hopefully resume development. Any feedback is welcome. Michael On 9/19/19 2:52 AM, Paul M wrote:
I was wondering what kind of tests are of interest in investigating resolver behaviour. I appreciate any feedback on how to begin conducting the tests.
Best Regards,
Paul Muchene
_______________________________________________ rssac-caucus mailing list rssac-caucus@icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (4)
-
Fred Baker -
Joe Abley -
Michael Casadevall -
Paul M