BADCOOKIE (and other EDNS errors, probably) #96

Closed
opened 2022-09-14 23:34:16 +00:00 by sam · 0 comments
Owner

Describe the bug
A clear and concise description of what the bug is.

Reproduction steps
Steps to reproduce the behavior:

❯ awl froth.zone @v0n1.nic.zone
;; opcode: QUERY, status: FORMERR
❯ awl froth.zone @v0n1.nic.zone +nocookie
;; opcode: QUERY, status: NOERROR

Expected behaviour
If a BADCOOKIE is received, awl should restart the query with the correct cookie.

System information (please complete the following information):

  • OS: Ran and failed on Debian and Arch
  • Version: awl version v0.5.0, built with go1.19

Additional context
RFC

**Describe the bug** A clear and concise description of what the bug is. **Reproduction steps** Steps to reproduce the behavior: 1. ``` ❯ awl froth.zone @v0n1.nic.zone ;; opcode: QUERY, status: FORMERR ``` 2. ``` ❯ awl froth.zone @v0n1.nic.zone +nocookie ;; opcode: QUERY, status: NOERROR ``` **Expected behaviour** If a BADCOOKIE is received, `awl` should restart the query with the correct cookie. **System information (please complete the following information):** - OS: Ran and failed on Debian and Arch - Version: `awl version v0.5.0, built with go1.19` **Additional context** [RFC](https://www.rfc-editor.org/rfc/rfc7873.html)
sam added the
bug
Priority: High
labels 2022-09-14 23:34:16 +00:00
sam added a new dependency 2022-09-16 22:51:46 +00:00
sam removed a dependency 2022-09-16 22:55:37 +00:00
sam closed this issue 2022-09-16 23:26:11 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
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: sam/awl#96
No description provided.