DirectNIC requests BellSouth help.

Thu Sep 1 20:20:12 UTC 2005

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?
-- 
Paul Vixie