Hi!
And here's two executed at York University, also in Toronto:
$ dig +short @130.63.168.21 twitter.com.multi.surbl.org 216.234.179.13 $ dig +short @130.63.237.99 twitter.com.multi.surbl.org 203.161.230.171
I confirm...
[martins@localhost ~]$ host twitter.com.multi.surbl.org. Host twitter.com.multi.surbl.org. not found: 3(NXDOMAIN) [martins@localhost ~]$ host twitter.com.multi.surbl.org. twitter.com.multi.surbl.org has address 209.145.54.50 Host twitter.com.multi.surbl.org not found: 3(NXDOMAIN) Host twitter.com.multi.surbl.org not found: 3(NXDOMAIN) [martins@localhost ~]$ host twitter.com.multi.surbl.org. Host twitter.com.multi.surbl.org. not found: 3(NXDOMAIN) [martins@localhost ~]$ host twitter.com.multi.surbl.org. twitter.com.multi.surbl.org has address 203.161.230.171 Host twitter.com.multi.surbl.org not found: 3(NXDOMAIN) Host twitter.com.multi.surbl.org not found: 3(NXDOMAIN)
twitter.com.multi.surbl.org has address 216.234.179.13 [martins@localhost ~]$ host twitter.com.multi.surbl.org. | grep -v NXDOMAIN [martins@localhost ~]$ host twitter.com.multi.surbl.org. | grep -v NXDOMAIN twitter.com.multi.surbl.org has address 211.94.66.147 [martins@localhost ~]$
Allmost sounds like either a broken DNS somewhere or ... cache poisoning.
Would be interesting to check this with a capture running so you see whaqt server is telling this.
Bye, Raymond.