Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

rjbs (4671)

rjbs
  (email not shown publicly)
http://rjbs.manxome.org/
AOL IM: RicardoJBSignes (Add Buddy, Send Message)
Yahoo! ID: RicardoSignes (Add User, Send Message)

I'm a Perl coder living in Bethlehem, PA and working Philadelphia. I'm a philosopher and theologan by training, but I was shocked to learn upon my graduation that these skills don't have many associated careers. Now I write code.

Journal of rjbs (4671)

Thursday October 07, 2004
10:43 AM

goodbye gandi!

[ #21235 ]

The following is a dramatization. The content has been changed to ridicule the annoying.

Tuesday morning:

        Dear Gandi:

        I filed a request to have my nameservers changed on Thursday. It's Tuesday, and they still haven't been updated! This is very inconvenient.

Tuesday evening:

        Dear Ricardo,

        Actualluy, the site is online. After this kind of change, you need to wait for the propagation delay. This delay can last 48-72 hours.

Wednesday morning:

        Dear Gandi:

        It's been well over 72 hours, now. I don't know what you mean, but the DNS servers should be:

        x.ns.manxome.org - 66.92.232.24 y.ns.manxome.org - 67.18.176.115

Thursday morning:

        Dear Ricardo:

        Actually, the servers for manxome.org are : Name Server:A.NS.MANXOME.ORG Name Server:B.NS.MANXOME.ORG

Thursday afternoon:

        Dear Gandi:

        Fine. The problem is that the IPs are wrong. Your system has the correct ones. The TLD servers has the wrong ones.

Thursday afternoon, later:

        Dear Ricardo:

        You have to update the IP on the registry. Please go to our administration page / Others Functions / Nameservers records at Registry And update your reccords. ...so, to update my records, I need to update /their/ records of my NS servers and IP, and I need to update /the TLD/ records of my NS servers and IP. This is new. It is stupid. It is not documented. It took way to long to be explained.

So, goodbye Gandi! I registered at PairNIC this morning, and hope to be transferred quickly. For reasonable (or better!) service, plus a friend at the company, six dollars more each year is a bargain.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • this really is how it works. Registrars do maintain their own database of nameservers for sanity's sake, and they are a royal pain to change. When I have to change a nameserver's IP, I just create a new nameserver at the registrar and delete the old one once the transition is made. That way, no existing records have to be updated, and I don't have to interact with any people. :)
    • So I found on pairnic! I am /quite/ certain, though, that I did not need to do this in the past (admittedly, a year or more ago) when dealing with my records at Gandi. Perhaps their software was once more intelligent, and had to be altered for some reason.

      The key difference is that with Gandi, getting the information I needed was a serious pain. Pair had it quite easily available in their FAQ, where I found it after a few minutes of looking. There were no days of mental anguish.

      And, I see, now, that d
      --
      rjbs