How to: Edit DNS records (A, AAAA, CNAME, MX, TXT, SRV)

This article will show you how to Add and Edit DNS records in your Hover account. The DNS zone file in your Hover account only applies to your domain if it's pointed at the Hover name servers ns1.hover.com and ns2.hover.com.

If you need to change your name servers, please see: How To: Change your nameservers (DNS Servers)

By the same token, if you're using another company's name servers, such as your website hosting company, you'll need to add and edit the DNS records through your hosting company account where that DNS zone file is managed.

You should not change your DNS records unless directed by your hosting company, or if you are familiar with configuring zone files.  If you are unsure whether or not you need to edit your DNS records, don't hesitate to contact a customer adviser for assistance at help@hover.com or by phone at 1-866-731-6556.

 

To manage DNS records, follow the steps below:

  1. Log into your Hover account at: https://hover.com/signin
  2. If you have more than one domain name listed in your account, choose Domains from the Your Account menu.

    save image

  3. Select the domain from your list, or choose Edit DNS from the Edit menu.

    save image

  4. On the DNS page, you can manage DNS records for the selected domain name.

    save image

 

The next steps depend on the record type that you want to edit or create.  Details for each type can be found below.

Note: Hostname refers to the prefix before the domain name.  To create a Blank record, use an @ in the Hostname field. This represents an empty prefix (so the name exactly matches the domain name; for example divapirate.com). The @ hostname is also referred to as the the root of the domain. An * (asterisk) in the Hostname is a wildcard, and represents any prefix.  For example, creating a record for *.divapirate.com will point <any prefix>.divapirate.com at the IP address provided.

 

A (IPv4) and AAAA (IPv6) Records

An A Record, or AAAA Record, is used to point a hostname at an IP address. This record type can be used to point your domain name at your web host or for creating subdomains which point directly to an IP address.

To create a new A or AAAA Record, follow these steps:

  • Click on Add A Record.

    save image

  • Select the Record Type A.  Enter your hostname, and then type the appropriate IP address in the IP Address text box. You can leave TTL at the default setting. 

    Click Add Record.

    save image

    OR
  • Select the Record Type AAAA. Enter your hostname, and then type the appropriate IP IPv6 address in the IP Address text box.

    Click Add Record.

    save image

 

CNAME Records

A CNAME record, or Canonical Name record, is a pointer of one name to another.  A CNAME record points a hostname to another name that is already created for a server or system.  Canonical means expected or real name.  These records are pointing a name you created at the "real" name for the server or system.

This is useful when running multiple services (such as an FTP and a webserver) from a single IP address. Each service can then have its own entry in DNS (such as blog.mydomain.com or ftp.mydomain.com).

You may also be requested to enter a CNAME record to verify domain ownership for online services such as Google Apps

CNAMEs should only be used if you can't use an A Record.

Note on CNAMES: A blank (@) CNAME record will cause other blank records to fail, such as MX records, or blank A records. This can have a negative impact on the resolution of your website or sending/receiving of email.

To add a new CNAME record, follow these steps:

  • Click on Add A Record.

    save image

  • Select the Record Type CNAME from the drop down menu.  Enter your hostname (which creates the subdomain), and then type the appropriate target hostname in the Target Host text box. You can leave the TTL at the default setting.

    Click Add Record.

    save image

 

MX Records

A MX record or Mail Exchange record specifies how e-mail should be routed.  The MX record points to the servers that should receive e-mail for the domain.

In simple terms, the MX record allows the rest of the world to know where your email needs to be delivered.  The default setting points your domain to Hover's mail system.

Each MX record contains a host name and a numeric priority.  The lower numbers have higher priority.  Priority 0 is highest priority.  Setting priority is useful if the e-mail service uses secondary servers.  Secondary servers are usually given lower priority because they may be operated externally, not have direct access to the primary e-mail storage, have less Internet bandwidth, among other reasons.

To create an MX record for your domain enter @ as the hostname.  If you are creating an MX record for a sub domain, then you can enter your sub domain into the Hostname field.

To add a new MX record, follow these steps:

  • Click on Add A Record.

    save image

  • Enter @ as the Hostname (unless otherwise instructed by your email provider), select MX from the Record Type drop-down list, enter a priority, and then type in the Hostname of your email service (your email provider will be able to tell you what hostname should be used).

    Click on Add Record.

    save image

 

TXT Records

TXT records allow users to associate some text with a hostname.   Originally TXT records were created to add arbitrary human-readable text to DNS records. Today TXT records have a number of practical uses, one of which is to define Sender Policy Framework (SPF) information which can be used by multiple e-mail technologies to assist in identifying the actual sender of an email.

 

To add a new TXT record, follow these steps:

  • Click on Add A Record.

    save image

  • Select the Record Type TXT from the drop-down list, enter your Hostname, and then type in the value of your TXT record. In this example, there is an example SPF Record for Google.

    Click on Add Record.

    save image

 

SRV Records

An SRV record is a service record which specifies information on available services.    Services such as Google Apps may require you to create SRV records.  

SRV records have the following form:  _Service._Protocol.DomainName TTL Class SRV Priority Weight Port Target

The Class is always set to IN and the TTL is set automatically by our DNS server.

To add a new SRV record, follow these steps:

  • Click on Add A Record.

    save image

  • The example below will create an SRV record with the following values:

    Hostname:  _xmpp-server._tcp (xmpp-server service over the tcp protocol)
    Record Type:  SRV
    Priority:  5
    Weight:  10
    Port:  5269
    Destination Hostname (Target):  xmpp-server.l.google.com

    You can leave the TTL set to the Default settings.

    Click on Add Record.

    save image

 

Edit and Delete Existing DNS Records

To edit an existing record, follow these steps:

  • Click on the Edit option to the right of the DNS record you wish to edit.

    save image

  • Enter the new information, then click Save Changes.
    save image

 

To Delete an existing record, follow these steps:

  • Click on the Green X to the far right of the DNS record you wish to delete. 

    save image

  • You will be giving the chance to confirm this action, or cancel it. If you do wish to delete this DNS record, click Delete.

    save image

 

Bulk DNS Management

DNS records can be edited in bulk for multiple domain names instead of editing records for each individual domain name.  To edit DNS records in bulk, follow these steps:

  • Use the check boxes to select multiple DNS records. Then, using the Bulk Edit menu above, choose from the available bulk edit option for your selection.

    save image
  • You can sort the DNS records by clicking on the headings Type, Host, Value, and TTL.

    save image

 

 
Have more questions? Submit a request

97 Comments

  • 0
    Avatar
    Andrew Costen

    Thanks for the suggestion Nathan. It will definitely be taken into consideration.

  • 0
    Avatar
    Richard Bettridge

    Please support round robin dns. I would like to add two ips of my two hosted VMs for fail over purposes. Shouldn't be that hard to simply offer the two IPs in DNS, it's pretty straight forward.

  • 0
    Avatar
    Yakira Dixon

    Hello Sean Liu - Please make sure your A record is pointing to this IP address: 66.6.44.4.

    Depending on the number of levels in your domain, you may need to use a CNAME record instead of an A record.

    Please consult this Tumblr document for more information: http://www.tumblr.com/docs/en/custom_domains

  • 0
    Avatar
    Victoria Walker

    Hi, 

    how long does it take for changes to the MX to take effect? I have put in host record "@", priority "0" and hostname "mail.affordable.ch" (details provided by my host) but i still get a postmaster failure when I try to send myself an email (the host has confirmed that the A record is successfully pointing at their servers). 

  • 0
    Avatar
    Dave Kuhar

    Seriously, who doesn't love a good Terry Gilliam reference in their tech support documents? It's fun to charter an accountant, and sail the wide accountancy!

  • 0
    Avatar
    Neil Faiman

    Can you explain the relationship between forwarding (as described in your "How to forward your domain name" article) and the use of CNAME records? They seem to accomplish the same thing.

    Supposing that I have a domain, "myfinedomain.org" registered at Hover, and I have a web site for that domain hosted at Amazon S3, what would be the best way to get myfinedomain.com and www.myfinedomain.com pointing at my S3 bucket? Create top-level and www. CNAME records? Use forwarding? Or follow Amazon's suggestion, to point the top-level domain at the S3 bucket, create a second S3 bucket to represent the www. domain, define that bucket to forward to the real bucket within S3, and create a CNAME record for the www. subdomain pointing at the www. bucket?

  • 0
    Avatar
    Victoria Walker

    Edit to my comment - should read hostname "mail.affordablegeneva.ch"

  • 0
    Avatar
    Robert Rockefeller

    What is the MX record address for Hover's email servers?

  • 0
    Avatar
    Simon Littlehales

    It would be great if Hover added a "Comment" field to each entry where you as a user could add an optional comment / reminder describing each entry that you make. That would help in the future when you've totally forgotten why specific entries were made!

  • 0
    Avatar
    Brian Cabral

    Hi Neil,

    There is no relationship between URL forwarding and CNAME records, unless of course you are forwarding your domain to a subdomain that is set up with a CNAME record.

    URL forwarding allows the forwarding of your domain to a URL, for example  domain.com can be forwarded to the URL:  http://example.com/page

    In order for URL forwarding in Hover to work, your blank domain must be pointing to our forwarding IP address: 64.99.80.30

    A CNAME is a DNS record. This is used to create a subdomain, such as " www.example.com" which points to a hostname.  This hostname may be pointing to a server that uses a pool of rotating IP addresses. Many hosting companies use CNAME records because it allows all their customers to point to the hostname instead of and IP address, which would result in the customer to have to make any changes to their DNS everytime their hosting company's IP address changes.

    And eample of this would be Google Apps.  You can create a subdomain for "mail" as a CNAME record that points " mail.example.com" to the hostname " ghs.googlehosted.com".

    How you point your domain to your Amazon hosting depends soley on what Amazon's requirements are.  If you have any email from them with instructions of what they require, and are unsure how to proceed, please feel free to send us an email to  help@hover.com or give us a call at 1-866-731-6556 (Mon-Fri between 8am and 8pm EST) and we can help you out with that.

  • 0
    Avatar
    Brian Cabral

    Hi Shawn,

    mail.hover.com is used as a standard because it's protected by an SSL certificate. However, you can use mail.<yourdomainname> as the mail server as long as there's a corresponding DNS record for the domain but there wouldn't be an SSL certificate associated. I've sent you an email for some assistance so you can reply to my email if there's anything I can help you with.

  • 0
    Avatar
    Andrew Costen

    For Joseph (and anyone else who may be wondering), the issue with SRV records not being able to be over 4 digits long should now be resolved.

  • 0
    Avatar
    Lora Dillenkoffer

    I keep getting this "Verification failed. Your verification DNS TXT record was not found. You might need to wait a few minutes before Google sees your changes to the TXT record"

     

    Can anyone help me?

  • 0
    Avatar
    Tyson Acker

    Hi Jon - I've sent a reply to your support ticket with additional information and a workaround solution for you.

  • 0
    Avatar
    Ken Anderson

    I would like to associate one of my domains with a website located on Github. The Github instructions for doing this are located here:

    https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/

    To follow those instructions on Hover, do I just add two new A records using the @ symbol for the hostname and filling in the two IP addresses listed on the GitHub page?

    I assume that i would then delete the other A record that has a hostname of * (asterisk)?

    I've never done this before so I don't want to mess anything up! Thanks.

  • 0
    Avatar
    Andrew Costen

    Hover's MX record address is: mx.hover.com.cust.hostedemail.com

  • 0
    Avatar
    Jon Zafra

    Hello,   I just want to update my current DNSs from** ns5.ev1servers.net  *into * srv1.kukers.com. *and it stays  the same problem as Zoe Robson. It says "Domain not in registry (Code 480)".  The problem is I dont want to transfer the DNS into an own server in my domain, so I suppose is not a glue server.     I dont see the current * ns5.ev1servers.net   **server in the list....  Im trying to create new DNS as CNAME, as A... and impossible.

     

    Thank you

  • 0
    Avatar
    Ken Anderson

    How long should I wait before the new A records become available? I made the changes ~2-3 days ago and it does not appear to have propagated. When I run the dig command that GitHub recommends, I get the following response:

     

    dig cuacm.org +nostats +nocomments +nocmd

    ; <<>> DiG 9.8.3-P1 <<>> cuacm.org +nostats +nocomments +nocmd

    ;; global options: +cmd

    ;cuacm.org. IN A

     

    GitHub indicates that I should see something similar to the below example:

    dig example.com +nostats +nocomments +nocmd
    ;example.com
    example.com. 73 IN A 192.30.252.153
    example.com. 73 IN A 192.30.252.154

     

    Did I make the changes to my A records correctly for cuacm.org?

  • 0
    Avatar
    Manfred SCHRIEFL

    Hi. I am having problem of point my domain to the website that hosted in godaddy.

    This is my problem. I have domain name in Hover.com and also using the email from hover.com. However, i have subscribed the hosting for my website in godaddy (wordpress hosting) and i am trying to edit the dns so that my domain is point to the website.

    I have edit the CNAME in the EDIT DNS option but seems like it is still not working. 

    Please guide me on this.

     

     

     

     

     

     

  • 0
    Avatar
    Robert Rockefeller

    My DNS control panel won't take an MX record of the form mx.hover.com.cust.hostedemail.com. It wants an IP address.

    Am I doing something wrong? Or what is the IP address from Hover's mail server?

  • 0
    Avatar
    Allan Van Ness

    i've been having the same issue.  

  • 0
    Avatar
    Blair M

    Hi Ken, 

    Thanks for the message about this.  Based on those instructions, you can use the two A records.  You would want to delete the two A records that are set as default (64.99.80.83) and then add two new A records (@) that point to each of the IP addresses provided by GitHub: 

    • 192.30.252.153
    • 192.30.252.154
  • 0
    Avatar
    Tyson Acker

    Hi Allan - this issue has a few possible root causes.  Can you send us a support ticket or call in so we can help you get this fixed please?

  • 0
    Avatar
    Brian Cabral

    Hi Ken,

    I noticed the name servers associated with your domain were not set to ns1.hover.com and ns2.hover.com. I went ahead and updated them for you so the website will begin resolving properly once the changes propagate.

  • 0
    Avatar
    David Lawrence

    Are there plans to add support for any other record types?  I just wanted to add two NS records for a subdelegation within one of my zones, but the question is somewhat broader since there are only a few limited records that can be used.

  • 0
    Avatar
    Brian Rossman

    You seem to be missing CAA records still

  • 0
    Avatar
    Ken Anderson

    Hi Brian,

    Thanks so much! I knew I was doing something wrong. I'll check things out tomorrow to see if the changes have propagated.

    Happy Thanksgiving!

    Ken

  • 0
    Avatar
    Tim Goldsmith

    I'm not the sharpest tool in the box, and I'm really struggling. I've added an A Record, but when I go to my website, it comes up with nothing. I'm not sure if there is some major thing I missed when I transferred from godaddy to you, or if I am just missing something...

  • 0
    Avatar
    Konstantin Rubinov

    Useful and clear explanation about difference between ARecord and CNAME http://www.youtube.com/watch?v=WqhgGpv4cKY

  • 0
    Avatar
    Josh Weatherly

    I don't understand how you can claim to have "Advanced DNS Management" while still lacking an ability to import zone files. Even the ability to import only records of a certain type would be helpful..

    I want to transfer more domains to your service but am hesitant to do because the amount of work it will take to enter each record manually through your UI.

    I don't need to Bulk edit records that already exist, I need to bulk insert many records(10-15), and then do this many times for all my domains. If I'm missing something and this is already available, I apologize.

    Thanks
    -Josh

Please sign in to leave a comment.
Powered by Zendesk