Implement message body parsing for types

Question

Implement message body parsing for types

clue opened this issue 9 years ago · 2 comments

Implement message body parsing for types other than A and CNAME: NS, SOA, PTR, MX, TXT, AAAA

Answer 1 · 2015-11-21T19:15:28.000Z

Out of interest how would you chose when to get an A or an AAAA? Don't want to us try and use an AAAA record on an IPv4 only connection or vice versa. Not sure if this is the right place to discuss that but it seems to be the most relevant.

Answer 2 · 2016-05-20T15:24:10.000Z

Out of interest how would you chose when to get an A or an AAAA?

This ticket mainly focuses on implementing an API that allows fetching A or AAAA records. Both can be useful even if you're not using a dual stack connection.

In a follow-up ticket we should address how users can select which type should be preferred by default. We may likely end up with an additional method to define that IPv6 is preferred over IPv4.