Check DNSBL Access for Spam Blocker

**donhwyo** · 04-26-2018, 07:53 AM

I see a notification triangle about "dnsbl not working". Seems it may be an intermittent thing as it is gone now. Anyway I googled and found the link below. I got the result shown. Now that the triangle went away I tried again with the same result.

According to this page https://support.untangle.com/hc/en-u...r-Spam-Blocker I should run this.

Code:

[root @ homeuntangle] ~ # curl -s http://www.untangle.com/download/patches/generic/check_spam_health.sh | bash
bash: line 1: syntax error near unexpected token `newline'
bash: line 1: `<html>'
[root @ homeuntangle] ~ #

I don't think that is what I should see. Is that page just out of date?

Thanks

**dmorris** · 04-26-2018, 08:05 AM

the command is here:

https://wiki.untangle.com/index.php/Script_-_Check_DNSBL_Access

**donhwyo** · 04-26-2018, 08:37 AM

Thanks it is normal now. Will try again if the triangle returns.

**donhwyo** · 04-26-2018, 08:56 AM

Ran it anyway. Now I see this.

Code:

Testing dnsmasq ...
[127.0.0.1] : DNS       FAILED (incorrect result)

In the script I see this.

Code:

# check a normal lookup
    testServer $server "untangle.com" 'has address 74.123.31.30' 'DNS'

Nslookup shows this.

Code:

Non-authoritative answer:
Name:    untangle.com
Addresses:  2400:cb00:204
          2400:cb00:2048:
          104.20.2.248
          104.20.3.248

or

Code:

[root @ homeuntangle] ~ # nslookup untangle.com
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   untangle.com
Address: 104.20.2.248
Name:   untangle.com
Address: 104.20.3.248

Is something spoofing me?

Thanks

**sky-knight** · 04-26-2018, 09:14 AM

If the DNS test is failing, the upstream DNS servers you've configured on Untangle's external interface are intermittently not working properly.

*Edit* Hold a moment I think I spoke too soon, I need to check something.

Confirmed, the script has a bug. It was never updated when Untangle.com changed web servers.

Anyone that runs this script is going to see DNS as "failed" because it's expecting untangle.com to resolve to 74.123.31.30, and it's resolving to 104.20.3.248 and 104.20.2.248.

**dmorris** · 04-26-2018, 09:29 AM

No its probably just out of date.

**donhwyo** · 04-26-2018, 09:37 AM

Ya I am suspecting my "no completion piss poor isp". But I think the tool may need help. It might also be nice if the thing that triggers the triangle also triggered a log entry. Not sure it doesn't. But I don't know where to look.

Thanks

**donhwyo** · 04-26-2018, 09:54 AM

Originally Posted by dmorris

No its probably just out of date.

I have to agree, I am out of date but I consider it a feature.

My isp has gone down 3 times since I started this thread. LOL

**dmorris** · 04-26-2018, 08:09 PM

Originally Posted by donhwyo

I have to agree, I am out of date but I consider it a feature.

My isp has gone down 3 times since I started this thread. LOL

No I mean the script is out of date.
Its probably just checking the wrong IP.

**sky-knight** · 04-26-2018, 08:41 PM

Originally Posted by sky-knight

Confirmed, the script has a bug. It was never updated when Untangle.com changed web servers.

Anyone that runs this script is going to see DNS as "failed" because it's expecting untangle.com to resolve to 74.123.31.30, and it's resolving to 104.20.3.248 and 104.20.2.248.

That's exactly what's happening.

Thread: Check DNSBL Access for Spam Blocker

LinkBack

Thread Tools

Check DNSBL Access for Spam Blocker

Posting Permissions