![]() ![]() Someone outside of the local network told me that he could not access my domain, but at this time, I was also outside the pfSense network and could access it successfully. Also it seems (unconfirmed) that my domain cannot resolve for everyone. On the pfSense, the DNS Lookup returns: Host "" could not be resolved. I did a reset of the connections states of the pfSense I tried putting Google DNS in the DNS Servers When enabling DNS Resolver, it shows "unbound" in the Status>Services page. I have disabled DNS Forwarder and DNS Resolver to force queries to bypass the pfSense DNS So there is something in the pfSense that keeps something somewhere but can't find what it is. So I know it's not a problem of the ISP DNS. If I try the website when connected to this very first router, everything work fine. The ISP company came here, installed a new modem/router and put it in front of the pfSense router. Recently I changed to ISP company #2 and went to a dynamic public IP. If I try outside of the network, it works fine. My main local router is a pfSense v2.4.3 and I removed all the configurations I did for the old local server, but still, when I am inside this pfsense network, I can't access the site at the new location. ![]() If it is not resolved then using cached then we use DNSCRYPT. The main reason was that pfBlockerNG could not show all the blocked DNS. The replication of the A record has been done about 2 weeks ago now. NXFilter is the DNS SERVER, which has unbound as upstream DNS and goes to dns hsts bypass engine. NxFilter supports various kinds of user authentication methods including Active. Now I decided to move the website to a remote hosting company so I changed the A records of my domain to point to that new server. If your browser can't verify an SSL certificate, it stops you from visiting the site by giving you the 'your connection is not private' error message. I was also using a static public IP for the WAN with ISP #1. Most often, the 'your connection is not private' error lies in a site's Secure Sockets Layer (SSL) certificate, which is required for sites running over HTTPS (connection security). The issue is that unless we install the Filter appliance SSL root certificate on every device, we're going to see the 'This connection is not private' error, typically in modern browsers (related to HSTS).Ĭan any other filter show a block page for HTTPS sites without needing to install the SSL certificate?īasically, I'd like to take some examples back to them and suggest they are not correct in saying that all filtering engines suffer the same problem - I'm sure I've seen a block page on my device when going joining a guest network and heading to a HTTPS site (without SSL certificate) Can't remember whether it was Smoothwall or Sophos.ĮDIT: Apologies, I should have mentioned that I actually don't want to SSL inspect any traffic, but without the inspection this issue is compounded in the sense that most HTTPS sites then show the 'Connection not private' problem page.I had a local webserver that was working fine and on which I had a website on domain. They suggest all filtering providers are the same on this issue. Came across an issue with our current filtering solution that has an undesirable workaround.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |