Hopp til innhold

How do I move my domain without my website and email going down?

Moving your domain to Sedes leaves its nameservers alone, so the move itself stops nothing. What can stop is DNS, email or hosting at the registrar you leave. Ask them what ends and when, move the domain, put your records in at Sedes, then ask us to switch the nameservers.

Publisert 20. november 2026

Les denne på norsk

Moving a .no domain to Sedes does not touch its nameservers, so the transfer on its own stops nothing: your website and email keep running on the DNS they use today. What can stop them is the DNS, email or web hosting run by the registrar you are leaving, if they end those services when the domain leaves. So: find out who runs each, and ask that registrar in writing what stops and when. Then move the domain, put your records in at Sedes while the old DNS still answers, and only then have us switch the nameservers. The order matters because we copy no records for you and cannot run DNS for a domain until it has moved to us.

If the old DNS stops the moment the domain leaves, that order is not enough: see the last case below.

What actually moves when you transfer a domain?

Three jobs sit behind a domain:

  • The registrar holds your domain at Norid. A transfer changes only this.
  • Your DNS host runs the nameservers (the servers that answer for your domain) and the DNS records on them. A transfer to us leaves the nameservers as they were.
  • The mail and web servers are where the records point.

All three may well be done by one company, but each can stop or carry on separately. The longer version: Can I move just my .no to Sedes and keep my other domains at Domeneshop?

Find out who runs your DNS, email and website today

  1. Your DNS host. Look the domain up in Norid's DNS check, which shows its nameservers. The name usually shows the provider: ns1.hyp.net is Domeneshop, ns1.sedes.no is us. Norid's domain lookup shows which registrar the domain is with.
  2. Your email. Whoever your MX records point to runs your mail. That need not be your registrar: sedes.no is registered with us, and its MX records point to Google. See What is an MX record, and what does the priority number do?
  3. Your website. Whoever the A or AAAA record on the bare domain and the www record point to runs your site. See A record or CNAME record: which one do you need?
  4. Copy every record. In the control panel of whoever runs your DNS today, write down or export every record: its name, type and value, and the priority on MX records. You enter the records at Sedes one at a time (there is no zone file import), so keep a readable list outside that control panel.

Ask the registrar you are leaving what stops, and when

Ask them in writing: does your DNS keep answering for my domain after the move, and for how long; does my email with you stop; does my web hosting stop. Keep their answer.

What their own pages say (in Norwegian; our translations):

  • Webhuset: their email and web hosting "will stop working when the transfer is complete, unless you set up equivalent services with the new provider before you move". The page does not say how long their DNS keeps answering.
  • Domene.no: "when a name is moved away, all existing services for that name are cancelled at the end of the current period". The page does not say whether DNS is one of those services.
  • Domeneshop: their terms count moving a domain away as "a cancellation of the services with us, unless you have informed us in advance that the services are to continue". How do I move my .no domain from Domeneshop to Sedes? covers what follows.
  • One.com, Uniweb and anyone else: ask them.

Webhuset, Domene.no, One.com and Uniweb are in the table in How do I move my .no domain to Sedes?. If their answer is unclear, write to hei@sedes.no before you ask for the authorisation code.

The order to follow, by their answer

Their DNS keeps answering after the move

  1. Move the domain, as in How do I move my .no domain to Sedes?. With the authorisation code, Norid completes the transfer at once. The order page then says "The domain is now with Sedes, on the same nameservers as before."
  2. Put your records in at Sedes. The domain is now in your Sedes account. Add every record from your copy on the DNS tab, and the mail records on the Email tab. Both tabs will say: "This domain uses other nameservers than ours. Records you save here have no effect until the domain uses our nameservers. You can change them under Nameservers." That is what you want: the records wait at Sedes, unused, while the old DNS keeps serving the domain.
  3. Compare with your copy. The Zone file view on the DNS tab shows everything we hold for the domain.
  4. Write to hei@sedes.no and ask us to switch the domain to our nameservers. Leave the Nameservers tab alone, even though the notice points there. We publish your records first, wait until our nameservers answer for the domain, and only then ask Norid to change the nameservers; if a step fails, the domain stays on the old ones. We will not switch a domain we hold no records for.
  5. Watch for the switch. It has happened when the Nameservers tab or Norid's DNS check shows ns1.sedes.no to ns4.sedes.no. The two days count from then. If it still shows the old ones a few hours after you asked, write again.
  6. Check that it worked (below), and end the old DNS service last, after the checks pass and two days have passed since the switch. The app says: "It can take up to two days before the change works everywhere."

Their email or web hosting stops

If your mailbox or web hosting is with the registrar you are leaving and ends with the move, get the replacement working first, and point the records at it with whoever runs your DNS today, before you ask for the code. Webhuset's page sets that condition. For mail, see How do I get email on my domain? Then update your copy and follow the first case. Moving the mailboxes or the site itself is not covered here.

Their DNS stops the moment the domain leaves

This is the gap. Today we cannot run DNS for a domain until it has moved to us, so if the old DNS stops at the transfer, nothing answers for your domain until the switch. You can make the gap shorter. You cannot make it go away.

  1. Ask them to keep DNS running for a few days after the move. Domeneshop's terms allow services to continue if you tell them in advance. Ask others the same; if they agree, follow the first case.
  2. If they will not, keep the gap short. Before you ask for the code, write to hei@sedes.no with your copy of the records, so we know it is coming. The transfer happens when you submit the code, so you choose when the gap starts; choose a time when you can do the rest straight away. Right after the transfer, enter every record from your copy on the DNS and Email tabs yourself, as in step 2 of the first case. Then write to hei@sedes.no, ask for the switch, and watch for it as in step 5.

The gap lasts from the transfer until the switch is made and Norid has published it; Norid publishes a change within about two and a half hours. Even then, some visitors and senders may be sent to the old, silent nameservers for a while; the app says up to two days.

While nothing answers, sending mail servers must queue the message and retry, generally for at least four to five days, so mail is usually delayed, not lost. If a DNS host does answer, but says the domain does not exist or has wrong MX records, that counts as an error and mail can bounce. Your website is unreachable until the switch takes hold. It is a real interruption, better planned than discovered.

How long before the new nameservers work?

A nameserver change reaches .no's own servers within about two and a half hours: Norid generates the .no zone every other hour and publishing takes about half an hour. Resolvers that already know the old nameservers may keep using them for a while after that, and the app says up to two days.

Having the records at Sedes before the switch also matters because a "this name does not exist" answer is cached too, so a record added late can stay missing for a while. If a value changes, lower its TTL (time to live: how long others may keep a copy of an answer) at whichever DNS host serves the record at the time, if they let you, at least one old TTL before the change.

Check that it worked

  1. Norid's DNS check shows ns1.sedes.no to ns4.sedes.no, as in step 5.
  2. Open your website, both the bare domain and the www address.
  3. Send an email from an outside address to an address on your domain, then reply to it.

When it does not work

The website or email stopped right after the transfer

The nameservers did not change, so it is the old DNS, mail or hosting that stopped. Ask the old provider first, but do not wait on them: the domain is already in your Sedes account, so enter every record from your copy now, as in step 2 of the first case, and write to hei@sedes.no asking for the switch now. If you have no copy, ask the old provider for your records: we cannot fetch them for you.

It stopped after the switch

A record is missing or wrong at Sedes. Compare the DNS and Email tabs with your copy and add what is missing. If everything matches, write to hei@sedes.no with the domain name.

Mail bounces

Wrong MX records can make mail bounce. With no MX records at all, senders try the domain's own address instead, so mail goes somewhere that usually cannot take it. Check the MX records on the Email tab against your copy. If they match and mail still bounces, write to hei@sedes.no with the domain name and the bounce message, from another address if your own mail is down.

How this actually works

Norid holds the delegation: the list of nameservers that answer for the domain. Your DNS host holds the zone: the records on those nameservers, pointing to the mail and web servers. A transfer changes only who administers the domain at Norid, so the delegation and everything behind it carry on.

The trick is the order: records first, nameservers after. Nameservers pointing to a DNS host with no records take the domain dark; with the records already there, the switch changes who answers, not the answers. While caches run out, some resolvers ask the old nameservers and some ask ours; with the same records on both, nobody notices.

More on record types and TTL: Your domain's DNS settings, explained. Cost and the time you have paid for: Do I pay for a renewal when I transfer my .no domain to Sedes?

Sources: Norid on zone file production; RFC 1035, RFC 2308 and RFC 5321; the help pages of Webhuset and Domene.no; Domeneshop's terms. Read 18 November 2026.

Fikk du svar på det du lurte på?