Hosting DNS for a domain bought elsewhere

Hosting DNS for a domain bought elsewhere

Your domain is registered with another registrar (OVHcloud, Gandi, IONOS…) and you want Webgune to host its DNS zone? There are two steps: prove the domain is yours, then point its nameservers to ours.

1. Prove the domain is yours

In Domains, click New domain and enter your domain. Webgune gives you a record to create at your current DNS provider, meaning wherever your domain is managed today (often your registrar):

If adding a TXT record is awkward at your provider, a CNAME _webgune-challenge pointing to ….verify.nd0.net is exactly the same proof.

Depending on the interface, the "Name" field expects _webgune-challenge alone or the full name (_webgune-challenge.my-domain.com). Both work.

As soon as the record is visible, the DNS zone is created on our side. The check runs again on its own every 2 minutes, and the Check now button speeds it up. The request stays valid for 7 days. Once the domain is verified, you can delete the record.

Why this step? Our nameservers are shared by all customers. Without proof, anyone could register your domain with us before you do. If several accounts claim the same domain, the first one to prove it gets it.

Your nameservers already point to us? The proof has to come from a DNS provider other than us. Temporarily switch back to the original nameservers at your registrar, add the record, then continue with the next step.

2. Find your registrar

Nameservers are changed at your registrar, and only there. The Nameservers tab of the domain page identifies it automatically when the extension allows it. Otherwise, a WHOIS lookup will tell you, on the "Registrar" line:

• lookup.icann.org (new window) for most extensions;
• the Afnic WHOIS (new window) for .fr domains.

3. Replace the nameservers

At your registrar, replace all current nameservers with:

ns1.nd0.net
ns2.nd0.net

Don't leave any old server next to ours: some visitors would keep querying the old zone, and the domain would behave unpredictably.

Delegation usually takes a few minutes to a few hours, and up to 48 hours. The domain switches to Active on its own as soon as it is visible.

For some extensions (.fr, .de…), the registry checks that the new servers already answer for the domain before accepting the change. That is already the case after step 1, since the zone is created at verification.

Guides by registrar

Menus change regularly. If a label no longer matches, look for your domain's "Nameservers", "DNS servers" or "Name servers" section.

OVHcloud

1. In the Control Panel, open Web Cloud > Domain names, then your domain.
2. DNS servers tab, Modify DNS servers button.
3. Enter ns1.nd0.net in DNS server and confirm with +. Do the same for ns2.nd0.net, and remove the old servers.
4. Click Apply configuration, then Apply. Follow progress in Ongoing operations.

Gandi

1. Click Domain in the left menu, then your domain.
2. Nameservers tab, Change button.
3. Choose the External option, enter ns1.nd0.net and ns2.nd0.net, then save.

If you had Gandi's Premium DNS option, this change deactivates it.

IONOS

1. Open your domain list.
2. On the domain's row, click the gear icon in the Actions column, then the name server setting.
3. Choose to use your own name servers, enter ns1.nd0.net and ns2.nd0.net, then save.

o2switch

1. In your o2switch customer area, open the domain's management page.
2. In the DNS servers section, replace ns1.o2switch.net and ns2.o2switch.net with ns1.nd0.net and ns2.nd0.net, then confirm.

If in doubt, o2switch support can make the change for you.

Infomaniak

1. In the Manager, open domain management, then your domain.
2. DNS servers in the left menu, Modify DNS servers button.
3. Tick Custom name servers, enter ns1.nd0.net and ns2.nd0.net, then confirm at the bottom of the page.

LWS

1. In the customer area, click Manage next to the domain.
2. Open DNS servers and tick Other servers.
3. Enter ns1.nd0.net and ns2.nd0.net, then confirm.

Hostinger

1. In hPanel, open Domains, then Manage next to the domain.
2. DNS / Nameservers section, Change Nameservers button.
3. Choose to enter your own nameservers, enter ns1.nd0.net and ns2.nd0.net, then save.

GoDaddy

1. In your domain portfolio, select the domain to open Domain Settings.
2. Click DNS, then Nameservers.
3. Choose I'll use my own nameservers and enter ns1.nd0.net and ns2.nd0.net.
4. Click Save, then Continue. If the domain has Domain Protection, GoDaddy asks for a confirmation code.

Namecheap

1. Open Domain List, then Manage next to the domain.
2. In the Nameservers section, choose Custom DNS.
3. Enter ns1.nd0.net and ns2.nd0.net, then confirm with the green checkmark.

Squarespace

Google Domains domains were taken over by Squarespace, so this guide covers them too.

1. Open Settings > Domains, then your domain.
2. In the nameserver settings, click Edit, then choose Use custom nameservers.
3. Enter ns1.nd0.net and ns2.nd0.net, then save.

Porkbun

1. In Domain Management, open the domain's Details menu.
2. Click the edit icon of the Nameservers field.
3. Delete the existing servers, enter ns1.nd0.net and ns2.nd0.net (one per line), then click Save Nameservers and confirm with Submit.

Cloudflare

A domain bought from Cloudflare Registrar cannot change its nameservers: Cloudflare enforces this in its terms. To host its zone with us, first transfer the domain to another registrar, which is possible 60 days after purchase or the last transfer.

If your domain is only managed by Cloudflare DNS but registered elsewhere, change its nameservers at that original registrar, not in Cloudflare.

Check the delegation

dig NS my-domain.com +short

The answer must list ns1.nd0.net. and ns2.nd0.net., and only them. Then manage your records from the DNS tab: see Managing your DNS records.