DNSBL Source Definitions Invalid URL or Hostname not resolvable!

NOTORIOUS_VR

Somewhat at a loss here with this one as I cannot see anything wrong.

I moved my list from one local webserver (local) to another (local) that is on the same (physical) host (VM), but different hostname. Nothing else changed.

HAProxy is serving the certs, the list works when browsing to it from my browser inside my network and out, and nothing with the list changed just copied it from one DIR to another on my server.

DNS lookup from pfsense is good from what I can see:

Results
Result	Record type
10.10.0.254	A
Timings
Name server	Query time
127.0.0.1	1 msec
::1	No response
1.1.1.1	27 msec
1.0.0.1	27 msec

Traceroute good:

 1  pfSense (10.10.0.254)  0.154 ms  0.151 ms  0.063 ms

Yet I can't seem to get pfblocker to see the list for whatever reason:

tinfoilmatt

@NOTORIOUS_VR ~~.host is not a valid TLD and therefore fails input validation.~~

Strike that.

To be sure, HAProxy is listening on 10.10.10.254:443?

NOTORIOUS_VR

@tinfoilmatt said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

To be sure, HAProxy is listening on 10.10.10.254:443?

I would assume it would be. Like I said, the site/list works without issue inside and out of my network just like all of my other services that HAproxy serves.

tinfoilmatt

@NOTORIOUS_VR One way to confirm via webConfigurator is Diagnostics / Sockets (displaying sockstat output).

HAProxy config gotta be implicated. What happens if you curl the feed to /tmp from a shell?

NOTORIOUS_VR

@tinfoilmatt said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

What happens if you curl the feed to /tmp from a shell?

Seems to work...

tinfoilmatt

@NOTORIOUS_VR curl -o /tmp/adobe.txt https://xxxxx.host/lists/adobe.txt to download the file and save it as a file.

And it actually looks like curl exited with an error. You might try [hostname].xxxxx.host for this webserver.

NOTORIOUS_VR

@tinfoilmatt said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

curl -o /tmp/adobe.txt https://xxxxx.host/lists/adobe.txt to download the file and save it as a file.

And it actually looks like curl exited with an error. You might try [hostname].xxxxx.host for this webserver.

Saving to a file works just fine:

The error was just because I didn't know what the command was...

tinfoilmatt

@NOTORIOUS_VR I don't know, man. If it were my system, there's at least two other integrations and one system configuration I'd check (not to mention attempt to decipher the code I linked you to). But nothing's jumping out at me.

tinfoilmatt

Is pfBlockerNG otherwise configured and operational with working both DNSBL and IP feeds?

NOTORIOUS_VR

@tinfoilmatt said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

Is pfBlockerNG otherwise configured and operational with working both DNSBL and IP feeds?

Yes everything is working as it should - the only issue is that it report it cannot access the URL feed from my web server.

It's very strange. I want to say that I might have had a similar problem when I had it on the other URL/site (same server) but it was so long ago now I cannot be sure.

tinfoilmatt

@NOTORIOUS_VR Additional relevant validation code here.

NOTORIOUS_VR

@tinfoilmatt said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

@NOTORIOUS_VR Additional relevant validation code here.

Not sure what that is sorry.

Spider_VL

@NOTORIOUS_VR Not sure if thats gonna point in any right direction but I had same error when I changed the type form Unbound to Python version. I couldnt figure out that at my short attempt to use python version and swapped back to unbound and all fixed itself and suddenly lists working again.

NOTORIOUS_VR

@Spider_VL said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

@NOTORIOUS_VR Not sure if thats gonna point in any right direction but I had same error when I changed the type form Unbound to Python version. I couldnt figure out that at my short attempt to use python version and swapped back to unbound and all fixed itself and suddenly lists working again.

Well, well, well! That worked for me as well! Thank you!

So now the question is, what breaks and why when moving to python version.

Spider_VL

@NOTORIOUS_VR glad it helped :) I will probably take a look at python version at some point in unforseen future :) but if you find the reason in mean time dont be shy to post here or drop me a message :)

NOTORIOUS_VR

@Spider_VL said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

@NOTORIOUS_VR glad it helped :) I will probably take a look at python version at some point in unforseen future :) but if you find the reason in mean time dont be shy to post here or drop me a message :)

Will do!

Gertjan

You've mixed IP addresses (and/or networks), some of them with the port number (seems wrong to me) and host names together in one file.
That's a big no-no.

You've create a DNSBL entry "Adobe"
and the very first line :

will get flagged as an error, as it is not a host name. It's an IP.

tinfoilmatt

@Gertjan That error references an 'invalid URL or hostname' of the feed itself.

That said, pfBlockerNG's parsing functionality properly handles an IP feed also containing FQDNs, and vice versa.

NOTORIOUS_VR

@Gertjan said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

will get flagged as an error, as it is not a host name. It's an IP.

This is incorrect, the error is for the position of the line in the DNSBL Category/list position.

I know this because when I added another it then said line 2 instead of 1. Also I removed all IP's and the error is the same.

Also as confirmed above in non-python mode the list loads just fine, so the issue is with the python mode not able to resolve the local server address while pfsense and everything else is.

tinfoilmatt

@NOTORIOUS_VR said in DNSBL Source Definitions Invalid URL or Hostname not resolvable!:

the error is for the position of the line in the DNSBL Category/list position.

These are called 'feeds' within a 'feed group' configuration.