DNS server priority

marcelloc

If you want to remove 127.0.0.1 from list, disable dns forwarder in services menu.

A Former User

@marcelloc:

If you want to remove 127.0.0.1 from list, disable dns forwarder in services menu.

thank you. i disabled that option and i clicked saved, but i still see it as the first DNS server under

status–-->interfaces

it didnt say anything about rebooting pfsense, but do i need to wait a few minutes and check again?

or will i always see 127.0.0.1, but the system just bypasses it?

thanks.

marcelloc

@tomdlgns:

or will i always see 127.0.0.1, but the system just bypasses it?

It will not, try the reboot when possible.

A Former User

@marcelloc:

@tomdlgns:

or will i always see 127.0.0.1, but the system just bypasses it?

It will not, try the reboot when possible.

interesting. ever since i disabled that DNS forwarder option, i cant get anything to work.

no internet, no webgui, nothing…

i am off site right now. i was connected into a workstation on the network that is running pfsense.

since i am not on site, i cant reboot it at this time.

(however i am still connected via logmein....) this is odd.

A Former User

while remotely connected, i can ping the pfsense box (192.168.1.1) but something with DNS isnt working.

C:\Users\admin>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\admin>ping google.com
Ping request could not find host google.com. Please check the name and try again
.

C:\Users\admin>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 22ms

hmmmmmmm. i cant web into 192.168.1.1

is it possible to reboot pfsense via command line from a network PC?

EDIT- i just tried IE and i can login to pfsense using IE. should i reboot the box or is there something else i should try before i attempt to reboot it?

marcelloc

is it possible to reboot pfsense via command line from a network PC?

yes it's in menu option.

interesting. ever since i disabled that DNS forwarder option, i cant get anything to work.

you need firewall rules to allow access to dns service on lan.

A Former User

@marcelloc:

is it possible to reboot pfsense via command line from a network PC?

yes it's in menu option.

interesting. ever since i disabled that DNS forwarder option, i cant get anything to work.

you need firewall rules to allow access to dns service on lan.

it is in the menu option from a remote PC on the network? i dont follow.

also, if i needed rules to allow DNS server on the LAN, it would have been nice to know that prior to unchecking that box. ;D

A Former User

ok, i just enabled DNS forwarder to make sure sites can resolve. this is probably something that i should work on while i am on site.

wallabybob

@tomdlgns:

for my LAN devices, i want to make sure that they point to pfsense (192.168.1.1) for DNS, which is what is currently in place now.

So why would tomdlgns want to disable the DNS forwarder as suggested:
@marcelloc:

If you want to remove 127.0.0.1 from list, disable dns forwarder in services menu.

cmb

@marcelloc:

If you want to remove 127.0.0.1 from list, disable dns forwarder in services menu.

Don't do this unless you really know what you're doing, it'll break DNS on all LAN clients in the default out of the box setup.

marcelloc

@wallabybob:

So why would tomdlgns want to disable the DNS forwarder as suggested:
@marcelloc:

If you want to remove 127.0.0.1 from list, disable dns forwarder in services menu.

he wants to use only opendns servers:

i want to use the openDNS servers (208.67.222.222, 208.67.220.220).

wallabybob

@marcelloc:

he wants to use only opendns servers:

i want to use the openDNS servers (208.67.222.222, 208.67.220.220).

Right, but his LAN clients are configured to use pfSense as their name server:
@tomdlgns:

for my LAN devices, i want to make sure that they point to pfsense (192.168.1.1) for DNS, which is what is currently in place now.

If pfSense doesn't have DNS forwarder (or equivalent) enabled how will his LAN clients get name service from pfSense?

marcelloc

tomdlgns did not specified a complete scenario, he just asked how to use his opendns servers.

The way he asked, creating lan rules to allow dns queries to 208.67.222.222 and 208.67.220.220 will work.

A Former User

@marcelloc:

tomdlgns did not specified a complete scenario, he just asked how to use his opendns servers.

The way he asked, creating lan rules to allow dns queries to 208.67.222.222 and 208.67.220.220 will work.

How do I do this?

That was the next part of my question, but I didn't want to tackle it until I got home.

My goal is to have network computers point to 192.168.1.1 for DNA, the pfSense box, and I want to use opendns servers.

I am using opendns servers now, but if a network user inputs 8.8.8.8 or other third party servers in their nic settings, they will bypass the opendns servers.

Basically, I want to intercept all DNA lookps just before they leave the network. I was able to do this with dd wrt firmware on a Lindsay's router before I switched to pfSense.

Thanks

marcelloc

This way you need to block dns queries on lan rules and enable dns forwarder.

A Former User

@marcelloc:

This way you need to block dns queries on lan rules and enable dns forwarder.

sure, but is there a guide to do this? if i knew how to do it, i wouldnt have posted in here.

:)

marcelloc

Do you need help creating rules or changing dns servers?

A Former User

@marcelloc:

Do you need help creating rules or changing dns servers?

under the general tab, right now, i have the openDNS servers and the local host address

127.0.0.1
208.67.222.222
208.67.220.220

with the help from you guys in this thread, i have been able to eliminate the ISP DNS Servers from that list.

it appears that is working w/o any issues.

the next step is to create rules, i suppose that is next, that will allow me to intercept DNS lookups. that might not be the right word/phrase.

but what i would like to accomplish is to force a certain set of DNS servers to be used regardless of what the user has used on their device.

wallabybob

You could add the following firewall rule (On Firewall -> Rules, click on the LAN tab, click on the lowermost "+": Action=Block, Disabled='not ticked', Interface=LAN, Protocol=TCP/UDP, Source=any, Destination=( not='ticked', Type=LAN address,) Destination port range=DNS, Log='ticked')

This will block any attempt by a system connected to the LAN interface to access (by TCP or UDP) a DNS Server (port 53) on any IP address other than the pfSense LAN IP address and will log in the system log any such attempt.

If you have other firewall rules on the LAN interface you need to check that a rule higher up the list doesn't allow this rule to be bypassed. (Rules are processed from the top down, processing stops on the first match.)

The logging gives some information to help track down offenders.

A Former User

thanks, i will try this.

if i do this, can i disable the DNS forwarder option?

my LAN PCs are using 192.168.1.1 for the DNS server, which is what i want, but i didnt set that under the DHCP settings for the LAN interface.

is it pulling that by default?

also, i dont mind leaving the DNS forwarder option as is, i dont want to break anything, but i also dont see the need to have 127.0.0.1 as a DNS server.

thank you for your help.