-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
rfc:rpz (draft) for having full support of rpz zones and always_nxdomain #74
Comments
Hi, |
Yes 👍
Will do this later, as unbound is on a diff PC |
Found the line in a local file added to the config 👍 now I have to figure out why... but that not your headache By the way... I can see you are working on integrating full support for RPZ zones in this PR Do you have any idea for the release date ❓ and do you have docs on the layouts for the RPZ zone files?. I would hate to make a lot of code just to remake it in 2 weeks 😒 |
Closing this as RPZ is fully supported since 1.14.0 |
intro:
I'm building a project to hosts public owned RPZ zones.
The issue is the way unbound handles
always_nxdomain
as demonstrated in this threadunbound is not only adding nxdomain from second level domains and down the latter, it also doing so in the opposed direction from fourth or fifth level domains to the second level
Now the question/feature request:
Is there currently a work around for this issue to use the
always_nxdomain
or actually full support for real RPZ zones, rather than having to build very very big files withOuttro
The main idea with my project is to fully implant the NXDOMAIN as they smarter and faster as you have a straight-up answer and wildcard is fully supporter, any DNS queries don't have to wait up for any redirection timeouts ex. 127.0.0.1 or 0.0.0.0
I'm asking you here as (personal linux) Unbound is the only reliable recursor I have found that could be easily installed on Windows 10.Home.xxxxxxxxxxxxxxx.what.ever.hosts.reset.version.tracking.optimization.version
Ping for inclusion
@ScriptTiger
The text was updated successfully, but these errors were encountered: