Skip to content

LookupSession CNAME handling is broken #212

@ibauersachs

Description

@ibauersachs

A query for example.com./A may be answered with a CNAME. The target of the CNAME can (and often is) in the same message, even over multiple CNAMEs. The current assumption that this is illegal is wrong.

  • Fix the assumption with the RFC reference
  • Fix that multiple queries are sent if the original answer contains all responses
    • with a Cache
    • without Cache or TTL=0

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions