When configuring your domain to use our DNS service you should specify the following servers as your domain's name servers.

  ns1.division120.net
  ns2.division120.net
  ns3.division120.net
  ns4.division120.net

Yes. Division120 supports wildcard / catch-all records.

To setup a wildcard record just enter * for the host name. Our name servers will first check for an actual host record for the requested name. If the host name doesn't exist our name servers will then deliver the wildcard record.

Division120 currently supports A, AAAA, CNAME, MX, PTR, and TXT records. NS and SOA records are also supported but are automatically managed by Division120. If there's a record type you require that we don't support please let us know and we'll do our best to add it.

If your domain was working and has stopped working it has likely expired. This is the most common issue we see. You'll have to contact your registrar to renew your domain.

If you're adding a new domain and it's not working correctly then the domain likely isn't configured correctly. The domain must be registered and the name server records must be configured to use Division120's name servers. Each domain registrar has slightly different procedures for updating name servers. Typically the domain registrar will have a customer control panel that users can user to make these changes. Occasionally we see Division120's name servers added to a domain's existing name servers. This will cause inconsistent service. You must delete your existing name servers and replace them with Division120's name servers.

If you've just updated your domain to use our name servers it may take 24 hours before it begins to operate. This delay is due to caching. During this period some visitors may still receive responses from your old name servers.

A third level or fourth level domain such as  'www.beta.example.com' can be added in two ways. The hostname field accepts nested subdomains so if your domain was 'example.com' you would simply type 'www.beta' in the host field. As an alternative you could also create a new zone named 'beta.example.com' and then add 'www' as a new host within 'beta.example.com'.

We're working hard on introducing IPv6 support and hope to have full support for IPv6 by the end of 2010.
 
We can currently host IPv6 address records (AAAA) and in the summer of 2010 we will be rolling out support for IPv6 reverse DNS (IPv6). Our name servers at this time only have IPv4 addresses. Our goal is to have our name servers answering queries over IPv6 by the end of 2010.

Every domain has a TTL (time to live) value. This value defines how long a domain record may be cached. When a domain record is queried the remote server will cache the record for duration of the TTL. We recommend a TTL value of 1 day

If you are planning to make changes to your DNS you may wish to temporarily lower this value in advance of the change. For example if you want to change the IP address associated with your web site you may wish to temporarily lower the TTL value to 5 minutes. That means all users should be directed to the new web site's address within 5 minutes of making the DNS change. The TTL value should be changed a few days before the change.

Division120 does not provide secondary DNS service. Our unique infrastructure does not allow incoming zone transfers which would be required for us to provide secondary DNS service.