PfBlockerNG v2.0 w/DNSBL
-
So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.
Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?
It seems like that should work (not that I'd know) but I don't see why it is necessary that pfbng w/ dnsbl uses an ISP's DNS. If it can filter requests going through the ISP couldn't it do the same with any public DNS?
-
Read again https://forum.pfsense.org/index.php?topic=102470.msg572527#msg572527
about forwarding mode. -
Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).
Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.
-
So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.
All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.
Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?
That what pfSense DNS Resolver forwarding mode is for.
-
Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).
Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.
Check the hosts DNS configuration to see what DNS server they use.
-
All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.
OK, awesome, thank-you. This is what I must be doing wrong. As far as I thought, I am using the DNS resolver (not using forwarded, forwarding mode not turned on, and I've removed all entries in general setup & dhcp for alternative DNS servers).
But whenever I run dnsleaktest.com, I still get my ISP's DNS server?What am I doing wrong? How can I run DNS off of pfsenses internal DNS?
I didn't even know pfsense did this natively, I thought if I wanted to use an internal DNS server then I had to set up and run the whole thing on a real or virtual machine, which I dont know how to do.
-
yup pfsense has a DNS Resolver ;)
So now you have to check your hosts/device DNS configuration.
If they get DNS server configuration from a DHCP server, then configure the DHCP server to send pfsense ip.
@ :
Leave blank to use the system default DNS servers: this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the System / General Setup page.
-
awesome, i got it working as its meant to be, thank you for sticking with my ignorant line of questioning!
One last question, how does the "root server" resolve the DNS lookups? as in what tells my pfsense box the ip address that google.com resolves to?
-
https://en.wikipedia.org/wiki/Domain_Name_System
https://en.wikipedia.org/wiki/Root_name_server -
A PR has been merged for pfBlockerNG. v2.1.1_6
https://github.com/pfsense/FreeBSD-ports/pull/253Fixes:
- EasyList has recently changed the format of the feed. DNSBL parser has been updated.
- Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
- Fix DNSBL Certificate creation for pfSense 2.4
-
A PR has been merged for pfBlockerNG. v2.1.1_6
https://github.com/pfsense/FreeBSD-ports/pull/253Fixes:
- EasyList has recently changed the format of the feed. DNSBL parser has been updated.
- Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
- Fix DNSBL Certificate creation for pfSense 2.4
Hello, thanks for all your work on this. I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
-
I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
Yes. And the point of the report is exactly what?
-
I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.
http://imgur.com/a/I3mep
Yes. And the point of the report is exactly what?
Please review the linked image. There are two points :
1. "Package is configured but not (fully) installed" (even after reinstallation)
2. "Newer version available" (without the update option)Regards,
Matt -
Please review the linked image. There are two points :
1. "Package is configured but not (fully) installed" (even after reinstallation)
2. "Newer version available" (without the update option)Regards,
MattThat is the Legend for the Package Manager ::)
So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"
-
That is the Legend for the Package Manager ::)
So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"
Ah, my bad! The lack of a separator there as opposed to the ones above it is a bit confusing ( http://imgur.com/a/lwSFx ).
Regards,
Matt -
That is the Legend for the Package Manager ::)
So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"
Ah, my bad! The lack of a separator there as opposed to the ones above it is a bit confusing ( http://imgur.com/a/lwSFx ).
Regards,
MattLOL, ok… https://redmine.pfsense.org/issues/7203
-
-
LOL, ok… https://redmine.pfsense.org/issues/7203
Maybe just add "Legend : "
Yeah I tried and that looked even worse than now. Leaving this to someone else.
-
Hello,
Regarding Adaway,
https://adaway.org/hosts.txt
Although the list is downloaded:
[ Adaway ] Downloading update .. 200 OK. completed ..
I got this error:
[ pfB_Adaway Adaway ] List Error ]
Please advise
-
I assume that Adaway is also the name of the Alias?
Do you have anything in the custom list at the bottom of this alias? I think that's the part that's not parsing properly. Anything in a custom list must be formatted properly.
