Transfer to masterhost

    Hello, Habr! I really want to talk about what I did the last three days, namely, the opposition to the support of the master host. I have been using the masterhost since 2006, mainly due to the fact that they had sane support, the intervention of which was often not necessary. Or the engineers did everything themselves. Now, apparently the situation has changed.

    Three days (!), For the whole three days they can’t start my domain and register vhost :)

    upd: Three more (!) Letters from the domain owner and the problem is solved, everything works! And it seems to me not without the help of a habr. :)
    upd2: Masterhost sent an apology letter, the incident is over.

    Well, now, in order:
    On the morning of this Sunday, our modest project was scheduled to be transferred to a second-level domain, to a site that was previously used by the same project, but only as a file storage. The result is deplorable and from this situation I see two ways out, one of which is moving to another hoster. Not for advertising, I really want to know your preferences.

    1. The support engineer confirmed that everything is in order in the DNS zone. This was not true, because I did not create (in the control panel) a new svalko.org domain. The engineer’s explanation was this: dns replication takes up to 72 hours. When the old ip from dns records disappeared in the world and all the aliases became available, my suspicions that it was not about DNS replication were confirmed.
    2. After the domain was created, all operations on it returned an error that not a single DNS zone was associated with it.
    3. DNS really began to be updated only after I made a change in the editor, records began to appear on ns1. I wrote in all letters THAT I REQUESTED DNS from ns.masterhost.ru directly, and that there was nothing to do with replication.

      So the first two days passed - the weekend - the best time to move has already been lost. :(
    4. I deleted data.old.domain.ru so as not to redirect, but simply to give content from all addresses from one platform. It was a fatal mistake. It was not possible for the host to create a synonym (vhost) because the owner also uses the masterhost. It so happened that he is on vacation in places where the Internet is GPRS in roaming, p. 5. Nevertheless, this did not stop me from using this domain for four and a year pennies.
    5. The owner of old.domain.ru went online to put the old.domain.ru CNAME on the new domain, but did not suspect that this would be another fatal error. Since there is no vhost, the masterhost issues a stub with a caliper phone.


    The result of all this - the old site lies, the new one started working in three days, and I already want to move to a more sane site (and cheaper, because it turned out that the masterhost had prices higher than market); and also, because masterhost support engineers seriously think that I decided to steal 3rd-level and 4th-level domains myself using vhost and forging FROM fields from e-mail. And this despite the fact that the domain owner has already registered CNAME on my new domain. :)

    Also popular now: