I've been testing DNS tonight vice using Earthlinks DNS nameservers.
Looking at my hourly syslog snip, about half way through my NANAS run I
noticed the below entries. First of all, what are these entries telling
me? Secondly, if this is an error in the uridnsbl plug-in is it possibly
caused by the change in nameservers? I did notice that my report time per
message was a bit slower tonight than usual, its usually about
3.1-3.5secs/report, whereas tonight it was about 4.8/report.
Sep *1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr for
domain=spamhaus.org, rule=URIBL_XS_SURBL, id=8876
rr=spamhaus.org.xs.surbl.org. 1 IN A 208.67.219.40
at / line
626.
Sep *1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr for
domain=otwaloow.com, rule=URIBL_XS_SURBL, id=8880
rr=otwaloow.com.xs.surbl.org. 1 IN A 208.67.219.40
at / line
626.
Sep *1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr:
domain=senderbase.org, zone=multi.uribl.com., id=8871
1 IN A 208.67.219.40
at / line
638.
Thanks for any guidance.

Fri, Sep 01, 2006 at 10:22:42PM -0500, Chris wrote:
First of all, what are these entries telling me? Secondly, if this
is an error in the uridnsbl plug-in is it possibly caused by the change
in nameservers?

The error is saying that it's looking for a 127/8 result, but it gets
208.67.219.40 (which resolves to a *.opendns.com name btw). So I would
say that yes, the problems are related to changing your nameservers.

Friday 01 September 2006 10:35 pm, Theo Van Dinter wrote:
Fri, Sep 01, 2006 at 10:22:42PM -0500, Chris wrote:
First of all, what are these entries telling me? Secondly, if this
is an error in the uridnsbl plug-in is it possibly caused by the change
in nameservers?

The error is saying that it's looking for a 127/8 result, but it gets
208.67.219.40 (which resolves to a *.opendns.com name btw). So I would
say that yes, the problems are related to changing your nameservers.

Thanks Theo, back to the EL nameservers it is then.

Friday, September 1, 2006, 8:22:42 PM, Chris Chris wrote:
I've been testing DNS tonight vice using Earthlinks DNS nameservers.
Looking at my hourly syslog snip, about half way through my NANAS run I
noticed the below entries. First of all, what are these entries telling
me? Secondly, if this is an error in the uridnsbl plug-in is it possibly
caused by the change in nameservers? I did notice that my report time per
message was a bit slower tonight than usual, its usually about
3.1-3.5secs/report, whereas tonight it was about 4.8/report.

Sep *1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr for
domain=spamhaus.org, rule=URIBL_XS_SURBL, id=8876
rr=spamhaus.org.xs.surbl.org. 1 IN A 208.67.219.40
at / line
626.
Sep *1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr for
domain=otwaloow.com, rule=URIBL_XS_SURBL, id=8880
rr=otwaloow.com.xs.surbl.org. 1 IN A 208.67.219.40
at / line
626.

BTW, please stop using xs.surbl.org until you hear otherwise.
It's a test list that's sort of napping now.

Jeff C.

Saturday 02 September 2006 8:46 am, SM wrote:
At 20:22 01-09-2006, Chris wrote:
>I've been testing DNS tonight vice using Earthlinks DNS nameservers.
>Looking at my hourly syslog snip, about half way through my NANAS run I
>noticed the below entries. First of all, what are these entries telling
>

Turn off the "typo correction" feature of DNS.

Regards,
-sm

Thanks, went there and did that, I'll see how it goes now. also that
after I went back and started using DNS I finally got their 'welcome'
page, then after a bit went back and got the 'oops' page. Seems to be
working though, nslookup shows I'm using their nameservers.

Saturday, September 2, 2006, 8:43:21 PM, Chris Chris wrote:
Saturday 02 September 2006 8:46 am, SM wrote:
>At 20:22 01-09-2006, Chris wrote:
>>I've been testing DNS tonight vice using Earthlinks DNS nameservers.
>>Looking at my hourly syslog snip, about half way through my NANAS run I
>>noticed the below entries. First of all, what are these entries telling
>>

>Turn off the "typo correction" feature of DNS.
>>
>Regards,
>-sm

Thanks, went there and did that, I'll see how it goes now. also that
after I went back and started using DNS I finally got their 'welcome'
page, then after a bit went back and got the 'oops' page. Seems to be
working though, nslookup shows I'm using their nameservers.

Question for Chris:

Did turning off the typo correction feature of DNS cause the
SURBL lookups (both hits and misses) to start working again? If
so we may want to add it to our FAQ, given that others may be
having similar issues.

Jeff C.