On 6/2/09, Raymond Dijkxhoorn raymond@surbl.org wrote:

Ho!

...

...

So able to reproduce this. But its depending what machine you are using, what reply you get. On some if get random results, on others i get nxdomain, on this exact same server.

...

I can reproduce the above. I suggest dropping 202.106.182.243 too.

< f.surbl.org. 86400 IN A 202.106.182.243 113d111 < k.surbl.org. 86400 IN A 123.125.50.246 124d121 < l.surbl.org. 86400 IN A 202.106.182.244

Those 3, all running a older vers rbldnsd, we will follow up with the people kindly hosting those nameservers for us.

The 202.106 servers seem to be giving the right results now:

; <<>> DiG 9.4.2 <<>> twitter.com.multi.surbl.org @202.106.182.243 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2324

; <<>> DiG 9.4.2 <<>> twitter.com.multi.surbl.org @202.106.182.244 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15391

Can anyone else confirm please?

The 123.125 one seems wrong:

; <<>> DiG 9.4.2 <<>> twitter.com.multi.surbl.org @123.125.50.246 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26165 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;twitter.com.multi.surbl.org. IN A

;; ANSWER SECTION: twitter.com.multi.surbl.org. 86400 IN A 211.94.66.147

Undelegating it.

Jeff C.