Wrong dns response?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 173
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Using Linux dig:
dig @127.0.0.1 example.com
In response say:
;; WARNING: recursion requested but not available
;; WARNING: Message has 50 extra bytes at end
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with Linux dig using dig @127.0.0.1 example.com, then trace the DNS response handling that produces the recursion and extra-bytes warnings. The issue does not name a file or test; done should be defined by the expected response behavior and verified against the reported warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100