10
« on: August 31, 2011, 1734 UTC »
Corq is right about nameservers not answering queries, ns1.joplinglobe.com does answer pings, so whatever A record that name points to is up, but it does not answer on port 53 (DNS). ns1.joplinglobeonline.com looks like it doesn't even have an A record anymore. the joplinglobe.com site uses teklinks.com for secondary and tertiary name service so that site still works. After running ISPs for 12 years, I'm guessing someone did a favor for FRN by hosting their zone file on the dl, and after the tornado mess someone decided not to do DNS on ns1.joplinglobe.com any more and frn.net "vanished". Programmatically, moving a .net is no different from moving a .com or .info or .whatever, BIND (DNS software) doesn't care. Moving domains becomes a chore when critters with opposable thumbs get involved.