DNSMentor
Demo Free trial

Supported provider

NS1 DNS, in the same place as everything else.

Does DNSMentor support NS1?

Yes. DNSMentor manages NS1 DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every NS1 change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.

Connect NS1 free for 7 days → What DNSMentor does

Connecting NS1

  1. Create the credential in NS1 NS1 Connect portal → the account menu (top right) → Account Settings → API Keys → Add Key. Give the key the 'DNS' permissions 'View zones' and 'Manage zones' and nothing else — an NS1 key with account permissions can also add users and change billing. If the key is scoped to specific zones, only those zones will appear in DNSMentor. The same screen has an 'Allow only these IP addresses' setting; restricting the key to DNSMentor's egress addresses is strongly recommended.
  2. Add the connection in DNSMentor Go to Admin → Providers & API keys, choose NS1, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
  3. Sync the estate DNSMentor discovers every zone the NS1 account holds and imports every record in them. This is a read operation — nothing is written to any zone.
  4. Group by client and start working Assign the imported domains to client portfolios, and the estate view, health scoring, checks and audit trail apply from that point on.

What NS1 asks you for

The exact fields DNSMentor needs, and where in NS1 to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.

API Key secret

NS1 Connect portal → the account menu (top right) → Account Settings → API Keys → Add Key. Give the key the 'DNS' permissions 'View zones' and 'Manage zones' and nothing else — an NS1 key with account permissions can also add users and change billing. If the key is scoped to specific zones, only those zones will appear in DNSMentor. The same screen has an 'Allow only these IP addresses' setting; restricting the key to DNSMentor's egress addresses is strongly recommended.

The sharp edge in NS1's API

Every provider API has one behaviour that catches integrations out. This is NS1's, and DNSMentor's adapter is written around it — the sort of thing you would otherwise discover during a migration.

The RRset model. NS1 has no per-record identity; the adapter synthesises one per answer and every write is a read-modify-write of the whole RRset. Add a second MX at the apex, delete the first, re-read.

What you get on top of the NS1 console

One estate, not one provider

NS1 zones sit beside every other provider your clients came with, grouped by the client who pays for them and searchable in one place.

56 checks before apply

The NS1 console will accept a second SPF record or an MX pointing at an address without comment. DNSMentor will not.

Approval and audit

A second pair of eyes where policy requires it, and a hash-chained record of who changed what — neither of which a provider console offers.

NS1 questions

Can I manage NS1 DNS alongside my other providers?

Yes. DNSMentor connects NS1 through its API and shows its zones in the same estate view as every other provider you connect — 26 are supported in total. Your engineers work in one interface instead of switching between provider portals, and the same checks, approval policy and audit trail apply regardless of which provider a domain happens to be with.

What credentials does DNSMentor need for NS1?

DNSMentor needs API Key for NS1. NS1 Connect portal → the account menu (top right) → Account Settings → API Keys → Add Key. Give the key the 'DNS' permissions 'View zones' and 'Manage zones' and nothing else — an NS1 key with account permissions can also add users and change billing. If the key is scoped to specific zones, only those zones will appear in DNSMentor. The same screen has an 'Allow only these IP addresses' setting; restricting the key to DNSMentor's egress addresses is strongly recommended.

Does DNSMentor move my zones away from NS1?

No. Your zones stay hosted at NS1 and remain authoritative there. DNSMentor reads and writes through the NS1 API, so nothing about your resolution path changes, and if you stop using DNSMentor the zones carry on exactly as they are.

Does DNSMentor validate NS1 changes before applying them?

Yes. All 56 checks run against the zone as it would exist after the change, whichever provider hosts it. The change is then simulated, routed for approval if policy requires it, written through the NS1 API after re-reading live state, and independently verified in public DNS afterwards.

Other providers DNSMentor manages

Connect NS1 in about five minutes.

Paste one credential, sync, and see every zone in that account. It is a read operation — nothing is written until somebody presses apply.

Book a look → Or try it yourself first

No card. No trial clock. UK-hosted, and we will tell you which providers we have actually proven before you ask.

Last updated