VLAN, lans and OpenDNS?

[awebster]

Hi,

The example you show has 0 bytes hitting that DNS rule, so maybe the device isn't sending packets where you expect it.
Basic troubleshooting: what DNS servers are configured on the client devices?  Make sure that it shows the pfsense device as the DNS server.

[Velcro]

Thanks awebster…

I have attached another screen shot with updates. The dns on my device(iPad in this case) is showing the ip for the IPv4 address I created in "Interface->IOTVLAN".

From this screenshot I can see "bytes" are hitting that rule(thanks for that quick trouble shooting tip!)

I am able to get internet access and all is working however I am not using opendns?

[johnpoz]

pfsense out of the box would use unbound in resolver mode, so it would be resolving not forwarding.  If you want clients that ask pfsense for dns to just be forwarded to opendns then you would have to setup unbound in forwarder mode, or use the forwarder not unbound.

Or just point your client directly to opendns via dhcp, etc.

[awebster]

What tells you that it isn't using OpenDNS?

The normal function is device talks to DNS service (forwarder or resolver) running on pfSense.
If it is configured as a forwarder, it sends queries to the configured DNS servers in System->General Setup.
If it is configured as a resolver (default), it actually resolves the DNS names by chasing down the references starting from the top, so in this instance it would not be using OpenDNS at all.

[Velcro]

What tells me I am not using OpenDNS is when I go to the following web page on the OpenDNS site from my client:

https://support.opendns.com/hc/en-us/articles/227986567-How-to-test-for-successful-OpenDNS-configuration-

I would think using OpenDNS would be more "secure"? I think I would want to configure pfsense as a forwarder?

Johnpoz, when you say:

"Or just point your client directly to opendns via dhcp, etc."

Are you referring to adding the OpenDNS IPs into the Services->DHCP Server->Interface field labeled "Server-DNS servers"?

Thanks again to both for your response…

[awebster]

Whether OpenDNS is more "secure" is open to debate, but that's not the issue here.
You can either use the forwarder, or as Johnpoz suggests, putting the DNS servers into the DHCP configuration so that they are given out to the clients.
You will need a rule to allow DNS queries out to OpenDNS if you select the later option.

[Velcro]

Thanks again to all…I tried both settings.

I tried putting the DNS servers into the DHCP configuration, via Services->DHCP Server->Interface field labeled "Server-DNS servers". Immediately saw it was blocked....specifically the OpenDNS IPs.

I then changed from resolver to forwarder, I unchecked both dns server override and disable dns forwarder in DNS Server Settings under System->General. I only "enabled forwarder"(disabled dns resolver).

I went to the OpenDNS test and its working:
https://support.opendns.com/hc/en-us/articles/227986567-How-to-test-for-successful-OpenDNS-configuration-

Thanks again...

[johnpoz]

"DHCP Server->Interface field labeled "Server-DNS servers". Immediately saw it was blocked….specifically the OpenDNS IPs."

huh?  You do understand that if your client is going to be directly talking to opendns you would have to allow it on your firewall rules.  And 2nd you would have to make sure the client updated its lease or got a new one so it actually changed to using opendns directly.

[Velcro]

I did see it blocked wasn't sure of what the rule would look like but I assume the new rule would simply be changing the "destination" to an OpenDNS alias consisting of both OpenDNS IPs, with port 53 also as destination?

Is it better practice to use dns resolver(putting the DNS servers into the DHCP configuration) over using dns forwarder?

[awebster]

Yes, the rule is source=any, destination=alias of OpenDNS servers, port=53.  Make sure you specify TCP+UDP in the protocol, while UDP is primarily used for DNS, it will fall back to TCP under certain circumstances.

As far as better practice… pick what you're most comfortable with...

• DNS Forwarder = one place to control DNS behavior regardless of clients.

• DHCP config = requires the device's lease to renew (or device to reboot and/or reconnect) for the device to see the changes.

[Velcro]

Thank you awebster and Johnpoz…you rock!