Always return most relevant error message for CNAME entry

Open Beginner friendly
#1,246 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api

Research direction

Read the CNAME validation and conflicting-entry checks, then find the tests covering CNAME errors. Add or update a test for an empty subname when conflicting entries are present. Done means that case always returns CNAME RRset cannot have empty subname. and does not report the conflicting-entry error.

Written by the indexing model from the issue text.

Description

api enhancement prio: low

According to this forum thread the error message of a CNAME entry with empty subname should always be CNAME RRset cannot have empty subname..

The check for conflicting entries should be skipped (RRset with conflicting type present at same subname: database (MX, NS, TXT). (No other RRsets are allowed alongside CNAME.)) because an empty subname is not possible at all. So the conflicting entries do not matter.

Dominant language
Python
Stars
678
Forks
74
Avg merge
7d 23h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from desec-io/desec-stack

All issues in desec-io/desec-stack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.