Thanks to visit codestin.com
Credit goes to GitHub.com

Skip to content

Comments

fix(dns): return NODATA instead of NXDOMAIN when a name exists with a…#374

Open
lbauer13 wants to merge 2 commits intoacme-dns:masterfrom
lbauer13:fix/nxdomain
Open

fix(dns): return NODATA instead of NXDOMAIN when a name exists with a…#374
lbauer13 wants to merge 2 commits intoacme-dns:masterfrom
lbauer13:fix/nxdomain

Conversation

@lbauer13
Copy link

Return NODATA instead of NXDOMAIN when a name exists with another type

Should fix #373

When a TXT exists for a given name but a resolver queries another type, acme-dns will now return NODATA to prevent the resolver from caching a negative response for further TXT queries.

It still returns NXDOMAIN if the name does not exist at all.

…nother type

acme-dns#373

When a TXT exists for a given name but a resolver queries another type,
acme-dns will now return NODATA to prevent the resolver from caching
a negative response for further TXT queries.

It still returns NXDOMAIN if the name does not exist at all.
@lbauer13
Copy link
Author

Added tests for authoritative name with various types (NOERROR, 0 or 1 answer) vs. non-authoritative name (NXDOMAIN)

@tyami94
Copy link

tyami94 commented Mar 6, 2025

FYI, I think @Yannik already submitted a fix for this with #264, but it never got merged. I think this project is sort-of in maintenance mode at the moment.

@lbauer13
Copy link
Author

lbauer13 commented Mar 7, 2025

Thanks for the pointer.
@Yannik 's patch actually looks better than mine, except for the unit test I added. I hope we can have both merged one day.

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

Successfully merging this pull request may close these issues.

DNS server returns NXDOMAIN when it should not - preventing cache DNS from resolving the challenge

2 participants