Selectel DNS Hosting Namecheap BasicDNS

Migrate DNS from Selectel to Namecheap.

8 record types move as they are. 3 things work differently at Namecheap, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

Selectel to Namecheap DNS migration differences

Generated from the same provider capability data the migration engine uses.

Moves as-is

A
AAAA
CNAME
MX
TXT
NS
CAA
ALIAS

SRV, DNAME, HTTPS, SVCB, SSHFP aren't available

Namecheap can't store SRV, DNAME, HTTPS, SVCB, SSHFP records through its API. They're marked Unsupported with the reason, never dropped silently.

Namecheap rewrites the whole host list

Every write to Namecheap's API replaces all records. We read, merge and write once, so records outside the migration survive.

Namecheap needs BasicDNS turned on

Namecheap only accepts records while the domain uses its BasicDNS nameservers, so records are written at cutover time rather than staged in advance.

A typical Selectel zone at Namecheap

Example records for example.com. Open any flagged row to read why it changed.

Selectel Namecheap

ExactA@
192.0.2.70
ExactAAAA@
2001:db8::70
ExactMX@
10 mx1.mail.example.net. +1
ExactTXT@
"v=spf1 include:_spf.example.net -all"
ExactCAA@
0 issue "letsencrypt.org"
ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
UnsupportedSRV_sip._tls
Not migrated
Namecheap doesn't support SRV records through its API.
ExactCNAMEwww
example.com.

How each record at Selectel DNS Hosting translates to Namecheap BasicDNS
Status	Type	Name	At Namecheap	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Unsupported	SRV	_sip._tls	Not migrated	—
Exact	CNAME	www	example.com.	1h

Set up the connections

Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.

How the move works

1
Connect Selectel
Connect Selectel with read-only access (Service user (username + password) with a project-scoped IAM token).
2
Connect Namecheap
Connect Namecheap (API user + API key, with our egress IP allow-listed). Write access is only used when you apply.
3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
4
Apply to Namecheap
We snapshot the Namecheap zone, write in batches, and leave Selectel untouched.
5
Verify
We query Namecheap's own nameservers for every record and compare the answers before you switch.
6
Switch nameservers
Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.

Good to know about Selectel

Only DNS Hosting (actual) zones are supported. Zones still on DNS Hosting (legacy, API v1) must be moved to the actual version in the control panel first.
Zones belong to a project; this connection only sees the project it signs in to.
Apex NS and SOA records are created and managed by Selectel and can't be changed.
A CNAME can't be placed at the zone apex; use ALIAS instead.
Each record set can hold at most 100 values.
Records you disabled in Selectel are left untouched and aren't imported.
Selectel doesn't publish API rate limits; requests are retried with backoff when throttled.

Access we need: Create a service user with the member role scoped to only the project that holds your zones. The reader role on that project is enough for read-only exports.

Good to know about Namecheap

Namecheap's API replaces the whole host list on every write, so we always read, merge and then write.
SRV records can't be managed through the API.
URL redirect records are Namecheap-specific and aren't real DNS records.

Access we need: API access enabled under Profile → Tools, with our static IP added to the allow-list.

Questions

Will there be downtime moving from Selectel to Namecheap?

Not if both providers serve the same answers during the switch. The records are copied to Namecheap and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.

Do I have to delete anything at Selectel?

No. We never write to Selectel. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.

What about DNSSEC?

If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at Namecheap and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?

Start a free preview