1 WAN 2 LAN

KOM

I am pretty sure that there is something to do with the DNS

What's your output if you drop to a shell and type nslookup www.google.com?

nevr0sed

Hi,

Server:         192.168.2.1
Address:        192.168.2.1#53

** server can't find wwww.google.com: NXDOMAIN

I have no idea what that means…

n.

KOM

It means that you can't resolve hostnames to IP addresses, as if your DNS isn't working. Your DNS server is pfSense itself. Previous screens show you're running the DNS Resolver. Under your DNS Resolver settings, uncheck the Enable forwarding mode box and try it again. Do you have anything configured under General Settings - DNS Servers?

nevr0sed

@KOM:

It means that you can't resolve hostnames to IP addresses, as if your DNS isn't working. Your DNS server is pfSense itself. Previous screens show you're running the DNS Resolver. Under your DNS Resolver settings, uncheck the Enable forwarding mode box and try it again. Do you have anything configured under General Settings - DNS Servers?

Hi,

I have done what you requested. Still no changes in the problem.
I have 2 DNS servers that will be used on the PRIVATELANINTERFACE to configure a VPN on it. I have tried with them and without, and nothing changes.

Thanks again. This issue is starting to make me crazy… :)

n.

![Image 1.png](/public/imported_attachments/1/Image 1.png)
![Image 1.png_thumb](/public/imported_attachments/1/Image 1.png_thumb)
![Image 2.png](/public/imported_attachments/1/Image 2.png)
![Image 2.png_thumb](/public/imported_attachments/1/Image 2.png_thumb)

KOM

I don't know then. Maybe someone else has some suggestions.

nevr0sed

Ok ! I Will be here looking at the topic from time to time.

On my side, I will maybe reset to factory defaults and see what will happen then. I will post any further results here.

I am giving you an applaud for your help ! :)

Thanks again.

n.

jpk_pfsense

Do you have DNS resolver enabled? If not, check it and enable on all interfaces. Go into the Interface tab and remove "Block private networks" checkbox. If you get things working then you can tighten it back up. Then go to your DHCP server and on the interface erase any DNS and Gateway settings you might have.

nevr0sed

Ok the issue was the NAT. Didn't have an outbound rule…

Stupid of me.

Thanks to you all for the help and support.

n.

gkrellShoot_03-14-16_020613.jpg_thumb

Jameson4170

This post is deleted!

JKnott

This post is deleted!