This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] Thoughts on allowing newer DNS RR queries?
- Previous message (by thread): [atlas] Thoughts on allowing newer DNS RR queries?
- Next message (by thread): [atlas] Thoughts on allowing newer DNS RR queries?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Delany
f4w at echo.emu.st
Thu Feb 20 19:29:50 CET 2014
On 20Feb14, Antony Antony allegedly wrote: > Hi Mark, > what is the specific RR query you are looking for? > > currently we support a bunch of them UDP or TCP. Here is a list. > > in class IN > A, AAAA, ANY, CNAME, DS, DNSKEY, MX, NS, NSEC, NSEC3, PTR, RRSIG, SOA, SRV, NAPTR. > > class CHAOS > hostname.bind, id.server, version.bind, version.server Don't ask me why I made such a goof, but for some reason when I checked I thought I only saw a couple of types. Sorry. To answer your question, it wasn't a particular type I had in mind, it was more trying to ask the question of how well the infrastructure deals with new types. In the bad old days introducing a new type was deemed risky because a lot of middleware, such as caches and firewalls had type-specific code. I was wanting to test the claim that most modern middleware is type-oblivious and "just works" with new types. So ideally, it would be a type that doesn't exist or one that has just recently been published. Mark.
- Previous message (by thread): [atlas] Thoughts on allowing newer DNS RR queries?
- Next message (by thread): [atlas] Thoughts on allowing newer DNS RR queries?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]