Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support NODATA (NSEC/NSEC3 use case) #1615

Open
xinbenlv opened this issue Nov 5, 2024 · 1 comment
Open

Support NODATA (NSEC/NSEC3 use case) #1615

xinbenlv opened this issue Nov 5, 2024 · 1 comment

Comments

@xinbenlv
Copy link

xinbenlv commented Nov 5, 2024

For use case of NSEC/NSEC3 it seems a requirement to support NODATA, and this repo doesn't yet.

See the latest RFC 9077 it reads

[[RFC2308](https://datatracker.ietf.org/doc/html/rfc2308)] defines the TTL of the
Start of Authority (SOA) record that must be returned in negative answers
(NXDOMAIN or NODATA):

Case:

We are trying to deny existence of MX records or TXT records of a domain and only to found that CoreDNS doesn't support NODATA. After digging, I found that it's due to the dependency of this repo from

See

Previously the request within this repo to support NODATA is in #428

@xinbenlv xinbenlv changed the title Support NODATA Support NODATA (NSEC use case) Nov 5, 2024
@xinbenlv xinbenlv changed the title Support NODATA (NSEC use case) Support NODATA (NSEC/NSEC3 use case) Nov 5, 2024
@Chreo
Copy link
Contributor

Chreo commented Nov 14, 2024

I trust you are aware that "NODATA" is not a defined RCODE (https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6)
When we say "NODATA" that is pseudo for NOERROR RCODE with an empty ANSWER section
That said, it could be potentially useful to have a helper function for DNS messages being defined as:
func (m Msg) IsNODATAResponse() bool
but as with anything, code talks...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants