Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Response Policy Zone: disabling "leaking" of lookups

132 views
Skip to first unread message

Fred Morris

unread,
Sep 2, 2020, 8:47:27 PM9/2/20
to bind-...@lists.isc.org, dnsfirewalls

It comes to my attention that when an unresolvable query occurs, it gets forwarded to the authoritative zone regardless of anything I can set in named.conf. Closest I can come is qname-wait-recurse which has the opposite effect sort of, namely waiting for recursion to complete. If I have something in an RPZ, I want it to accept that; period, full stop, no outwardly visible effects.

Ironically the text surrounding this option in the ARM is to the effect that "... not resolving the requested name can leak the fact that response policy rewriting is in use..." and leaking the fact that it is in use by not leaking the query in the first place is what I'm trying to achieve: how do I disable the (useless) resolution directed at upstream servers?

Here is a use case:

  1. A search list is in place for example.com. This means that if "foo.bar" fails to resolve then "foo.bar.example.com" will be tried, followed by "foo.bar.com".
  2. In addition to the foregoing a rule is placed in the RPZ that "com.example.com" and "*.com.example.com" are NXDOMAIN.
  3. An additional rule is present in the RPZ that "my-outhouse-example.com" is NXDOMAIN.

In this case:

Let's stop the leaks.

--

Fred Morris


Carl Byington

unread,
Sep 2, 2020, 11:23:44 PM9/2/20
to bind-...@lists.isc.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, 2020-09-02 at 17:47 -0700, Fred Morris wrote:
> how do I disable the (useless) resolution directed at upstream
> servers?

Isn't that just "qname-wait-recurse no;"


-----BEGIN PGP SIGNATURE-----

iHMEAREKADMWIQSuFMepaSkjWnTxQ5QvqPuaKVMWwQUCX1BhpBUcY2FybEBmaXZl
LXRlbi1zZy5jb20ACgkQL6j7milTFsFe7gCfVN8JVwC8eQ5RExIYVJkOVf3Ywc4A
n1pCBkinzCzqBH9IYlXfp5sNeNh1
=Zfin
-----END PGP SIGNATURE-----


pvm_job

unread,
Sep 3, 2020, 12:34:58 PM9/3/20
to Fred Morris, dnsfirewalls, bind-...@lists.isc.org
It is a well known behaviour.  This is the way how your DNS client works (not DNS server).
Get rid of the search list or block requests to the domains in the search lists by RPZ (e.g. if it is pushed by ISP).
 
BR,
Vadim
Четверг, 3 сентября 2020, 19:04 +03:00 от Fred Morris <m3...@m3047.net>:
 
_______________________________________________
DNSfirewalls mailing list
DNSfir...@lists.redbarn.org
http://lists.redbarn.org/mailman/listinfo/dnsfirewalls
 
 
 
 
 

Fred Morris

unread,
Sep 3, 2020, 2:45:17 PM9/3/20
to bind-...@lists.isc.org, dnsfirewalls
Carl Byington wrote:
> On Wed, 2020-09-02 at 17:47 -0700, Fred Morris wrote:
> > how do I disable the (useless) resolution directed at upstream
> > servers?
>
> Isn't that just "qname-wait-recurse no;"
>
You are correct! I got confused and the doc didn't help. The logic is
tri-state:

*Default* (not present): The lookup is performed, but isn't waited for.

*Yes*: Resolution waits for the lookup to complete.

*No*: Resolution is not performed.


Verified by testing. :-) Thanks for the sanity check.

--

Fred Morris


0 new messages