Treat nameservers as part of the asset

This URL still looks like a second VPS roundup. The first of those pages is now about whether a for-sale name even needs a server. This one is the hold-period problem: people treat nameservers as a hosting upgrade they can flip every month. That is how you drop email, look hijacked, or fail a transfer.

I’m Mostapha. I buy and sell domains from Morocco. A name you keep is an asset in a registrar account. DNS is the steering. If the checker says the letters are weak, you should not be redesigning nameservers; you should be deciding whether the name belongs in the portfolio at all. Failed investments are full of unused machines and busy DNS.

After you buy

Move the name into an account you control, with 2FA, before you point it anywhere clever. Lock it. Put MX somewhere you read if you published a contact. Do not “try a new VPS” the same afternoon as the purchase. That mixes a registrar event with a hosting event. If history was dirty, you already know from the history audit whether you should even be building.

Buying is documented in using the checker before you buy. This page assumes you already kept the name and now might break it with DNS restlessness.

While you hold

Leave nameservers still unless there is a reason: host dead, mail broken, you are parking after a hack. Benchmark blogs will tell you a new data centre will help “SEO of the domain.” For an investor, that sentence is usually bait. Speed of a lander does not reprice the letters — that argument is elsewhere. What does hurt: TTL thrash, accidental unlocking, a staging hostname that becomes the public A record. Keep experiments off the apex: don’t test on the name you might still sell.

Renew the names you mean to keep on purpose. An expired card plus an unlocked name is a transfer you did not intend. Renew early is portfolio work, not a hosting coupon.

When the name changes hands

Then you change DNS once, on purpose, or you do not change it at all. Many buyers want a registrar push and will point to the name themselves. Your job is a clean unlock, auth code, and a name that is not in the middle of a host migration. If they need the site, agree that in writing. Do not “helpfully” retarget A records during escrow. Panic DNS looks like theft. Lock and process: domain security.

If you are the buyer receiving a name, do not rebuild WordPress on the live hostname the day it arrives. Park or lander first, then a copy. The VPS, if any, comes after the asset is in your account — the opposite order of the old article on this URL.

Decision

  1. Checker first. Weak name: no DNS project.
  2. Hold: lock boring records, mail you read, and no monthly nameserver shopping.
  3. Transfer: one planned change or none. Registrar first, servers second.

This URL used to sell you a scalable VPS. It still exists so the Google row does not die. The investment habit it should teach is stillness: nameservers are part of the asset, not a hobby. For what to put on the name instead of a server, use the companion page: parking, a lander, or a VPS.

Leave a Comment