From m3047 at m3047.net Thu Sep 3 00:47:09 2020 From: m3047 at m3047.net (Fred Morris) Date: Wed, 2 Sep 2020 17:47:09 -0700 Subject: [DNSfirewalls] Response Policy Zone: disabling "leaking" of lookups Message-ID: 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: * "my-outhouse-example.com.example.com" will return NXDOMAIN (it does!) * There should be /no/ upstream (pointless) query for my-outhouse-example.com.example.com. (oops!) Let's stop the leaks. -- Fred Morris -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvm_job at mail.ru Thu Sep 3 16:34:35 2020 From: pvm_job at mail.ru (=?UTF-8?B?cHZtX2pvYg==?=) Date: Thu, 03 Sep 2020 19:34:35 +0300 Subject: [DNSfirewalls] =?utf-8?q?Response_Policy_Zone=3A_disabling_=22le?= =?utf-8?q?aking=22_of_lookups?= In-Reply-To: References: Message-ID: <1599150875.905419497@f707.i.mail.ru> 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 : >? >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: >* 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". >* In addition to the foregoing a rule is placed in the RPZ that "com.example.com" and "*.com.example.com" are NXDOMAIN. >* An additional rule is present in the RPZ that "my-outhouse-example.com" is NXDOMAIN. >In this case: >* "my-outhouse-example.com.example.com" will return NXDOMAIN (it does!) >* There should be no upstream (pointless) query for my-outhouse-example.com.example.com. (oops!) >Let's stop the leaks. >-- >Fred Morris >? >_______________________________________________ >DNSfirewalls mailing list >DNSfirewalls at lists.redbarn.org >http://lists.redbarn.org/mailman/listinfo/dnsfirewalls >? ? ? ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From m3047 at m3047.net Thu Sep 3 18:44:56 2020 From: m3047 at m3047.net (Fred Morris) Date: Thu, 3 Sep 2020 11:44:56 -0700 Subject: [DNSfirewalls] Response Policy Zone: disabling "leaking" of lookups In-Reply-To: <4ef66fdfdcae3d73aa3dd6df1b115fe37ac5675c.camel@byington.org> References: <4ef66fdfdcae3d73aa3dd6df1b115fe37ac5675c.camel@byington.org> Message-ID: <78bc23f4-7163-b4d3-63ef-91a21ddb6c99@m3047.net> 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