hashicorp / hashicorp/consul

Broken response when asking for the SOA record of the consul zone

Open
#1,906 0 comments 0 reactions 0 assignees View on GitHub
theme/api type/bug
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

Expected result: a NOERROR response with the SOA record in the answer section

Actual result on 0.6.4: a NXDOMAIN response with the SOA record in the authority section twice

This probably breaks down into more than one bug in the DNS implementation:
- Obviously this SOA exists, so there shouldn't be any kind of error response
- When I ask for a record that doesn't exist, I still get NXDOMAIN which is still wrong because the name exists. NXDOMAIN should only ever be returned when the requested name has no records _of any kind_ and no existing subdomains. "The name exists but doesn't have records of this type" should be NOERROR with an empty answer section.
- Don't know why the SOA is duplicated but it shouldn't be. This seems to happen only for SOA, asking for TXT or AAAA returns one SOA in the authority section (but still NXDOMAIN which is still wrong).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.