Skip to content

Implement message body parsing for types #31

Closed

Description

@clue

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

Activity

  1. WyriHaximus commented on Nov 21, 2015

    @WyriHaximus
    Member

    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.

  2. clue commented on May 20, 2016

    @clue
    MemberAuthor

    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.

  3. added this to the v0.4.15 milestone on Jun 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions