Periodic since 2.2 pages load blank, certs invalid

Trel

We were using 8.8.8.8 and 8.8.4.4

Changed them over to opendns and machines responded almost immediately

That looks like it has a good chance at being the cause then.
I'm going to remove those from my list and just keep the Level3 ones (4.2.2.1 and 4.2.2.2) and see if it ever happens again.

That might also explain why it didn't happen until right after the 2.2 upgrade if dnsmasq had a higher tolerance before falling over to the secondary DNS server than unbound does.

Pakken

God, and I thought I was the only one having this problem since I came up reading this thread.

Any news about that? Same invalid cert, same google dns.
Spent the last night trying to figure out what the he** could have happened.

Trel

@Pakken:

God, and I thought I was the only one having this problem since I came up reading this thread.

Any news about that? Same invalid cert, same google dns.
Spent the last night trying to figure out what the he** could have happened.

Other than us three, I haven't found anyone who reported it anywhere but here.

But it's way too coincidental that three people got the same symptoms and had the same dns.

kejianshi

Me also - Thats main reason I turned off forwarder and turned on unbound on one of my systems.
The kids were reporting same exact issues as you…

Unbound with DNSSEC is technically slower than a forwarder but it seems faster in actual use and the kids report its solid.
I'm also using it over the VPN for my private use.

doktornotor

NSA testing some new (broken) toys? :D

kejianshi

I will just say I like unbound and leave it at that… (-;

Unbound + VPN = my tinfoil hat

Trel

I just had this happen with level3 DNS (4.2.2.1 and 4.2.2.2) as the DNS servers. I removed them leaving ONLY OpenDNS and it immediately started resolving correctly again.

kejianshi

A lack of resolution could simply be a network error. I was really only seeing issue with HTTPS sites.
Cert errors just smell like MITM to me.

Trel

@kejianshi:

A lack of resolution could simply be a network error. I was really only seeing issue with HTTPS sites.
Cert errors just smell like MITM to me.

It's not a lack of resolution. It IS resolving to a different IP.

kejianshi

I'm certain no one would use DNS resolution to effect a MITM attack. (You are just paranoid)

cmb

@kejianshi:

I'm certain no one would use DNS resolution to effect a MITM attack.

That's actually pretty common, there's a variety of malware that will do just that to individual PCs, and sometimes to exploit routers and change their DNS servers so it impacts all LAN hosts. A variety of consumer-grade routers have been susceptible to such attacks.

cmb

@Trel:

I should mention though, that when I release/renew the WAN interface, I'm not getting a new IP. I'm getting the same one. Breaking the connection seems to be what fixes it.

After the further details later in the thread, I think why that has an impact is because it's triggering a DNS cache flush in the DNS forwarder, so the poisoned replies are no longer there.

kejianshi

haha - Yeah. I know. My sarcasm wasn't obvious enough? I'll try harder.

cmb

@kejianshi:

haha - Yeah. I know. My sarcasm wasn't obvious enough? I'll try harder.

Oh, the sarcasm font on here must be broken, sorry. :)

Trel

@cmb:

@Trel:

I should mention though, that when I release/renew the WAN interface, I'm not getting a new IP. I'm getting the same one. Breaking the connection seems to be what fixes it.

After the further details later in the thread, I think why that has an impact is because it's triggering a DNS cache flush in the DNS forwarder, so the poisoned replies are no longer there.

I actually just asked about this here: https://forum.pfsense.org/index.php?topic=87743.0

Is that a possible scenario, because if so I have a good idea of what might be doing it then.

kejianshi

My problem was originating outside the house between the ONT and the FIOS and or google DNS servers…
Its nothing inside the network that was causing it, but hopefully its mitigated now.

Trel

@kejianshi:

This problem is originating outside the house between the ONT and the FIOS and or google DNS servers…
Its nothing inside the network that was causing it, but hopefully its mitigated now.

If I can verify that pfsense itself is seeing the incorrect IPs for DNS lookups, there's definitely nothing internal that could be causing that at all?

kejianshi

There are just too many ways to mess with DNS especially if you can't trust the network between your machine and the servers. In the end, at best you can really only make sure that the guys playing games with your network aren't common criminals because you don't own the root servers.

Trel

@kejianshi:

There are just too many ways to mess with DNS especially if you can't trust the network between your machine and the servers. In the end, at best you can really only make sure that the guys playing games with your network aren't common criminals because you don't own the root servers.

But I'm asking about this specifically, I need to know if what's been happening could be due to an infected machine elsewhere on my network, or if it's definitely happening due to something from WAN and beyond.

kejianshi

I don't think one machine on the network could be the problem (unless that machine is pfsense its self), at least in my case, or going to unbound+DNSSEC would have made no difference.