North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: I've just tried new.net's plugin. Don't.
On Wed, 14 Mar 2001, Chris Davis wrote: > response NS is searchpages.newdotnet.net, IP 64.208.49.135 > echo reply from 64.208.49.135 > echo reply from 64.208.49.135 > echo reply from 64.208.49.135 Just blackhole that route. Then no one from your network can get to it. of course, they would most likely have backup ips. > > > So, I pinged a nonexistent domain name and got replies from > test.new-net.vegas.idealab.com, 64.208.49.135 > > C:\>ping asldj.asogh.asdlfj > > Pinging test.new-net.vegas.idealab.com [64.208.49.135] with 32 bytes of > data: > > Reply from 64.208.49.135: bytes=32 time=60ms TTL=244 > Reply from 64.208.49.135: bytes=32 time=60ms TTL=244 > Reply from 64.208.49.135: bytes=32 time=60ms TTL=244 > Reply from 64.208.49.135: bytes=32 time=60ms TTL=244 > > > Seems that everything in the world not ending with an ICANN TLD goes to > 64.208.49.135. Have a look at http://64.208.49.135 > > Let's role play: > German Customer: "I can't access the Bank of America site. I get something > called Google" > NOC: "Can you ping www.bankofamerica.com?" > German Customer: "Yes" { pinging www.bankofamerika.kom } > NOC "Well, you have connectivity since you can ping it. Let's see what else > could be wrong. You get Google, you say???" > > > Now, tell me that's OK. > > > > >
|