[GH-ISSUE #5] AXFR response ordering incorrect #303

Closed
opened 2026-03-15 21:50:46 +03:00 by kerem · 1 comment
Owner

Originally created by @bluejekyll on GitHub (Nov 12, 2015).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/5

dig reports an error with since the SOA record is not the first in the response. This will be fixed as I implement the DNSSec RFC's, where canonical ordering is a requirement.

Originally created by @bluejekyll on GitHub (Nov 12, 2015). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/5 dig reports an error with since the SOA record is not the first in the response. This will be fixed as I implement the DNSSec RFC's, where canonical ordering is a requirement.
kerem 2026-03-15 21:50:46 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@bluejekyll commented on GitHub (Apr 6, 2016):

This was fixed a while back

<!-- gh-comment-id:206394122 --> @bluejekyll commented on GitHub (Apr 6, 2016): This was fixed a while back
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#303
No description provided.