Cannot resolve DNS from LAN
Hi everyone, I'm a new user, I'm trying to install pfSense on an old computer that i had lying around, everything goes out nicely during installation. The problem is that i cannot resolve hostnames from the LAN, i tryed pinging with the console itself and it's working, both hostnames and ips, but when it comes to a pc connected to the lan i can only ping external ip addresses, like 188.8.131.52 (and reach the pfsense web configurator). I alredy did a virtualised installation and everything worked fine virtualised, so i'm kinda confused... can it be an hardware problem? I'm sure someone probably alredy had a similar problem so even linking a solved thread would be helpful. Thanks in advice
Gertjan last edited by
It this device on LAN a PC ?
Check the network status of the network adaptor.
The IP, mask, gateway and DSN are obtained by DHCP ?
Is the IP "in" the LAN network ? DHCP server pool ? mask is ok ?
The DNS and gateway IP should be the IP of the LAN IP of pfSense.
What do you see in here : Status > System Logs > DHCP and Resolver ?
Out of the box, after installing pfSense, after putting in your password, and change nothing else, pfSense works like any other router on the planet : it works.
Btw 184.108.40.206 isn't mentioned no where in the pfSense manual .... which means : not needed for pfSense to operate.
I can get to other services on our website like our unlock for our software (unlock.xenetech.com) but when trying to go to the main site of xenetech.com it says site can't be reached. however, I can get to it remotely or by typing in the address.
Does anyone have an idea of why my main site address won't resolve?
oops wrong topic
@Gertjan The device in the LAN is a PC, also tried with a mobile phone but same result.
IP, mask, and gateway of the PC are obtained by pfSense LAN's DHCP, the pc's ip's is within the LAN network which I configured as 192.168.2.1/24, starting the DHCP range at .10 and terminating at .200, the pc network adapter got 192.168.2.11 as ip, 255.255.255.0 as mask, and 192.168.2.1 as gateway/dns resolver which I believe is all correct and within the LAN.
The mikroTik you can see in the logs is there cause i tried to extend the LAN with this device to get wireless connectivity, but to prove it's not some external HW problem i connected directly to the network card two different PC's, same result, can connect to internet if i reach to an ip, but cannot resolve DNS's queryes.
If you need to know also the WAN connection comes from an external proprietary router DHCP, in which I setted a reservation for pfSense as 192.168.1.50 in a 192.168.1.1/24 network
I put all the logs you requested here