--- title: "Point your domain to E2E nameservers" description: "Switch your domain to E2E DNS by setting E2E's two nameservers at your registrar, after you copy its records over and test them." content_type: "how-to" product: "dns" platform: "MyAccount" url: "/myaccount/dns/how-to/point-your-domain-to-e2e-nameservers/" relationships: {"requires":["/myaccount/dns/how-to/add-a-domain/"]} --- # Point your domain to E2E nameservers Your domain's nameservers decide which DNS service answers for it. Once you set E2E's two nameservers at your registrar, the records you keep in MyAccount become the answers the internet gets for your website, your email, and everything else on the domain. You make the change at your registrar, the company you bought the domain from. ## Before you begin - The domain is on **Manage DNS**. Adding it there is a separate step from pointing the nameservers. See [Add a domain](/myaccount/dns/how-to/add-a-domain/). - Every record the domain uses at its current DNS provider is also on E2E: its website, `www`, email, and any verification records. **Diagnostics** gives this as the first step, so that every name keeps answering after the switch. See [Add a DNS record](/myaccount/dns/how-to/add-a-dns-record/) and [Set up email records](/myaccount/dns/how-to/set-up-email-records/). - You can sign in to your registrar's control panel. - Your role in the project lets you create resources, which is what shows **Nameservers**. ## Test the records on E2E first E2E's nameservers answer for your domain as soon as you add it, so you can test every record before the switch. Ask an E2E nameserver directly: ```bash dig @ns50.e2enetworks.net.in example.com A +short dig @ns50.e2enetworks.net.in www.example.com A +short dig @ns50.e2enetworks.net.in example.com MX +short ``` Each command prints the record's value, such as `203.0.113.10`, or `10 mail.example.com.` for an MX record. An empty output means E2E has no record of that name and type yet. Compare each answer with the value at your current provider. To test your website on its new server before the switch, point your own computer at it with a hosts file entry. Add a line like this to `/etc/hosts` on Linux or macOS, or to `C:\Windows\System32\drivers\etc\hosts` on Windows, with your server's address: ```text 203.0.113.10 example.com www.example.com ``` Your computer then opens the site from that address, whatever DNS says. Remove the line once you have finished testing. ## Set E2E's nameservers at your registrar 1. In MyAccount, on **Manage DNS**, click **Nameservers**. The dialog lists **Nameserver1:** `ns50.e2enetworks.net.in` and **Nameserver2:** `ns51.e2enetworks.net.in`. 2. Sign in to your registrar's control panel, and open the domain's nameserver settings. 3. Replace every current nameserver with these two: ```text ns50.e2enetworks.net.in ns51.e2enetworks.net.in ``` 4. Save the change at your registrar. The registrar passes the change to the domain's registry. Resolvers on the internet move to E2E's nameservers as their copy of the old ones expires, which can take up to 48 hours. During that time some visitors reach the old provider's records and some reach E2E's, which is why the records must match. ## Check that the domain points to E2E To see the nameservers the internet has for your domain, run: ```bash dig NS example.com +short ``` Once the change has spread, the output is E2E's two nameservers: ```text ns50.e2enetworks.net.in. ns51.e2enetworks.net.in. ``` In MyAccount, open the domain on **Manage DNS** with **Actions**, then **Manage**, and click **Diagnostics**. The nameserver check reads **Your nameservers point to E2E Networks cloud nameservers.** with **No fix required.** While it reads **Your DNS is currently hosted with another provider.**, it lists the nameservers it found under **Current nameservers are:**. Click the refresh button to run the checks again later. See [Check your domain with Diagnostics](/myaccount/dns/how-to/check-your-domain-with-diagnostics/). Your domain now answers from E2E DNS. Changes you make in MyAccount reach E2E's nameservers within about 10 seconds. If the domain does not resolve after the switch, see [Troubleshooting DNS](/myaccount/dns/troubleshooting/dns/).