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

RPZ: put SOA in modified responses #8232

Closed
Habbie opened this issue Aug 26, 2019 · 3 comments · Fixed by #12883
Closed

RPZ: put SOA in modified responses #8232

Habbie opened this issue Aug 26, 2019 · 3 comments · Fixed by #12883
Assignees
Milestone

Comments

@Habbie
Copy link
Member

Habbie commented Aug 26, 2019

  • Program: Recursor
  • Issue type: Bug report

Short description

When Recursor modifies a response as instructed by an RPZ, it should include the SOA of the RPZ zone in the Additional section of the response, as instructed by the last paragraph of https://tools.ietf.org/html/draft-vixie-dnsop-dns-rpz-00#section-6

Environment

  • Operating system: Debian buster
  • Software version: git master @ b348322
  • Software source: compile from git

Steps to reproduce

  1. set up RPZ (I used the steps from RPZ: ENTs do not prevent wildcard expansion #8231)
  2. send a query (like foo.2o7.net) that would be modified by the RPZ

Expected behaviour

NXDOMAIN + SOA in additional.

Actual behaviour

NXDOMAIN without SOA.

Other information

Usecase

Description

@omoerbeek omoerbeek added this to the rec-5 milestone Feb 5, 2021
@aj-gh
Copy link
Contributor

aj-gh commented Jun 24, 2021

This would likely also help dnsdist to cache these answers (when running in front) ...

@chbruyand
Copy link
Member

This would likely also help dnsdist to cache these answers (when running in front) ...

Hi ! Do you have anything specific in mind ? As far as I know, dnsdist doesn't care about the content of the response regarding caching it or not.

@rgacogne
Copy link
Member

dnsdist kind of does, because it tries to get the minimum TTL of the response to determine how long it can cache it, and at the moment it refuses to cache an answer without any TTL at all to prevent caching a response forever. What we could do would be to use maxNegativeTTL when an answer has no record at all. It would be a breaking change but as long as we document it I'm fine with it.
Of course that only fixes it for dnsdist, so we might still want to return a SOA in RPZ-generated answers, which is the expected behaviour according to the current version of the RPZ specifications.

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

Successfully merging a pull request may close this issue.

6 participants