Show search and navigation.

 

Switching DNS Provider

Applies To:
RouteThis platform is designed to provide reliable, high performance, and secure DNS service. This DNS service consists of zone administration, traffic management, and custom routing policies.
ManagedThe Managed (Primary) or Secondary DNS module allows DNS zone management, authoritative DNS for zones managed outside of our network, and traffic distribution to multiple servers via load balancing or failover configurations.
SecondaryThe Managed (Primary) or Secondary DNS module allows DNS zone management, authoritative DNS for zones managed outside of our network, and traffic distribution to multiple servers via load balancing or failover configurations.

Creating a zone will not automatically redirect DNS traffic to our Route name servers. Once a zone is ready to handle production traffic, its traffic needs to be directed to our Route name servers by changing the name servers at your domain registrar. This may require the creation of glue records, which are also known as Host or Name Server records. This type of record should identify either of the following:

Vanity Name Servers

Upon creating a primary or secondary zone, our Route solution automatically creates NS records for each of our vanity name servers. Delegate your primary or secondary zone by pointing your glue records to our vanity name servers. The naming convention for our vanity name servers varies according to whether you are delegating a primary or secondary zone.

Zone Type Naming Convention

Example

Primary
ns#Represents a sequential number..<Zone Name>Identifies the name of your zone..

ns1.example.com.

Secondary
s#Represents a sequential number.ns#Represents a sequential number..<Zone Name>Identifies the name of your zone..

s1ns1.example.com.

We provide 4 vanity name servers and each one may fulfill IPv4 and IPv6 requests. As a result, our vanity name servers leverage 8 IP addresses to serve your zone. The following sample scenarios provide a listing of the IP addresses in use by our vanity name servers.

ClosedView a primary zone delegation example

This example indicates the records that will be created for a primary zone called "example.com."

Record Type

Name

 Value

NS

@

ns1.example.com.

NS

@

ns2.example.com.

NS

@

ns3.example.com.

NS

@

ns4.example.com.

A

ns1

192.16.16.5

A

ns2

192.16.16.6

A

ns3

198.7.29.5

A

ns4

198.7.29.6

AAAA

ns1

2606:2800:3::5

AAAA

ns2

2606:2800:3::6

AAAA

ns3

2606:2800:c::5

AAAA

ns4

2606:2800:c::6

Delegate this zone to our DNS service by adding all of our vanity name servers (e.g., ns1.example.com.) as custom name servers to your domain registrar.

ClosedView a secondary zone delegation example

This example indicates the records that will be created for a secondary zone called "secondexample.com."

Record Type

Name

 Value

NS

@

s1ns1.secondexample.com.

NS

@

s2ns2.secondexample.com.

NS

@

s3ns3.secondexample.com.

NS

@

s4ns4.secondexample.com.

A

s1ns1

192.16.16.5

A

s2ns2

192.16.16.6

A

s3ns3

198.7.29.5

A

s4ns4

198.7.29.6

AAAA

s1ns1

2606:2800:3::5

AAAA

s2ns2

2606:2800:3::6

AAAA

s3ns3

2606:2800:c::5

AAAA

s4ns4

2606:2800:c::6

Authorize our Route service to perform secondary DNS tasks by registering all of our secondary zone name servers with your domain registrar.

Information on how to delegate a domain is provided below.

Route-Branded Name Servers

A primary zone may be delegated to our Route-branded name servers instead of vanity name servers.

DNS testing tools may warn that stealth name servers have been detected. This warning is due to the presence of our vanity name servers within your zone. These vanity name servers cannot be modified or deleted.

ClosedTo delegate a primary zone using Route-branded name servers

  1. Define the following records within your zone:

    Record Type

    Name

    		 Value

    NS

    @

    ns1.edgecastdns.net.

    NS

    @

    ns2.edgecastdns.net.

    NS

    @

    ns3.edgecastdns.net.

    NS

    @

    ns4.edgecastdns.net.

    A

    ns1

    192.16.16.5

    A

    ns2

    192.16.16.6

    A

    ns3

    198.7.29.5

    A

    ns4

    198.7.29.6

    AAAA

    ns1

    2606:2800:3::5

    AAAA

    ns2

    2606:2800:3::6

    AAAA

    ns3

    2606:2800:c::5

    AAAA

    ns4

    2606:2800:c::6
  2. Delegate your domain by registering our Route-branded name servers (i.e., ns[1-4].edgecastdns.net.) with your domain registrar.

Domain Delegation

The exact procedure through which you can define glue records for your domain varies by domain registrar. This section provides procedural information for GoDaddy and Dyn.

For more information, please refer to the documentation provided by your DNS service provider.

ClosedTo delegate a domain from GoDaddy (primary zone)

Perform the following procedure:

  1. Determine which of the following you would like to use:

  2. Add each name server as described in the following GoDaddy article:

    Set custom nameservers for domains registered with GoDaddy

    Make sure to add all vanity or Route-branded name servers.

ClosedTo enable GoDaddy's secondary DNS support

Follow the instructions provided within the following GoDaddy article:

Enable Secondary DNS with GoDaddy nameservers as masters

Make sure to add all of our secondary zone name servers.

Our name servers are configured to submit AXFR requests to your DNS service provider.

ClosedTo delegate a domain from Dyn

Perform the following procedure:

  1. Log in to Dyn.
  2. Submit a delegation change to remove nsx.mydyndns.org or nsxxxx.dns.dyn.com.

  3. Specify one of the following sets of Route name servers:

    4. Please register all primary zone name servers.