How to Add or Modify DNS Records in Manage

Pre-Flight Check

To manage a domain’s DNS records in your account management interface, it must use one of our nameservers, which are:

  • ns.liquidweb.com and ns1.liquidweb.com
  • ns.sourcedns.com and ns1.sourcedns.com

If you already know that your site is using Liquid Web’s nameservers, skip ahead to Step #2: Adding or Editing a DNS Entry.

Step #1: Where is DNS hosted?

There are several methods to determine which nameservers are considered authoritative for your domain. You can either:

  • Use a web-based WHOIS lookup tool such as ICANN WHOIS and noting the listings under Name Servers
  • Query WHOIS from a terminal by running the command “whois yourdomainname.com” and noting the listings under Name Servers
  • Log into your Manage interface, select Domains from the left menu and click on the DNS tab. Scroll down to the CURRENT DNS ZONES section and look at the Delegation column. If you see a green button labeled “Delegated”, your domain is using our nameservers and you can click the [+] the the left of the domain name to expand its record and start managing entries immediately.

    CurrentDNSZones

If your domain is not using our nameservers but you do want to be able manage DNS records through your Liquid Web account interface, you will need to log into your account at the registrar and update the nameservers to one of the pairs noted at the top of this article.

Note: It is not necessary to transfer a domain name simply to specify different nameservers or move its authoritative DNS record. You can continue to use your preferred registrar for domain name renewal and management even if you update the domain to use our nameservers.

 

Step #2: Adding or Editing a DNS Entry

  1. From your Manage interface, click on Domains in the left menu and then select the DNS tab in the Domains Dashboard and click the [+] to the left of the domain name to expand its DNS record.

    Add a DNS record in Manage

  2. To add a new record, click the blue Add New Record button at the bottom. To edit an existing record, click the Edit button to the right of the entry you wish to change. Each entry has four fields:

    Add new DNS record

    • Name: This field allows you to append a prefix (or more accurately, a suffix, since domain names are resolved from right to left) to the main domain name. If you’re adding a record for a subdomain, such as shop.example.com, you would enter “shop” in this field. Note: The Name field is also called “Host” or “@” at some registrars and hosting companies.
    • TTL: This specifies, in seconds, how long the DNS entry should be cached by a resolver before it’s considered outdated and checked again. A higher setting will reduce load on the DNS server, but will extend the time it takes for the new entry or value to propagate. Generally, you will want to set a lower value prior to changing a record (300 or 3600 for 5 minutes or one hour, respectively), and then raise the TTL back after 24 to 48 hours once your change has had a chance to fully propagate.
    • Type, and Data: Manage allows you to enter and edit multiple record types. Remember that only A, AAAA, and NS records take an IP address in the Data field.
      • A and AAAA records resolve a domain to an IP address (IPv4 for A, IPv6 for AAAA). Without these records, a site will not resolve. In addition to the main domain name, you likely will want to add an A record for your hostname, as well as any subdomains which resolve to a different server.
      • CNAMEs are aliases pointing an entry back to the main domain. Once a browser requests a page from that subdomain from your web server, the server will route the request to the proper directory. If you find yourself frequently creating records for subdomains, you may wish to add a wildcard CNAME to cover any requests for subdomains without their own records. You can do so by entering an asterisk in the Name field.
      • MX records determine how mail is handled for the domain. When selecting an MX record type, Data will contain two fields: Priority and Exchange.
        • Priority always will be a number. Mail will be routed to the lowest numbered (highest priority) MX entry. Use the settings recommended by your control panel or email provider.
        • Exchange is the server to which mail will be directed.
      • NS Nameserver records specify the nameservers for the domain. Remember that the authoritative nameservers are specified at the registrar — if a WHOIS search returns different nameservers than what you’ve entered here, your entries in Manage will have no effect.
        Note: When using your own private or custom nameservers, their nameserver entries must be added at the domain’s registrar. When using custom nameservers, you will not be able to use Manage to add or edit DNS entries; that will be done via your server’s control panel.
      • SRV, or Service, records are used to configure services for your domain. When configuring an SRV record in Manage, the Name field should begin with an underscore, then the name of the service, a period, an underscore, and finally the protocol. For instance, a SRV record for Office 365’s Session Initiation Protocol over TLS would contain “_sip._tls” in the Name field. An SRV record contains four Data fields, each of which should be filled out according to the service’s instructions:
        • Priority: As with MX records, the lower the number the higher the priority.
        • Weight: Is used to distribute requests based on capacity.
        • Port: Directs requests to a specific port.
        • Target: Specifies the destination. For the example Office 365 SRV record above, the target would be “sipdir.online.lync.com”.
      • TXT records contain, as the name suggests, text. They can be used for SPF and rDNS entries, as well as domain verification information.
  3. Once you click the green checkmark button, the record will be added and DNS will begin to propagate. Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally.

 

How To Add a DNS Record For Your Hostname in Manage

Pre-Flight Check

  • These instructions are intended for domain names using Liquid Web’s nameservers.
  • If the main domain uses other nameservers, such as at a registrar, you will need to log in there and add an “A” record for the hostname in the main domain’s DNS zone file. The record should point to the server’s primary IP address.

Whenever you create a new server (or change the name of an existing one) you will need to add (or update) the DNS record for its parent domain.

If the hostname does not resolve, you will not be able to:

  • access WHM, cPanel, or Webmail via the hostname
  • send or receive email over a secure (SSL) connection using a mail client
  • verify the authenticity of email sent by the server (which could result in mail being rejected or flagged as junk by the recipient’s server)

Fortunately, adding the record is a simple process, and you can add the record in your Manage dashboard.

  1. Once logged into your Manage interface at https://manage.liquidweb.com/manage, click on Domains in the left menu and then select the DNS tab in the Domains Dashboard.

    DNS zones

  2. Now, click the [+] next to the main domain name to expand the domain’s DNS record and click the Add New Record button at the bottom. For the host.examplesite.com server, we’ll be editing the DNS record for the main domain, examplesite.com.

    Add a DNS record in Manage

  3. Your hostname will need an “A” record pointing to the IP address of the server itself. In this case, because the server has only one IP address, it is the same as the IP address of the site.

    Add new DNS record

  4. Once you click the green checkmark button, the record will be added and DNS will begin to propagate. Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally.

 

Most Common Support Requests

As you might expect, most support requests on managed cPanel servers fall into a few basic categories. What you might be surprised to discover is that many common problems can be resolved by following a few simple steps.

None of the common cPanel support requests listed here are server-critical issues that require an experienced system administrator to troubleshoot and resolve, and we recognize that many of our customers are curious about their servers and actively engaged in learning more about cPanel server administration.

To that end, we’ve gathered together some of our Most Common Support Requests, and we’re sharing them with you here — along with their solutions.

Should you find yourself experiencing one of these common issues, you’ll know exactly what to expect when contacting our Heroic Support® team. And while you certainly are welcome to try to resolve the issue yourself, remember that we are here to assist you 24 hours a day, seven days a week, 365 days a year.

These articles should hold the answers to a number of common questions and, if you are so inclined, provide you with the tools and resources to resolve some non-critical issues on your own. And should you ever find yourself in need of assistance with any issue, please do not hesitate to contact Heroic Support®.

How to Create and Add a New Domain in Plesk

Step #1: Add New Domain

To create a new domain in Plesk 11+ you will click on the Add New Domain button on the Websites & Domains tab (if you use Service Provider view you will need to choose “Manage Hosting” next to the subscription or domain). This will bring you to the Adding New Domain Name page. Here you will be required to determine three things which will be covered in detail below: DNS Settings, Hosting Type, and Hosting Settings.

How to Create and Add a New Domain in Plesk

Continue reading “How to Create and Add a New Domain in Plesk”

What are the Liquid Web Name Servers (NS)?

So let’s say your server is online, it has been secured with ServerSecure™ or ServerSecurePLUS™, and you’ve uploaded new site content. What is the next step? DNS and name servers! Name servers provide directory information that connect your domain name to your server’s IP address.

The Liquid Web Name Servers (NS) are:

ns.liquidweb.com
ns1.liquidweb.com

We also offer tips on Using Liquid Web’s Name Servers (DNS), deciding on where to host your DNS, and Diagnosing Common DNS Errors!

Continue reading “What are the Liquid Web Name Servers (NS)?”

Automating DNS With Zone Delegation and the Storm API

Although the term DNS zone delegation may seem new to you, you have been using zone delegation without even realizing it. When you tell your domain’s registrar what nameservers you are using for a particular domain, you are delegating the zone for that domain.

Single zone delegation will work for most people. In fact, most use a single zone file to reference multiple hosts, or multiple subdomains residing on a single host. However, there are cases where where it may be beneficial to perform additional delegation.

Continue reading “Automating DNS With Zone Delegation and the Storm API”