Skip to content
betaDNS betaRegistrarSetup guide checked 2026-09-27

Domeneshop

Domeneshop API token setup: generate a Domeneshop token and secret; DNSMigrator uses them as the username and password for HTTP Basic Auth.

On this page

Domeneshop API token permissions

Credential type
API token and secret
Preview access
A token and secret that can list domains and read /domains/{domainId}/dns.
Apply access
The same token and secret with access to POST, PUT, and DELETE DNS record endpoints.
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

Domeneshop's public authentication documentation does not describe read-only, per-zone, or per-method token controls. Create a dedicated pair and revoke it when no longer needed. Check access only lists domains.

DNSControl id

creds.json TYPE
{
  "TYPE": "DOMAINNAMESHOP"
}

Create credentials

Generate a Domeneshop token and secret; DNSMigrator uses them as the username and password for HTTP Basic Auth.

Access you'll grant

Preview

A token and secret that can list domains and read /domains/{domainId}/dns.

Apply

The same token and secret with access to POST, PUT, and DELETE DNS record endpoints.

Domeneshop's public authentication documentation does not describe read-only, per-zone, or per-method token controls. Create a dedicated pair and revoke it when no longer needed. Check access only lists domains.

Before you start

  • A Domeneshop account containing the domains you want to connect.
  • Active DNS service on each domain whose records DNSMigrator will read or change.

Setup steps

0 of 5 done

  1. Open the API page

    Sign in to the Domeneshop control panel and open the API credential page.

  2. Generate a credential pair

    Create a dedicated API token and API secret for DNSMigrator. The official API uses the token as the HTTP Basic-auth username and the secret as its password.

    Basic usernametoken
    Basic passwordsecret
  3. Copy both values

    Copy the complete token and its paired secret. Keep the pair together and do not substitute your Domeneshop account password.

  4. Paste the token and secret

    Paste the token into API token and the paired secret into API secret, then check access.

  5. Revoke the pair after use

    When the connection is no longer needed, remove it from DNSMigrator and delete its dedicated credentials from the API page.

Troubleshooting

Domeneshop rejects the credentials

Confirm the token and secret are from the same generated pair and that the account password was not pasted into API secret.

A domain does not appear

The API lists domains on the credential's account. Sign in to that account and confirm the domain is present and its DNS service is active.

A record write returns a conflict

Domeneshop rejects DNS records that collide with an existing HTTP forward. Remove or change the forward in the control panel before applying that record.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
API tokentokenRequiredThe token generated at domeneshop.no/admin?view=api. It is the username in Domeneshop HTTP Basic Auth.
API secretsecretRequiredThe secret generated with the token. It is the password in Domeneshop HTTP Basic Auth, not your account password.

Capabilities

Create zones
No
List zones
Yes
DNSSEC
Not available through this connection
Minimum TTL
60 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • TLSA

Caveats

  • TTLs must be a multiple of 60 seconds between 60 and 604800; other values are rounded down.
  • Apex NS records come from the domain's nameserver settings and can't be edited as DNS records.
  • HTTP forwards are a separate API object and aren't migrated as DNS records.

Troubleshooting

Domeneshop rejects the credentials
Confirm the token and secret are from the same generated pair and that the account password was not pasted into API secret.
A domain does not appear
The API lists domains on the credential's account. Sign in to that account and confirm the domain is present and its DNS service is active.
A record write returns a conflict
Domeneshop rejects DNS records that collide with an existing HTTP forward. Remove or change the forward in the control panel before applying that record.