Welcome to ZoomTown

 DNS ORDER FORM
  To submit a request for DNS Hosting or in update to exiting Zone information please complete the form below.

PLEASE NOTE: Your DNS changes will be completed with in 2 business days (Tuesday, July 08, 2008) of submission. After the changes are made, it may take up to 72 hours (Wednesday, July 09, 2008) for the changes to be fully propagated on the Internet.

Before FUSE changes can become affective you must set the following name servers as your primary and secondary at your Domain Name Registrar.

DNS Servers IP Address Priority
ns1.fuse.net 216.68.1.100 Primary
ns2.fuse.net 216.68.2.100 Secondary

We recommend that you add hostmaster@fuse.net as your Technical Contact for your domain name. This will make it easier for engineers to help if any problems ever occurs.

Name:  
Billing Telephone Number:     (5135556767) 
E-mail Address:     (name@hostname.com)  
Domain Name:  
Request Type:  

  Name   Type Data
1. IN  
2. IN  
3. IN  
4. IN  
5. IN  
6. IN  
7. IN  
8. IN  
9. IN  
10. IN  


How to use this form.

Please use these form to specify one or more additional resource records you would like to add to your Domain Names DNS data. The explanations and examples included below should help you to understand how to use the form properly.

The first resource field identifies the name of the record. Valid entries in the name field include alphanumeric letters, dashes, and periods. You may not begin the entry with a period nor can you begin or end the entry with a dash (double dashes and double periods are also not allowed.

The second resource field identifies the type of the record (A, CNAME, or MX).

The third resource field identifies the data associated with the record.

  • For address (A) records, the data field must consist of an IP address.
  • For canonical name (CNAME) records, the data field must refer to an existing address record - specify @ if you would like to use the primary address record for the dataremedies.com domain.
  • For mail exchange (MX) records, the data field must refer to an existing address record - specify @ if you would like to use the primary address record for the dataremedies.com domain. The different integer values displayed in conjunction with the MX type define the preference value of the MX record. The preference value ifself isn't important, only its relationship to the values of the other mail exchangers (lower values get preference).

Any Small Office Businessi DSL customer can order DNS as an add-on product for $10/month per domain name. Any Enterprise Business DSL customer will receive DNS free for 1 domain. After that, you can order additional DNS for $10/month per additional domain. No other DSL customers will qualify for DNS.

Examples and Explanations

 Setting up and maintaining your own DNS data may at first seem like a daunting task. However, some careful study of the examples below should help you understand enough about DNS to allow you to comfortably and confidently use the form provided above.

DNS database files are composed of many parts including the SOA (start of authority) record, NS (name server) resource records, A (address) records, CNAME (canonical name) resource records, MX (mail exchange) records, and a few others. Traditionally, these resource records are contained in a “zone file” which collectively define the DNS data for a specific domain name. Each line in the zone file is primarily composed of three parts: the name of the record, the type of the record, and the data that define the record. For example, the following lines represent a small section of an overall zone file: 
fuse.net.            IN A      192.41.5.172
fuse.net.            IN MX     10 mail.fuse.net.
mail.fuse.net.       IN A      192.41.5.172
www.fuse.net.        IN A      192.41.5.172
ftp.fuse.net.        IN CNAME  www.fuse.net.
The previous lines list several address mappings (A records), a single mail preference definition (the MX record), and a canonical name alias (the CNAME record). The DNS Order Form allows you to add, modify, and remove A, CNAME, and MX records for any domain name you host on one of the accounts you administrate. You can use this utility anytime and completely free of charge. More information about the A, CNAME, and MX records are found below.

Address (A) Records

The address record allows you to map a name to an internet address. Every domain name has a primary address record (or at least should have) which associates the domain name with an IP address. Consider the following example: 
fuse.net.            IN A      192.41.5.172
In the example above, the domain name “fuse.net” is mapped to the IP address “192.41.5.172”. Additional address records are shown below: 
fuse.net.            IN A      192.41.5.172
mail.fuse.net.       IN A      192.41.5.172
www.fuse.net.        IN A      192.41.5.172
forum.fuse.net.      IN A      204.202.68.34
You will notice that the first three address records simply point to the same address of the origin domain name (“fuse.net”). However, the last address record, “forum.fuse.net” points to a completely different internet address, in this case the IP address of the Virtual Server. You can create address records which map names to any IP address that you desire.

Canonical Name (CNAME) Records


The canonical name record allows you to specify aliases for existing address records. Consider the following examples: 
www.fuse.net.        IN A      192.41.5.172
ftp.fuse.net.        IN CNAME  www.fuse.net.
imap.fuse.net.       IN CNAME  www.fuse.net.
pop.fuse.net.        IN CNAME  www.fuse.net.
smtp.fuse.net.       IN CNAME  www.fuse.net.
support.fuse.net.    IN CNAME  www.fuse.net.
forum.fuse.net.      IN A      204.202.68.34
intervale.fuse.net.  IN CNAME  forum.fuse.net.
Where address records map a name to an address explicitly, canonical name records indirectly link names to IP addresses by referring to existing address records.

Mail Exchange (MX) Records

MX records specify a “mail exchanger” for a domain name. A mail exchanger is a host that will either process or forward mail for the domain name. MX records, like CNAME records, must refer to an existing address record. However, MX records differ from CNAME records in that they include an extra parameter, a preference value. The preference value is an number in the range of 0-65535 that indicates the mail exchanger's priority. For example: 
fuse.net.            IN MX     10 mail.fuse.net.          
mail.fuse.net.       IN A      192.41.5.172
The MX record specifies “mail.fuse.net” as the mail exchanger for the “fuse.net” domain name at a preference value of 10. The preference value itself isn't important, only its relationship to the values of other mail exchangers, i.e. is it higher or lower in value. Mailers will attempt delivery to the mail exchanger with the lowest preference value first. If delivery to the most preferred mail exchanger fails, mailers then attempt delivery to less preferred mail exchangers (those with higher preference values).

In most cases, the MX record we have set up for you will be all that you need. If you accidentally remove all MX definitions, most mailers will at least attempt to deliver mail to the host IP address.



Copyright (c) 2006 Cincinnati Bell