Skip to content
dnsmigrator

IBM NS1 Connect Porkbun

Migrate DNS from NS1 to Porkbun.

12 record types move as they are. 2 things work differently at Porkbun, and the preview shows exactly which of your records they affect.

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

What works differently

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

Moves as-is

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • ALIAS
  • HTTPS
  • SVCB
  • TLSA

TTLs below 600s are raised

Porkbun's minimum TTL is 600 seconds. Shorter TTLs are raised to 600s and shown as translated.

A typical NS1 zone at Porkbun

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

NS1 Porkbun

  • TranslatedA@

    192.0.2.70

    TTL 300s is outside the allowed range. Set to 600s.

  • TranslatedAAAA@

    2001:db8::70

    TTL 300s is outside the allowed range. Set to 600s.

  • 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"

  • ExactSRV_sip._tls

    100 1 443 sip.example.net.

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect NS1

    Connect NS1 with read-only access (API key).

  2. 2

    Connect Porkbun

    Connect Porkbun (API key + secret API key). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to Porkbun

    We snapshot the Porkbun zone, write in batches, and leave NS1 untouched.

  5. 5

    Verify

    We query Porkbun's own nameservers for every record and compare the answers before you switch.

  6. 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 NS1

  • Records that use filter chains, answer metadata, data feeds or record links are copied as plain answers only and flagged in their comment. We never overwrite them on NS1.
  • DNSSEC has to be available on the NS1 account before it can be turned on for a zone.
  • NS1 changes one record set per request, so large zones take longer and count against the API rate limit.

Access we need: DNS → View zones for the preview; DNS → View zones and Manage zones to apply.

Good to know about Porkbun

  • API Access must be turned on per domain, and only domains registered at Porkbun can be managed.
  • The minimum TTL is 600 seconds and a zone holds at most 2,500 records.
  • URL forwarding is not migrated; the ALIAS/CNAME records Porkbun creates for it are copied as plain records.

Access we need: Porkbun keys have no read-only mode. Restrict the key to the domains you move and turn on API Access for each of them.

Questions

Will there be downtime moving from NS1 to Porkbun?

Not if both providers serve the same answers during the switch. The records are copied to Porkbun 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 NS1?

No. We never write to NS1. 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 Porkbun and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview