Straight from the source:
"If anyone who works for or has connections with Bell South or Telcove
is reading this, tell us what it's going to take to get those OC3s
back up and running. We will try to coordinate and make it happen. "
directnic's nameservers appear to have been botchified during some kind of
hurried attempt to mirror them outside of new orleans.
according to the .COM servers:
ns0.directnic.com. 2D IN A 204.251.10.100
ns1.directnic.com. 2D IN A 66.115.160.187
according to the .100 server shown above:
ns0.directnic.com. 1D IN A 204.251.10.100
ns1.directnic.com. 1D IN A 66.115.130.188
according to the .187 server shown above:
ns0.directnic.com. 1D IN A 204.251.10.100
ns1.directnic.com. 1D IN A 66.115.130.188
according to the .188 server shown:
;; res_nsend: Connection refused
this is going to make directnic's customers, or any zone served by these
two nameservers, harder to reach than they strictly need to be. can someone
from directnic contact someone at verisign, or vice versa, and get this
straightened out?
Do they have a TSP number issued by the US Government for emergency
restoration?
No?
Then they are probably in the back of the line after federal, state and
local emergency telecommunication needs.
directnic's nameservers appear to have been botchified during some kind of
hurried attempt to mirror them outside of new orleans.
<...>
good eyes paul, been in contact with people over there and it's getting fixed. i hadn't been following nanog but i'm floating in the IRC stuff (since I'm also freenode staff...). Mike B. relays back thanks that the problem is being fixed. (sorry if this is duplicate information!)