Getting started

You can register a new domain through echo reply, or keep your current registrar and use echo reply to host DNS. Choose the path that fits your domain. If you are moving DNS for a domain you already use, keep its current DNS service active until the new records and delegation have been checked.

Before you start

  • Registering a new domain: choose the name you want and have the registrant contact details ready. The registration flow shows the current price and any details required for that domain.
  • Using a domain you already own: make sure you can access the registrar that controls its nameservers, and have a record list or export from your current DNS provider.

1. Create and activate your account

Open dns.echo-reply.net, choose Sign up, and enter your email address and a password. Accept the privacy policy and complete the human-verification field.

Activate the account using the link sent by email, then sign in. Create an Organisation if the account does not already belong to one. Registrations, zones, and permissions are scoped to an organisation. To register a domain, your role must allow registration changes; an organisation owner can help if you do not see the relevant action.

2. Choose how to use your domain

Register a new domain with echo reply

  1. Open Register New.
  2. Search for a complete domain name, such as example.dk, or search for a name and choose from the available endings.
  3. Select the organisation that will own the registration and provide the registrant details requested by the flow.
  4. Review the current quote and any terms shown. Complete checkout if payment is due.
  5. Follow the transaction in Registered Domains. A submitted registration can remain pending while the registrar or registry processes it.

DNS hosting for a domain registered through echo reply is included. The registration flow offers a DNS zone for it; if you do not create the zone during registration, you can create or link one from the registration details later. See register and manage domains for the full registration, renewal, and transfer guide.

Host DNS for a domain registered elsewhere

  1. Open Zones and choose Add Zone.
  2. Select the organisation, enter the domain name, and review the SOA administrator email and automatic-PTR setting.
  3. Choose Save. The platform creates the zone with managed SOA and NS records and opens the record list.

An eligible user can claim one free Basis zone. Eligibility is tied to the user, not granted afresh for every organisation. If the organisation has no remaining zone capacity, the interface warns you and may create the new zone disabled. Check Billing and free capacity before expecting it to serve records. This DNS-hosting path does not transfer the registration; the domain stays with its current registrar.

3. Add and check your DNS records

For an existing domain, recreate the records from your current provider in the new zone. The web interface does not offer a general BIND zone-file import. For a large migration, keep the export as your source of truth and contact support@echo-reply.net before changing delegation. For a newly registered domain, add the records its website, email, and other services need.

Pay particular attention to MX, TXT, CAA, and service records. Query each nameserver displayed for the zone directly, replacing the example hostname with the value shown in your zone:

dig @new-nameserver.example example.dk SOA +short
dig @new-nameserver.example example.dk MX +short
dig @new-nameserver.example www.example.dk A +short

Do not continue with an existing-domain DNS move until the direct answers match the records you intend to publish. See the record types reference for entry guidance.

4. Update nameservers when you host an existing domain here

At the domain’s current registrar, replace its nameserver delegation with the NS hostnames displayed in the echo reply zone. Registrar wording varies; look for Nameservers, Name servers, or Delegation. If you registered the domain through echo reply, follow its registration status and domain details instead of changing nameservers at an external registrar.

The zone’s enabled or disabled status is not proof that the public parent delegation points to it. Check the public delegation independently:

dig NS example.dk +short
dig +trace NS example.dk

Resolver caches expire according to previously published TTLs, so there is no single guaranteed propagation time. Keep the old provider serving the zone until the delegation and the resolver paths important to you consistently use the new nameservers.

5. Set up DNSSEC after delegation is stable

If the old provider signs the zone, follow the DNSSEC migration sequence before switching nameservers. A DS record that refers to the old provider’s key can make the new zone fail DNSSEC validation.

For a newly registered, unsigned domain—or an existing domain after its new delegation is stable—follow DNSSEC setup.

Next steps