You can use the account management control panel to add, manage and delete custom DNS entries. For example, you could add a new record that points "home.example.com" at your home computer, or you could override the standard MX records we provide.
DNS is a complicated subject. Although our control panel makes it easy to make changes, you should be familiar with how DNS works to know whether a change is appropriate. Altering DNS entries can cause problems with Web or e-mail services we provide for you. If you have any questions, please contact us before making any changes; we'll be happy to help and give advice.
On this page:
To edit and view your DNS settings:
You'll be able to easily add and alter the DNS records for your Web site.
Although we provide a convenient, understandable interface for making DNS changes, the way that DNS servers really work behind the scenes is to read the DNS entries in a special format from a "DNS zone file". Because some advanced DNS users are familiar with the format of the zone file, we display a copy of the file for experts to examine. What you see is the same zone file that our DNS servers actually use.
If you aren't familiar with the zone file, you should simply ignore the "DNS zone file" section of the control panel.
To replace a standard DNS entry, simply add your own entry of the same "label" and type.
For example, if you want to use your own MX entry instead of ours, just add an MX entry for your domain name. Our default MX entries will no longer appear.
We're often asked this question when customers add an A record that points to the IP address of their home DSL or cable modem connection. However, the company that owns an IP address (not the company that runs the domain name) is the company that provides reverse DNS entries.
For example, if you add "office.example.com" as a DNS entry pointing to your business Comcast cable IP address at 192.0.2.34, only Comcast can set up reverse DNS entries that would map 192.0.2.34 back to "office.example.com" — we can't do that.
For reverse DNS entries, you should contact the company that issued you the IP address (probably your ISP — the company that provides your modem connection).
We don't provide secondary MX service or MX forwarding. If you're setting up your own mail servers to receive incoming mail, you should list only those servers in the MX records. You should not include our MX servers in addition to your own. (When you add a new DNS MX entry, our standard MX servers will automatically be overridden for your domain name.)
The reason we don't offer backup MX service is that it causes far more problems than it solves on today's Internet. If we provided backup MX service for your server, we'd have no way of knowing what usernames are valid on the primary server, so our servers would have to accept mail for any username at your domain name. A huge percentage of that mail would be spam (spammers intentionally try delivering to secondary MX servers because they tend to have more permissive spam filters). Delivering that amount of spam to you or bouncing it (probably to forged sender addresses, called "backscatter") would both lead to major problems.
There should be no need for third-party backup MX servers at all with modern networks. Even if your primary mail server is down for some time, sending servers are required by Internet standards to queue mail and keep retrying all deliveries for at least four days, so you should never lose any mail.
You can add custom MX records as described above if you are running your own mail server such as Microsoft Exchange.
If you're using a Microsoft Exchange server and you're concerned about reliability, you may want to consider using the "Exchange Connector for POP3 Mailboxes", as described in the "LAN with Multiple POP3 Accounts" section of this page. This allows you to use Exchange even if your mail server is unavailable for more than four days or you have a dynamic IP address.
The TXT record we include by default is an SPF record. When you send mail to other ISPs that use the SPF anti-spam system, the receiving server uses the TXT record to verify that our servers are legitimate senders of mail for your domain name. This makes the messages less likely to be incorrectly rejected by spam systems.
The default TXT record will not be included in your DNS entries if you add any custom MX or TXT records for your domain name.
"Dynamic DNS" services allow you "point" custom DNS hostnames at your home computer, even if your home IP address changes frequently. By using a free dynamic DNS service and adding a custom DNS entry for example.com, you can easily point hostnames like "home.example.com" at a dynamic IP address, such as your home DSL or cable modem connection.
To do this, first sign up with a free dynamic DNS service such as DynDNS, No-IP.com, ZoneEdit, or afraid.org. These sites will let you choose a dynamic hostname such as "example.dyndns.org".
Once you have that hostname, use your example.com control panel to add a "CNAME" DNS entry for "home.example.com" that has the dynamic DNS hostname as the "CNAME target". After doing this, you'll be able to connect to your IP address using "home.example.com" as well as "example.dyndns.org": the two hostnames will be interchangeable for most purposes.
Although we've used "home.example.com" as an example here, you can use any hostname that doesn't interfere with another service we offer. For example, you could add a CNAME record for "office.example.com" or "private.example.com". The only thing to keep in mind is to make the CNAME target be the dynamic hostname that the other company provided to you.
DNS is a complex subject that literally has entire books written about it; explaining how it works is more than we can do here, unfortunately. A useful introduction is the Wikipedia article on DNS, and a search for "DNS tutorial" in your favorite search engine will provide plenty of links.