For those of you who haven't noticed, Network Solutions has been
demonstrating their complete and total lack of competence over the past 10
hours, AGAIN.
At 18:33 -0500, I sent in a new domain template.
At 22:36 -0500, I received the following from the mailer daemon:
----- The following addresses had transient non-fatal errors -----
<hostmaster@internic.net>
----- Transcript of session follows -----
... while talking to rs.internic.net.:
DATA
<<< 451 qq write error or disk full (#4.3.0)
<hostmaster@internic.net>... Deferred: 451 qq write error or disk full (#4.3.0)
Now, isn't that nice. They have tons of money to spend on television
advertisements and banner ads on the search engines/indexes yet, they can't
fork out any cash to keep their systems running? Hard drive space is dirt
cheap!
At 04:18 -0500, I received the following:
The original message was received at Sat, 16 Jan 1999 04:17:47 -0500 (EST)
from biprrs1.lb.internic.net [192.168.120.39]
----- The following addresses had permanent fatal errors -----
hostmaster@mail-hub-mgt.mgt.internic.net
(expanded from: <hostmaster@internic.net>)
----- Transcript of session follows -----
... while talking to mail-hub-mgt.mgt.internic.net.:
RCPT To:<hostmaster@mail-hub-mgt.mgt.internic.net>
<<< 550 <hostmaster@mail-hub-mgt.mgt.internic.net>... Relaying denied
550 hostmaster@mail-hub-mgt.mgt.internic.net... User unknown
Reporting-MTA: dns; opsmail.internic.net
Received-From-MTA: DNS; biprrs1.lb.internic.net
Arrival-Date: Sat, 16 Jan 1999 04:17:47 -0500 (EST)
Final-Recipient: RFC822; <hostmaster@internic.net>
X-Actual-Recipient: RFC822; hostmaster@mail-hub-mgt.mgt.internic.net
Action: failed
Status: 5.1.1
Remote-MTA: DNS; mail-hub-mgt.mgt.internic.net
Diagnostic-Code: SMTP; 550 <hostmaster@mail-hub-mgt.mgt.internic.net>...
Relaying denied
Last-Attempt-Date: Sat, 16 Jan 1999 04:17:49 -0500 (EST)
Relaying denied? So, their own mail hub won't accept mail for
hostmaster@internic.net now?
I don't care if they are "under heavy load resulting from domain
speculators." What I care about is that they have been contracted to
provide a service and they are failing miserably. Domain speculators are
not a new thing and they are not going away any time soon. The internet
community as a whole depends on the InterNIC to be reliable. Their
inability to deliver reliable service has impacted the entire net multiple
times in the very recent past.
Now, they can not deal with simply accepting email for delivery to
hostmaster@internic.net?
Something needs to change and it needs to change NOW.
I expect to see a full disclosure press release from Network Solutions
concerning this matter.
I want to know why there are not backup mail exchangers in place to at the
very least queue email in the event of a failure.
; <<>> DiG 2.2 <<>> -t internic.net
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; Ques: 1, Ans: 1, Auth: 5, Addit: 6
;; QUESTIONS:
;; internic.net, type = MX, class = IN
;; ANSWERS:
internic.net. 44809 MX 100 rs.internic.net.
;; AUTHORITY RECORDS:
internic.net. 75543 NS rs0.internic.net.
internic.net. 75543 NS ns2.internic.net.
internic.net. 75543 NS noc.cerf.net.
internic.net. 75543 NS ns.isi.edu.
internic.net. 75543 NS ns0.clt.internic.net.
;; ADDITIONAL RECORDS:
rs.internic.net. 639 A 198.41.0.6
rs0.internic.net. 167818 A 198.41.0.5
ns2.internic.net. 119444 A 198.41.0.11
noc.cerf.net. 32356 A 192.153.156.22
ns.isi.edu. 102407 A 128.9.128.127
ns0.clt.internic.net. 138901 A 198.17.208.6
;; Total query time: 18 msec
;; WHEN: Sat Jan 16 05:00:32 1999
;; MSG SIZE sent: 30 rcvd: 253
Note the one, single mail exchanger?
I want to know why there is not a monitoring and reporting system in place
to let someone know when the mail exchanger is running low on drive space.
If the above two systems are actually in place, I want to know who did not
do their job and I want to see news footage of them in the unemployment
line in Herndon, VA.
I want to know why the performance of the InterNIC has deteriorated to such
a point that they are the first thing I check in the event of erratic
behavior of ANYTHING on the net and in most cases are at least partly to blame.