Strange behavior with DNS resolving...

fmcatalan

Hi, this is very frustrating, I tried doing a lot of research before posting, but nothing seems to fit my problem, and is very very hard to explain, as I don't really understand it myself. I can only tell you what the effects are. So far I have identified 2 problems.

In my TV I can't execute the Youtube app, as I get a SSL cert error
In my home server I have an installation of Sonarr that can't resolve SOME addresses, and as a result I can't add new shows.

They seem like very unrelated issues, but here come the buts. If I connect the TV trough wireless I don't have that SSL error, I can use the app just fine. Now wireless is not managed by my pfsense directly I have a wireless router connected in bridged mode that takes an ethernet lan connection from my pfsense at the WAN port (that gets configured by pfsense's DHCP server.) If I get a cable from that router or the lan switch, I get the SSL Cert error, if I connect trough wireless everything works fine. So it seems something is wrong in pfsense DNS settings. That takes me to the second problem, I have reinstaled sonarr (many times over), standalone and in a docker image both locally and in a Virtual Machine, and there's no way to get it to work properly in my house, but if I take (Phisically take) the computer to my office it works fine. I have the same ISP here, running a second pfsense installation. I tried copying checkbox by checkbox the settings from the working pfsense to the other, and everyting seems identical, but I just won't work...

I have troubleshooted each individual error, with each individual community, and every time it all comes down to something wrong with pfsense...

I'm going slightly mad... The TV thing I can live without, and in any case is solved by the wireless route, but Sonarr was working fine, so fine it had turned completely transparent to me, I just found out it wasn't working when mid October I didn't get my new Flash episodes and found out they where not updating...

Well, if you read all of this, I thank you, and feel free to participate in this madness thread.

KOM

SSL has nothing to do with DNS per se. You may have a couple of issues that you're conflating as one.

Are you using any web proxy packages like Squid? Also, please provide more robust descriptions of the problem's symptoms because 'it doesn't work' isn't that helpful. Error messages? Timeouts? Incorrect data? Some details of your network configuration might also be useful.