DNS over TLS with CloudFlare not working for LAN hosts

rdlugosz

A few of us appear to be having a similar issue and started a thread here with some error logs: https://forum.pfsense.org/index.php?topic=146207.0

I'm guessing we're all experiencing the same problem.

ivor

We're seeing it as well. While we're investigating this issue, it seems to work with quad9 so I suggest you try it.

wgstarks

@ivor:

We're seeing it as well. While we're investigating this issue, it seems to work with quad9 so I suggest you try it.

What changes need to be made to use quad9?

ivor

We will be updating the blog post with that information, for now just replace the Cloudflare IP's with Quad9 ones (9.9.9.9 and 149.112.112.112).

wgstarks

@ivor:

We will be updating the blog post with that information, for now just replace the Cloudflare IP's with Quad9 ones (9.9.9.9 and 149.112.112.112).

Thanks. That worked.

I’ve seen similar reports on other forums regarding cloudflare’s primary server not working. Hopefully whatever the issue is will get resolved soon.

NeoDude

Also had this issue with CloudFlare's DNS servers. Using Quad9 until someone can figure out what's going on.

gsmornot

Not that its needed but, same here. First thing this morning no DNS service. Quick fix but strange, worked well all day yesterday.

Apr 4 09:28:42 unbound 15056:0 error: SSL_read syscall: Connection reset by peer

ivor

We have updated the blog post with Quad9 settings https://www.netgate.com/blog/dns-over-tls-with-pfsense.html

dem

@ivor:

We will be updating the blog post with that information, for now just replace the Cloudflare IP's with Quad9 ones (9.9.9.9 and 149.112.112.112).

Ivor, I see you've updated the instructions in the blog post to be closer to what I suggested here. However I still don't think you need the server: line.

Also I suggest against recommending people mix and match DNS providers since that could result in inconsistent results as the various providers block different sets of phishing and malware sites.

Finally it might be easier to confirm DNS over TLS is working by filtering States by :853 and :53.

Thanks.

jimp

You need the "server:" line because you cannot guarantee that the unbound config will still be in the "server:" context by the time it adds in the custom options. Depending on whatever else the user has configured in the resolver it may be in another section and break.

dem

Good to know, thanks Jim.

T5000

Doesn't work well, for me anyway. I have DNSBL enabled and my options look like this:

server:include: /var/unbound/pfb_dnsbl.*conf
forward-zone:
name: "."
forward-ssl-upstream: yes
forward-addr: 1.1.1.1@853
forward-addr: 1.0.0.1@853

many websites don't load at all or very slow (some are ok), iOS Appstore won't work either.

jimp

Cloudflare 's 1.1.1.1 server has been flaky for some people since it launched, try adding a line for 9.9.9.9 instead of 1.1.1.1

Ralphys

@T5000:

Doesn't work well, for me anyway. I have DNSBL enabled and my options look like this:
server:include: /var/unbound/pfb_dnsbl.*conf
forward-zone:
name: "."
forward-ssl-upstream: yes
forward-addr: 1.1.1.1@853
forward-addr: 1.0.0.1@853
many websites don't load at all or very slow (some are ok), iOS Appstore won't work either.

Cloudflare 1.1.1.1 and 1.0.0.1 is having issues with TLS atm. A Cloudflare team member mentioned that they will be releasing an update soon to correct it but there is no eta yet.

Try the following:

server:
include: /var/unbound/pfb_dnsbl.*conf
ssl-upstream: yes
do-tcp: yes
forward-zone:
name: "."
forward-addr: 9.9.9.9@853

That's Quad9 for the moment… you can reverse back to Cloudflare DNS once the issue has been resolved.

MoonKnight

Hi,

Strange, when i use forward-addr: 9.9.9.9@853 is working, but when I change to forward-addr: 1.1.1.1@853 or forward-addr: 1.0.0.1@853 i lose my Internet.

Any idea?

Thanks

jimp

Cloudflare has a problem with Unbound right now, they are not handling how it sends requests properly with tls. They say it's going to be fixed soon.

gsmornot

@jimp:

Cloudflare has a problem with Unbound right now, they are not handling how it sends requests properly with tls. They say it's going to be fixed soon.

Read on their Community this morning the update related to Unbound was released overnight. Testing here I still have an issue with 1.1.1.1 but 1.0.0.1 is fine. The issue covered here they created overnight a night ago with Unbound has been addressed though. No errors in my log. Now I just need to looking what is using 1.1.1.1 already.

tnovy

I think they have solved it - it started working for me.

NeoDude

Yep, working for me now too.

renegade

For me resolution does not work always.
I use MultiWAN with failover and it seems that if one gateway is down, resolution hangs.