>Is it a free DNS server? Is it popular IP for troubleshooting?
Where did you find this IP address? What problem are you trying to
-- Rod --
October 16, 2004 12:55:22 PM
Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)
Thanks for reply.
Someone referred me to it as a free DNS server. The concept of free DNS
server is too good to be true.
"Rod Dorman" <email@example.com> wrote in message
> In article <uPcaVHssEHA.2196@TK2MSFTNGP14.phx.gbl>,
> A.M <firstname.lastname@example.org> wrote:
> >What is the IP address 22.214.171.124 ?
> >Is it a free DNS server? Is it popular IP for troubleshooting?
> Where did you find this IP address? What problem are you trying to
> -- Rod --
It's not quite as detailed as the explanation I'd seen before, but I figured it was accurate and to-the-point.
Additional DNS Servers can be found here: http://www.dnsserverlist.org/
That site also includes a "top three calculated DNS servers for your IP" listing, which could prove very useful for speed demons out there!
I am going to take credit for 126.96.36.199 being used as a DNS server entry in your router... here's the story-
In 1998, I was managing a network operations center with a few support technicians. Early on in training these guys, I told them to ping 188.8.131.52 to see if the Internet was 'up', because 184.108.40.206 seemed like the "411" from phone calling... easy to remember when you were panicky (as they could become when our network had problems).
One day 220.127.116.11 stopped responding to pings, and we freaked out for a second- but only it was down. I immediately responded with, "Well, then what about 18.104.22.168?", just incrementing the 1's to 2's. It NEVER went down. It soon became our defacto test host to ping.
After a very short while, we were curious as to what this address was used for... and not being from the NE where it was originally used in the GTE network, we didn't already know it was a secondary caching-only resolver. But we soon found out... and also found that it was usable from outside GTE's network. So when we needed a quick DNS server to use ... we used 22.214.171.124.
I think it spread- not only as a DNS server to use, but also as a ping host test. I've definitely used it in my network administration career and told others to use it. But to hear it come back as a suggestion to me makes me smile.
Personally I think it's insecure that Level3 (which now controls it) allows it to continue to resolve for clients outside of it's network... but that doesn't stop me from using it
That's a fine story. Don't take this the wrong way, but I think you're taking credit where credit is not due...
I'd say that most of the credit for it goes to BBN Planet and specifically John Hawkinson for having the foresight to reserve the 4.2.2/24 network block, and Brett McCoy who set up the 126.96.36.199 systems and wanted an easy to remember and type IP address. FYI: They originally wanted to do 188.8.131.52, but it was already reserved.
I mean it's impossible to tell how it spread, but I'm just playing the odds here...
It could be that you told "a few" people and one of them told someone from Cisco tech support who then made it SOP to tell everyone who called to use 184.108.40.206 for testing...
But it seems more likely that one of the biggest oldest Internet players deliberately put DNS on 220.127.116.11, made it public, and since these IPs were their primary DNS servers they published it widely: all their customers were supposed to be using 18.104.22.168 through 22.214.171.124 as their DNS servers.
Again, playing the odds it seems more likely that BBN Planet themselves made 126.96.36.199 famous and thereby it ended up in the original posters router.