Pinging but not browsing - Pfsense
-
So the internal client has no DNS. What is it using for DNS?
Can pfSense itself resolve anything? From Diag > DNS Lookup for example.
Is the Unbound service running correctly in pfSense?
Steve
-
@stephenw10 I tried dns lookup through pfsense as u suggested, and it does successfully resolve hostnames.
-
On every listed server?
So what DNS is the client using?
Steve
-
@stephenw10 how do I find that out?
-
You can run something like
dig google.comand it will show what servers gets the result from. But if you're running systemd, as it slowly takes over everything, it will probably just show localhost. In which case run something likeresolvectl status eth0Steve
-
@stephenw10 running dig google.com from the Ubuntu VM instance syas "connection timed out; no servers could be reached". By the way, I am running a testing vm instance, its not the full OS installed, I dont know if that makes a difference, I dont think it should.
-
Is the client using dhcp? If not what DNS servers did you set?
If it's static and you didn't set any there's your problem.
If it's dhcp it should pull the pfSense LAN IP for DNS and you never answered my question about Unbound so I'll assume that is running correctly.
Steve
-
@stephenw10 Hi steve, I dont know what the "unbound service" is. Also, how do i check if the client is using dhcp? By client im guessing you are refering to my ubuntu instance right? I have set 8.8.4.4 and 8.8.8.8 as DNS servers during the set up wizard of pfsense.
I have tried out something right now, and the results are quite weird. So.. I have "enabled DHCP server on LAN interface" through the pfsense conf. and when I try to use an ip address like 157.240.14.35 directly in the browser, it resolves it to www.facebook.com but it does not connect to it, saying that it has trouble finding that site.
-
@stephenw10 Ive removed the ubuntu instance, and restarted it, made sure to have DHCP running on pfsense and for some reason it does work now. I can access the internet.
-
Ok, so the Ubuntu VM probably wasn't using DHCP before and didn't have any servers set so it couldn't resolve.
