Re: root server update
Randy, I suspect it would help some of us small incompetent ISPs if you could provide a pointer to where *you* would have successfully found the NOC phone number. That way we could all deal with problems right away without adding more traffic to this list, and we could add this to one of these "how to be an ISP" FAQs, too. -matthew kaufman matthew@scruz.net Original message <m0vvShi-0007zZC@rip.psg.com> From: randy@psg.com (Randy Bush) Date: Feb 14, 10:49 Subject: Re: root server update
So now everyone will start sending test DNS requests to the servers and overload them even further.
What do you expect for folk who call people at home because they can't figure out how to call a NOC?
Welcome to the new "I am sooooo important that thinking is not required" internet.
randy -- End of excerpt from Randy Bush
On Fri, 14 Feb 1997, Matthew Kaufman wrote:
I suspect it would help some of us small incompetent ISPs if you could provide a pointer to where *you* would have successfully found the NOC phone number.
OK, everbody. Do this right NOW! Check the whois data on your NIC handle and check the whois data on your domain name, especially the technical contact. Als check the NIC handle for the tech contact. I'll bet most of you discover contact info that is missing or inaccurate. In my case whois MD130 shows the wrong area code because it has changed recently. If you want to do a better job of keeping this info up to date, set up a cron job to do whois queries on the relevant records and email them to you once a month on some random day (not the 1st of the month please). If this information were accurate and complete there would be a lot less flailing around when people need NOC contact info. Michael Dillon - Internet & ISP Consulting Memra Software Inc. - Fax: +1-250-546-3049 http://www.memra.com - E-mail: michael@memra.com
participants (2)
-
matthew＠scruz.net -
Michael Dillon