Periodic since 2.2 pages load blank, certs invalid
-
Couple more of the hardened stuff here: https://forum.pfsense.org/index.php?topic=88466.msg488511#msg488511
- harden-referral-path is hardcoded to no in unbound.inc ATM :(
- harden-below-nxdomain can be set via the advanced config
(created a feature request for the two above)
- there's also this use-caps-for-id thing (patch to expose in GUI in 4205 or stick use-caps-for-id: yes to advanced config.
Another thing that makes me wonder… dnsmasq AFAICT is not compiled with DNSSEC support at all on pfSense even though it's apparently supported now. Hmmm. And of course, no matter what you are completely screwed with unsigned domains, and the DNS protocol is a piece of insecure crap.
A couple of suggestions for your own servers:
- sign your domains (ahem… why's pfsense.org not signed?!)
- if your registrar does not allow you to do so, switch registrar
- if the TLD you are using is not signed, choose a different one
- use DANE/TLSA for your critical servers at least.
Some useful tools:
-
DNSSEC Test - check your resolvers
-
DNSSEC Analyzer - check your domain for DNSSEC problems
-
Update for our situation (only dns active, harden glue settings not (yet) updated).
The situation happened again a few minutes ago, and here it is how it looked in the resolver.log (first time "csof" is visible today) :Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for 239.75.246.46.in-addr.arpa. PTR IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <75.246.46.in-addr.arpa.> 91.213.246.6#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns1.transitionalprotocol.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns2.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving f.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving g.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving k.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving l.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns2.transitionalprotocol.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving h.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving i.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns1.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving m.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving d.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: response for a.ns.portlane.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <portlane.net.>80.67.0.6#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for b.ns.portlane.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <portlane.net.>80.67.0.6#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for 125.10.113.188.in-addr.arpa. PTR IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <10.113.188.in-addr.arpa.> 80.240.240.2#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: resolving 113.188.in-addr.arpa. DS IN Feb 10 10:03:18 pf unbound: [24807:1] notice: sendto failed: Operation not permitted Feb 10 10:03:18 pf unbound: [24807:1] notice: remote address is 2001:500:13::c7d4:35 port 53 Feb 10 10:03:18 pf unbound: [24807:1] info: error sending query to auth server 2001:500:13::c7d4:35 port 53 Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns1.transitionalprotocol.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.52.178.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns2.csof.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving ns1.csof.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving e.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: resolving d.gtld-servers.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.52.178.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:0] info: response for 125.74.1.116.in-addr.arpa. PTR IN Feb 10 10:03:18 pf unbound: [24807:0] info: reply from <1.116.in-addr.arpa.> 202.103.224.69#53 Feb 10 10:03:18 pf unbound: [24807:0] info: query response was NXDOMAIN ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.transitionalprotocol.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.26.92.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <transitionalprotocol.net.>212.6.183.201#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns1.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.31.80.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.csof.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.43.172.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.transitionalprotocol.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <transitionalprotocol.net.>212.6.183.201#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for 113.188.in-addr.arpa. DS IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <188.in-addr.arpa.> 199.212.0.53#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: NSEC RRset for the referral proved not a delegation point Feb 10 10:03:18 pf unbound: [24807:1] info: NSEC RRset for the referral proved no DS. Feb 10 10:03:18 pf unbound: [24807:1] info: Verified that unsigned response is INSECURE Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns1.transitionalprotocol.net. A IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <transitionalprotocol.net.>54.77.72.254#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns1.csof.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <net.>192.26.92.30#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:18 pf unbound: [24807:1] info: response for 239.75.246.46.in-addr.arpa. PTR IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <239.75.246.46.in-addr.arpa.> 195.22.26.248#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:18 pf unbound: [24807:1] info: resolving 246.46.in-addr.arpa. DS IN Feb 10 10:03:18 pf unbound: [24807:1] info: NSEC RRset for the referral proved not a delegation point Feb 10 10:03:18 pf unbound: [24807:1] info: NSEC RRset for the referral proved no DS. Feb 10 10:03:18 pf unbound: [24807:1] info: Verified that unsigned response is INSECURE Feb 10 10:03:18 pf unbound: [24807:1] info: response for ns2.csof.net. AAAA IN Feb 10 10:03:18 pf unbound: [24807:1] info: reply from <csof.net.>208.109.255.32#53 Feb 10 10:03:18 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:18 pf unbound: [24807:0] info: response for 166.31.215.188.in-addr.arpa. PTR IN Feb 10 10:03:18 pf unbound: [24807:0] info: reply from <31.215.188.in-addr.arpa.> 89.39.166.2#53 Feb 10 10:03:18 pf unbound: [24807:0] info: query response was THROWAWAY Feb 10 10:03:19 pf unbound: [24807:1] info: response for ns1.csof.net. AAAA IN Feb 10 10:03:19 pf unbound: [24807:1] info: reply from <csof.net.>208.109.255.32#53 Feb 10 10:03:19 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:19 pf unbound: [24807:1] info: resolving 205.112.194.173.in-addr.arpa. PTR IN Feb 10 10:03:19 pf unbound: [24807:1] info: resolving ns2.google.com. AAAA IN Feb 10 10:03:19 pf unbound: [24807:1] info: resolving ns4.google.com. AAAA IN Feb 10 10:03:19 pf unbound: [24807:1] info: resolving ns1.google.com. AAAA IN Feb 10 10:03:19 pf unbound: [24807:1] info: response for ns1.transitionalprotocol.net. AAAA IN Feb 10 10:03:19 pf unbound: [24807:1] info: reply from <transitionalprotocol.net.>212.6.183.201#53 Feb 10 10:03:19 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:19 pf unbound: [24807:1] info: response for 205.112.194.173.in-addr.arpa. PTR IN Feb 10 10:03:19 pf unbound: [24807:1] info: reply from <194.173.in-addr.arpa.> 216.239.36.10#53 Feb 10 10:03:19 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:20 pf unbound: [24807:1] info: resolving www.insign.ch. A IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving dns2.insign.ch. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving dns1.insign.ch. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: response for www.insign.ch. A IN Feb 10 10:03:20 pf unbound: [24807:1] info: reply from <insign.ch.>46.175.9.120#53 Feb 10 10:03:20 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:20 pf unbound: [24807:1] info: NSEC3s for the referral proved no DS. Feb 10 10:03:20 pf unbound: [24807:1] info: Verified that unsigned response is INSECURE Feb 10 10:03:20 pf unbound: [24807:1] info: resolving 64.94.172.95.in-addr.arpa. PTR IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns-b.pnap.net. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns-c.pnap.net. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns-a.pnap.net. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving 185.112.194.173.in-addr.arpa. PTR IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns3.google.com. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns4.google.com. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: resolving ns1.google.com. AAAA IN Feb 10 10:03:20 pf unbound: [24807:1] info: response for 185.112.194.173.in-addr.arpa. PTR IN Feb 10 10:03:20 pf unbound: [24807:1] info: reply from <194.173.in-addr.arpa.> 216.239.32.10#53 Feb 10 10:03:20 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:20 pf unbound: [24807:1] info: response for 64.94.172.95.in-addr.arpa. PTR IN Feb 10 10:03:20 pf unbound: [24807:1] info: reply from <94.172.95.in-addr.arpa.> 64.95.61.4#53 Feb 10 10:03:41 pf unbound: [24807:0] info: query response was REFERRAL Feb 10 10:03:41 pf unbound: [24807:0] info: resolving dns4.bigrock.in. AAAA IN Feb 10 10:03:41 pf unbound: [24807:0] info: resolving dns2.bigrock.in. AAAA IN Feb 10 10:03:41 pf unbound: [24807:0] info: resolving asia1.akam.net. AAAA IN Feb 10 10:03:41 pf unbound: [24807:0] notice: sendto failed: Operation not permitted Feb 10 10:03:41 pf unbound: [24807:0] notice: remote address is 2600:1401:2::43 port 53 Feb 10 10:03:41 pf unbound: [24807:0] info: error sending query to auth server 2600:1401:2::43 port 53 Feb 10 10:03:41 pf unbound: [24807:1] info: response for ns0.mirasystem.net. A IN Feb 10 10:03:41 pf unbound: [24807:1] info: reply from <net.>54.72.8.183#53 Feb 10 10:03:41 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:42 pf unbound: [24807:0] info: response for asia1.akam.net. AAAA IN Feb 10 10:03:42 pf unbound: [24807:0] info: reply from <akam.net.>184.85.248.67#53 Feb 10 10:03:42 pf unbound: [24807:0] info: query response was nodata ANSWER Feb 10 10:03:42 pf unbound: [24807:0] info: response for dns2.bigrock.in. AAAA IN Feb 10 10:03:42 pf unbound: [24807:0] info: reply from <bigrock.in.>2.22.230.64#53 Feb 10 10:03:42 pf unbound: [24807:0] info: query response was nodata ANSWER Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns1.epn.ru. A IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <epn.ru.>195.22.26.248#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns0.epn.ru. AAAA IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <epn.ru.>195.22.26.248#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns0.epn.ru. A IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <epn.ru.>195.22.26.248#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was ANSWER Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns1.epn.ru. AAAA IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <epn.ru.>195.22.26.248#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was nodata ANSWER Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns1.hn.cnc.cn. AAAA IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <cnc.cn.>210.52.207.2#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns1.hn.cnc.cn. A IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <cnc.cn.>210.52.207.2#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns2.hn.cnc.cn. A IN Feb 10 10:03:42 pf unbound: [24807:1] info: reply from <cnc.cn.>210.52.207.2#53 Feb 10 10:03:42 pf unbound: [24807:1] info: query response was REFERRAL Feb 10 10:03:42 pf unbound: [24807:1] info: response for ns2.hn.cnc.cn. AAAA IN</cnc.cn.></cnc.cn.></cnc.cn.></epn.ru.></epn.ru.></epn.ru.></epn.ru.></bigrock.in.></akam.net.></net.></insign.ch.></transitionalprotocol.net.></csof.net.></csof.net.></net.></transitionalprotocol.net.></transitionalprotocol.net.></net.></net.></transitionalprotocol.net.></net.></net.></net.></portlane.net.></portlane.net.>At the end, all requests get resolved as "195.22.26.248".
Trigger request couldn't yet be found (the log rule on port 53 for requests not going over the router returned nothing at this moment).So when it starts, every single request then go over one of these ns1.csof.net name server, and get answered as if csof.net was a root server, but with wrong data. For example:
Normal case when querying the pfsense resolver (when everything is ok) :
om@ompc:~> dig -t ns @192.168.1.100 ch. ; <<>> DiG 9.9.5-rpz2+rl.14038.05-P1 <<>> -t ns @192.168.1.100 ch. ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62805 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 14 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;ch. IN NS ;; ANSWER SECTION: ch. 85292 IN NS c.nic.ch. ch. 85292 IN NS b.nic.ch. ch. 85292 IN NS e.nic.ch. ch. 85292 IN NS d.nic.ch. ch. 85292 IN NS a.nic.ch. ch. 85292 IN NS h.nic.ch. ch. 85292 IN NS f.nic.ch. ;; ADDITIONAL SECTION: a.nic.ch. 171692 IN A 130.59.1.80 a.nic.ch. 171692 IN AAAA 2001:620::4 b.nic.ch. 171692 IN A 130.59.211.10 b.nic.ch. 171692 IN AAAA 2001:620::5 c.nic.ch. 171692 IN A 147.28.0.39 c.nic.ch. 171692 IN AAAA 2001:418:1::39 d.nic.ch. 171692 IN A 200.160.0.5 d.nic.ch. 171692 IN AAAA 2001:12ff:0:a20::5 e.nic.ch. 171692 IN A 194.0.17.1 e.nic.ch. 171692 IN AAAA 2001:678:3::1 f.nic.ch. 171692 IN A 194.146.106.10 f.nic.ch. 171692 IN AAAA 2001:67c:1010:2::53 h.nic.ch. 171692 IN A 194.42.48.120 ;; Query time: 0 msec ;; SERVER: 192.168.1.100#53(192.168.1.100) ;; WHEN: Tue Feb 10 10:55:52 CET 2015 ;; MSG SIZE rcvd: 427When querying this ns1.csof.net server :
om@ompc:~> dig -t ns @ns1.csof.net ch. ; <<>> DiG 9.9.5-rpz2+rl.14038.05-P1 <<>> -t ns @ns1.csof.net ch. ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45232 ;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;ch. IN NS ;; ANSWER SECTION: ch. 172800 IN NS ns1.csof.net. ch. 172800 IN NS ns2.csof.net. ch. 172800 IN NS ns3.csof.net. ch. 172800 IN NS ns4.csof.net. ;; ADDITIONAL SECTION: ns1.csof.net. 100 IN A 54.77.72.254 ns2.csof.net. 100 IN A 212.6.183.201 ns3.csof.net. 100 IN A 195.22.26.199 ns4.csof.net. 100 IN A 54.72.8.183 ;; Query time: 54 msec ;; SERVER: 54.77.72.254#53(54.77.72.254) ;; WHEN: Tue Feb 10 10:45:26 CET 2015 ;; MSG SIZE rcvd: 164I now increased the verbosity of unbound with "unbound-control -c /var/unbound/unbound.conf verbosity 4" and waiting for another hit… If you have other suggestions in the mean time, please feel free.
-
Does that mean you have already made all the suggested changes?
-
Does that mean you have already made all the suggested changes?
Apparently not.
Update for our situation (only dns active, harden glue settings not (yet) updated).
People, by all means feel free to experiment if its your network. However, mind that if there are any unsuspecting users behind your router using your resolver, this is not the best idea around. Noone likes getting their boxes infected via malicious pages served via the subverted DNS, getting their banking info compromised etc.!
-
Does that mean you have already made all the suggested changes?
(if the question is for me) : no, as we would first would like to find out what/who is triggering this phenomena. But we'll change the setup then (today before the evening) and report again.
-
Yeah - Please do find out. Its a mystery for me.
-
Activating following settings (as suggested previously in this thread) seems to solve the issue for now, at least for the last 3 hours :
harden-glue: yes harden-dnssec-stripped: yesIn the mean time I have a 500 MB resolver.log in "verbose=5" mode to analyze.
-
With the great support of Wouter Wijngaards from the Unbound-Dev-Team this issue can be considered as closed, at least on our side.
Activating "harden-glue: yes" and "harden-dnssec-stripped: yes" was the solution, or a patch can be applied to fix this situation without enabling these options.@Wouter:
Hi Martin, Olivier,
I have found the issue, it is in unbound. You have turned off
harden-glue in config and this disabled the poison checks (that is its
purpose) and caused the poisoning. The domain is not an attack domain
I think but a domain-reseller.Turn on harden-glue: yes in unbound.conf
Also this patch may solve the problem (and you can continue to use
harden-glue: no). Note that harden-glue no allows people (not this
specific attack) to poison nameserver glue records and then poison
your cache as well, also with the patch.Index: iterator/iter_scrub.c
–- iterator/iter_scrub.c (revision 3329)
+++ iterator/iter_scrub.c (working copy)
@@ -680,7 +680,9 @@
* (we dont want its glue that was approved
* during the normalize action) /
del_addi = 1;
- } else if(!env->cfg->harden_glue) {
+ } else if(!env->cfg->harden_glue && (
+ rrset->type == LDNS_RR_TYPE_A ||
+ rrset->type == LDNS_RR_TYPE_AAAA)) {
/ store in cache! Since it is relevant
* (from normalize) it will be picked up
* from the cache to be used later */Why was harden-glue turned off? And perhaps I should change
documentation or implementation of this misfeature?Best regards,
WouterMore information from the Unbound-Users mailing list : https://unbound.nlnetlabs.nl/pipermail/unbound-users/2015-February/003768.html
Suggestion for pfSense 2.2.1 : apply this patch to unbound and/or activate the harden-options by default. I'll check later if there is anything in redmine about this issue or will create a new one accordingly.
Thanks again for your fast and helpful answers on this forum & I hope it will remain stable this way ! Now I can get back to my IPSEC issues :-)
Kind regards.PS: about the trigger :
> (...) could you see which host/device caused this issue ? Yes, the offending query was for ns2.transitionalprotocol.net A. The logs are missing lines (the logger seems to skip lines when presented at a high rate). That query was made to resolve another query for 105.73.246.46.in-addr.arpa. PTR. And this was requested by Feb 10 11:48:15 pf unbound: [68609:0] debug: udp request from ip4 192.168.1.150 port 62403 (len 16) The query for that reverse address seems innocent. -
@Wouter:
Why was harden-glue turned off?
Indeed, this is a good question, keeping in mind that unbound is enabled by default in all new 2.2 installations, I wonder how many unsuspecting people are being affected by this.
I feel that it warrants an official announcement by pfSense team with specific suggestions on how to remedy the issue… -
I'd say applying that patch AND enabling harden glue by default would probably be the safest option considering the havoc this was able to cause.
In the mean time, even with harden glue on, I'm going to keep my 0.0.0.0 overrides ;)
-
Suggestion for pfSense 2.2.1 : apply this patch to unbound and/or activate the harden-options by default. I'll check later if there is anything in redmine about this issue or will create a new one accordingly.
Voilà : https://redmine.pfsense.org/issues/4402
-
harden-glue is already on by default in RELENG_2_2:
https://redmine.pfsense.org/projects/pfsense/repository/revisions/ef120e878558f84ed14369a484c0938ccd1b6db5
(The iter_scrub.c patch still useful though…)
-
I just started getting this problem today for the first time since I installed the 2.2-RELEASE.
I was also using the 8.8.8.8 and 8.8.4.4 DNS from Google. I've changed to using OpenDNS now which seems to have stopped the problem?
The thread is really long I read the first few pages, should I activate the Harden Glue feature? - Just a worried noobie.
-
Harden Glue - yes, that definitely should be enabled. Otherwise, OpenDNS does not support DNSSEC at all, so all those other DNSSEC-related hardening features are kinda useless till you switch back to Google, or just disable the forwarding altogether.
-
Ok so I've turned Hardened Glue on, what else should I enable?
-
@cmb:
Have you tried checking:
Harden Glue
Harden DNSSEC data
These two in particular, if you don't have them enabled, enable them. I changed things to enable both those by default, and we'll add config upgrade code to turn those on for anyone who doesn't have them enabled upon upgrade to 2.2.1.
-
@cmb:
Have you tried checking:
Harden Glue
Harden DNSSEC data
These two in particular, if you don't have them enabled, enable them. I changed things to enable both those by default, and we'll add config upgrade code to turn those on for anyone who doesn't have them enabled upon upgrade to 2.2.1.
Okay I've enabled both of those. They will work okay with OpenDNS? - Thanks :)
-
-
They will work okay with OpenDNS? - Thanks :)
Goto…
I read that but I just wanted to confirm because I wasn't sure if you mistyped what you said due to the way it was worded.
-