[feat] Add SRV and CAA record support to DNS lookup
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- backend, networking
Research direction
Start in lib/services/dns_client.dart: read DnsQueryType and _parseRdata, then follow _Reader.name() for compressed DNS names. Add captured-packet tests under test/ for SRV, CAA, and a truncated or malformed record. Done means the query types are selectable, parsed values are human-readable, existing output stays unchanged, and flutter test passes.
Written by the indexing model from the issue text.
Description
DnsQueryType currently supports A/AAAA/CNAME/MX/NS/TXT/SOA (lib/services/dns_client.dart), and _parseRdata already decodes NS and SOA. SRV (33) and CAA (257) fall through to the hex dump and cannot be selected in the UI.
Scope
- Extend the
DnsQueryTypeenum withsrv(33, 'SRV')andcaa(257, 'CAA')(the record-type chips iterate the enum, so no UI change is needed). - Add RDATA parsing in
_parseRdata:- SRV:
priority,weight,port,target(reuse the existing_Reader.name()decoder; it handles pointer compression), - CAA: flags byte, length-prefixed ASCII tag, remaining bytes as the value; render like
0 issue "letsencrypt.org".
- SRV:
- Unit tests from captured response packets: one SRV, one CAA, plus a truncated/bad record case.
- No new dependencies.
Acceptance criteria
flutter testpasses with the new parser tests.- Querying an SRV and a CAA record shows human-readable values instead of a hex dump.
- Existing record types keep their current output.
Files
lib/services/dns_client.darttest/(new parser tests)
- Dominant language
- Dart
- Stars
- 15
- Forks
- 1
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from Cadman021/VeloceNet-Studio
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Cadman021/VeloceNet-Studio#12 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted i18n
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Cadman021/VeloceNet-Studio#10 ·
Maintainers usually reply within 1 day
-
enhancement good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Cadman021/VeloceNet-Studio#3 ·
Maintainers usually reply within 1 day
-
bug enhancement good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Cadman021/VeloceNet-Studio#2 ·
Maintainers usually reply within 1 day
-
enhancement good first issue UI
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Cadman021/VeloceNet-Studio#34 ·
Maintainers usually reply within 1 day
All issues in Cadman021/VeloceNet-Studio
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
espresso3389/pdfrx#776 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
atsign-foundation/at_server#2896 ·
Maintainers usually reply within 1 day
-
backlog:low bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simonoppowa/OpenNutriTracker#1445 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lugassawan/swe-workbench#823 ·
Maintainers usually reply within 1 day
-
auto-implement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bannzai/kashakeibo#142 · 1 comment ·
Maintainers usually reply within 1 day