Hi Raymond, At 14:22 02-06-2009, Raymond Dijkxhoorn wrote:
surbl.org nameservers, or multi.surbl.org nameservers? Two different things.
It's one of the multi.surbl.org nameservers.
For the first i dont see issues, for the second, its only rbldnsd servers so wonder how this could be....
I sent Jeff an email. The behavior looks more like policy enforcement instead of a rbldnsd server issue.
Regards, -sm
Hi!
It's one of the multi.surbl.org nameservers.
For the first i dont see issues, for the second, its only rbldnsd servers so wonder how this could be....
I sent Jeff an email. The behavior looks more like policy enforcement instead of a rbldnsd server issue.
No its not, its a couple broken rbldnsd nameservers. See my other posts. I have partly undelegated the broken servers. Behaviour should stabilize when we get the last two root servers updated.
Thanks for the notify however.
Bye, Raymond.
On Wed, 3 Jun 2009, Raymond Dijkxhoorn wrote:
Hi!
It's one of the multi.surbl.org nameservers.
For the first i dont see issues, for the second, its only rbldnsd servers so wonder how this could be....
I sent Jeff an email. The behavior looks more like policy enforcement instead of a rbldnsd server issue.
No its not, its a couple broken rbldnsd nameservers. See my other posts. I have partly undelegated the broken servers. Behaviour should stabilize when we get the last two root servers updated.
Thanks for the notify however.
Bye, Raymond.
FWIW, I was seeing the same behaivor from one of my DNS servers. I'm running two public rbldnsd servers, and I have a couple of BIND dns servsers as "type forward" front-ends for the surbl zones.
I had a stale config in one of the fall-back servser which had old entries containing explicit forwards for the old surbl zones (ws.surbl.org, be.surbl.org, ob.surbl.org, etc) and I was seeing bogus respones for those zones (IE twitter.com.xs.surbl.org -> 202.181.7.85).
I killed those stale forwards and those bogus reponses went away.
-
David B Funk -
Raymond Dijkxhoorn -
SM