Last night, I did a number of updates to domains, adding a few new name servers as secondaries, and removing one of the old primary servers. I got confirmation for all the changes, and everything looked OK. I went to bed. This morning, I got a number of phone calls from customers who are having all kinds of problems. It seems that the update for one domain, SENIE.COM, didn't get propagated into the root zone file. The old data is gone. The new data isn't there. My business isn't functioning well. It would appear there is something wrong with the program which creates the root zone files from the Network Solutions database. It would be nice if I could find someone inside NSI who understood this process and could or would do something about it. Instead, I talked with 8 or 9 people, all of whom tried to convince me it was "just a propagation problem." After explaining why it wasn't a propagation problem (the zone has been alive for many years, and so the old data SHOULD be there even if the new data hadn't gotten in), they agreed it seemed like a bug, but didn't know what to do about it. The domain in question is "senie.com" and while that domain has little in and of itself of importance, it's the domain where my name servers and mail server live, and a lot of customer email travels through there. I've updated all of my other zones to provide alternate paths for email, but some activity does rely on senie.com resolving. So, I've wasted a day of my life trying to get the problem solved. The best anyone at NSI could say is to see if it gets updated at 5PM today when they run the update. If it does, then that'll be the solution. If it doesn't, I'm basically screwed for yet another 24 hour period. The claim is there's no way to fix a screw-up mid-day. Without such a method, how's it even possible to know if the same screw-up will occur on the next update? The Internic operates with the same monopoly "we don't have to care" attitude as the telephone companies do, with the exception that in the case of the phone companies the public utilities commission is generally able to apply pressure and get a resolution. There appears to be no oversight of Network Solutions whatsoever, and no interest on their part in proactively fixing problems they've created. If anyone has any suggestions or ideas on getting access to someone with a clue at NSI, or has any method for helping cure this problem, I can be reached at: dts@amaranth.net (since dts@senie.com won't resolve presently) or 978-779-6813 Dan -- ----------------------------------------------------------------- Daniel Senie dts@senie.com Amaranth Networks Inc. http://www.amaranthnetworks.com
Actually, if anybody has a reliable way of getting things done at InterNIC I would like to hear about it. I have about 300 domain names that have the wrong billing address. Called and finally got to talk to a real person. He said they would to a global change if I sent them the list. Did that. They even sent email back saying that they had accomplished the global change. Imagine my surprise when the only thing that changed in their database was the info for my handle, dh47. Arrgh. This comedy of idiocy has been going on since January. Each iteration takes two to three weeks. I'm this close to flying to InterNIC and politely sit in front of their building until my customers needs are taken care of. Dirk On Tue, Jul 13, 1999 at 03:12:42PM -0400, Daniel Senie wrote:
Last night, I did a number of updates to domains, adding a few new name servers as secondaries, and removing one of the old primary servers. I got confirmation for all the changes, and everything looked OK. I went to bed.
This morning, I got a number of phone calls from customers who are having all kinds of problems. It seems that the update for one domain, SENIE.COM, didn't get propagated into the root zone file. The old data is gone. The new data isn't there. My business isn't functioning well.
It would appear there is something wrong with the program which creates the root zone files from the Network Solutions database. It would be nice if I could find someone inside NSI who understood this process and could or would do something about it. Instead, I talked with 8 or 9 people, all of whom tried to convince me it was "just a propagation problem." After explaining why it wasn't a propagation problem (the zone has been alive for many years, and so the old data SHOULD be there even if the new data hadn't gotten in), they agreed it seemed like a bug, but didn't know what to do about it.
The domain in question is "senie.com" and while that domain has little in and of itself of importance, it's the domain where my name servers and mail server live, and a lot of customer email travels through there. I've updated all of my other zones to provide alternate paths for email, but some activity does rely on senie.com resolving.
So, I've wasted a day of my life trying to get the problem solved. The best anyone at NSI could say is to see if it gets updated at 5PM today when they run the update. If it does, then that'll be the solution. If it doesn't, I'm basically screwed for yet another 24 hour period.
The claim is there's no way to fix a screw-up mid-day. Without such a method, how's it even possible to know if the same screw-up will occur on the next update?
The Internic operates with the same monopoly "we don't have to care" attitude as the telephone companies do, with the exception that in the case of the phone companies the public utilities commission is generally able to apply pressure and get a resolution. There appears to be no oversight of Network Solutions whatsoever, and no interest on their part in proactively fixing problems they've created.
If anyone has any suggestions or ideas on getting access to someone with a clue at NSI, or has any method for helping cure this problem, I can be reached at:
dts@amaranth.net (since dts@senie.com won't resolve presently)
or
978-779-6813
Dan
-- ----------------------------------------------------------------- Daniel Senie dts@senie.com Amaranth Networks Inc. http://www.amaranthnetworks.com
It'll take a lot of work for NSI to beat the morons at US Domain Registry. Their database was changed April 15th, and not by us. Since then, our "mariposa.ca.us" customers have been surviving on the secondary name server only, with consequent performance delays. We have asked US Domain Registry to (a) fix the problem and (b) give us any info on the source of the change. It takes approximately one month for them to reply to our e-mails. The responses are useless, and always late on a friday afternoon. One is tempted to believe that they have to get themselves good and drunk before dealing with the distatasteful chore of customer support e-mail. A decade ago, ISI was a place you could respect. ---------------------------------------------------------- Mike Bird Tel: 209-742-5000 FAX: 209-966-3117 President POP: 209-742-5156 PGR: 209-742-9979 Iron Mtn Systems http://member.yosemite.net/
On Tue, 13 Jul 1999, Daniel Senie wrote:
The claim is there's no way to fix a screw-up mid-day. Without such a method, how's it even possible to know if the same screw-up will occur on the next update?
I recall a few months ago when they screwed up aol.com and did a mid day build of the root zones, and distributed them. Sounds like they are willing to do special case repairs for "large" companies that have many lawyers. ======================================================================= Michael Lucking Michael@Lucking.COM
Hi, In the same vein, has anyone gotten the payment web site to work today? I can put a domain in, but then it goes to sleep and never returns anything. Tuc/TTSG
On Tue, Jul 13, 1999 at 05:21:02PM -0400, TTSG wrote:
Hi,
In the same vein, has anyone gotten the payment web site to work today? I can put a domain in, but then it goes to sleep and never returns anything.
Tuc/TTSG
It, like their PGP stuff, hasn't seemed to have worked for weeks if not months... (then again, I'm not sure I've even seen their PGP stuff work) -- Russell M. Van Tassell russell@cscorp.com "I'm out of my mind, but feel free to leave a message..."
On Wed, 14 Jul 1999, Russell Van Tassell wrote:
It, like their PGP stuff, hasn't seemed to have worked for weeks if not months... (then again, I'm not sure I've even seen their PGP stuff work)
Oh, their PGP stuff works all right. After spending lots and lots of time trying to get a pgp signature registered and get a couple domains changed to pgp authentication, I gave up. It was really really frustrating to say the least. Now, one of those domains I was trying to get set to pgp is now protected with a pgp authentication method. Mind you that It's been at least 2-3 years ago I tried to get the pgp to work and couldn't - but now when I need them changed all of a sudden my now defunct pgp key is needed to change the info. Oh well. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ----------------------------------------------------------------------
participants (7)
-
Daniel Senie -
Dirk Harms-Merbitz -
Forrest W. Christian -
Michael P. Lucking -
Mike Bird -
Russell Van Tassell -
TTSG