• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Managing DNS


What is DNS?

The Domain Name System (DNS) is essentially the phonebook for the Internet. It manages the relationships between IP addresses (the phone numbers) and domains (individuals and corporations). All domains and their components, such as web and mail servers, use DNS to resolve IP addresses to the appropriate locations. This article provides step-by-step instructions for managing your DNS records using the Next Generation Control Panel.

 

Create a Domain

To create a domain for your account, follow these steps:

  1. Log into the next generation Control Panel and click DNS at the top of the page.
  2. Click Create Domain. The Create Domain pop-over appears and looks like this:

Create Domain

  1. To create a domain not already listed:
  • Enter the Domain Name you want to add (for example you would use yourcompany.com, not www.yourcompany.com).
  • Enter the Email address for the Domain Administrator (domain contact person) who is responsible for maintaining the domain.
  • Enter the domain Time to Live (TTL). This controls when the record expires. This is also how long you will have to wait for changes to take effect. We recommend that you set TTL to 5 minutes (300 seconds), however you can choose any number you want up to 86400 seconds (24 hours). Then select the time unit.
  1. Click Create Domain.

The domain name will appear on the DNS list page.

 

View the Details of a Domain

To view a domain for your account, follow these steps:

  1. Click the DNS button at the top of the Control Panel page.
  2. A list of the domains for your account is displayed.
  3. Click the Domain Name to view.

The details for the domain are displayed. From this page you can:

 

Modify an Existing Domain

Edit the selected domain by choosing an option from the Actions cog or Actions menu or by clicking the edit pencil next to the option description. You can make the following modifications:

  • Edit Time to Live — Enter the Time to Live (TTL). Note that the domain TTL is displayed as the default value. Select the time unit from the drop-down menu. Then click Save TTL. This controls when the record expires. This is also how long you will have to wait for changes to take effect. We recommend that you set TTL to 5 minutes (300 seconds), however you can choose any number you want up to 86400 seconds (24 hours).
  • Add DNS Record — Enter the information for the record to add.
  • Edit Domain Contact — Enter the Email Address for the Domain Administrator (domain contact person).
  • Delete Domain — Confirm that you want to permanently delete the selected domain by clicking Delete Domain. If you are not sure about the deletion, click Cancel. When a domain is deleted, its immediate resource records are also deleted from the account. If a deleted domain had subdomains, each subdomain becomes a root domain and is not deleted. 

 

Add a DNS Record to a Domain

To add a record to the selected domain, follow these steps:

  1. Select the Record Type using the drop-down menu:
  • A/AAAA — A is an IPv4 Address record. This is the main type of record and should be the first record you add (for example rackspacecloud.com). AAAA is an address record for IPv6. The Target (IP Address) field is automatically used to determine whether the record type is A or AAAA.
  • CNAME — This is a Common Name or Canonical Name Record and is used for subdomains (for example www.rackspacecloud.com). The CNAME record works like an alias. 
  • MX — This is a Mail Exchange record and is used for mail delivery (for example mike@rackspacecloud.com).
  • NS — An NS record can be used to delegate an authoritative DNS server for a domain or subdomain. NS (Name Server) records indicate where the domain's DNS hosting services are located. It effectively delegates a domain to use a set of name servers.
  • SRV — An SRV record is used to designate a host and port for certain services for a domain (such as LDAP).
  • TXT — The TXT record can be used to store several data types, such as SPF or DKIM records.

TXT records are used primarily for SPF and DKIM records. An SPF (Sender Policy Framework) record allows administrators to specify which hosts are allowed to send e-mail from a domain by creating a specific SPF record in the public (DNS). Mail exchangers then use the DNS to check that mail from a given domain is being sent by a host sanctioned by that domain's administrators. DomainKeys Identified Mail (DKIM) is a method for associating a domain name to an email, thereby allowing an organization to take responsibility for a message in a way that can be validated by a recipient.

  1. Specify the information for the record you are adding. The fields change as appropriate based on the Record Type selected.
  2. When you are finished editing the fields for the record, click Add Record.

The new record appears in the Records list.

 

Modify a DNS Record

To modify a record for the selected domain follow these steps:

  1. Click the Actions cog to the left of the Name of the record you want to modify in the Records list.
  2. Choose the desired action from the drop-down menu:
  • Delete Record — Click Delete Record to permanently delete this record.
  • Modify Record — Modify the information as desired and then click Modify Record.

 



© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER

18 Comments

Is it possible to set the reverse DNS for the new cloud servers?

Not yet, I'm afraid. Support for reverse DNS configuration is in the works but is not yet available for the next gen Cloud Servers.

Our server need to send out email notifications at the completion of a transaction so we desperately need rDNS. What is the ETA or can you create this on your own server as you are ISP?

I can't provide you with an ETA, but it is possible to use our Cloud DNS API to manage reverse DNS for a next-gen server. More information here:

http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/ReverseDNS-123456999.html

Otherwise, you can still create first-generation servers through the original control panel, accessible via the menu in the upper-right of the CP. In the server details for a first-gen server there you can set up reverse DNS.

Hi, where do I need to set up my dns records if I'm using ISPConfig? Do I need to add anything in my Rackspace control panel, or will ISPConfig handle all my dns? Sorry to ask, but it takes so long to propogate changes I can't tell if what I'm doing is correct.
Also, do all the domains hosted on my virtual server need to have the same ns records, i.e.dns1.stabletransit.com and dns2.stabletransit.com

ISPConfig can include its own DNS/BIND server, I believe, which means you would be able to manage your DNS through ISPConfig only if you point your domains' NS records to the server running ISPConfig.

The NS record is used by the rest of the Internet to find out where to go to get authoritative information on your domain's DNS. If you manage your domain through our control panel then you'd want to use the Rackspace dns servers in their NS records (dns1.stabletransit.com, etc.). If you manage a domain elsewhere, or on your own server, then you would want to us appropriate addresses for those NS records.

You can use domains that have different NS records as virtual hosts on the same web server with no problem. So long as the domains are configured properly (so other machines can look up their addresses), the web server will be fine working with any of them.

I've set up a cluster of BIND servers within our RS dedicated environment to allow for a robust split-zone domain, but default nextgen cloud networking makes keeping our resolv.conf difficult. Is there any support for split-zone in the RS DNS service?

Hi, At the Cloud DNS API, how do I get my device-resource-uri ?
It needs to add reverse dns but I couldn't found it.

You can get the device URI through the API service of the product for which you're trying to control DNS. If you want to set reverse DNS for a Cloud Server, see this page for details on getting a listing. THe device URL will be in the "links" section of the response, I believe.

http://docs.rackspace.com/servers/api/v2/cs-devguide/content/List_Servers-d1e2078.html

Further details can be found in the API documentation for Cloud DNS and reverse DNS:

http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/ReverseDNS-123456999.html

Any word on when reverse DNS will be supported? Your Next Gen servers are useless to me without it.

No word yet, I'm afraid. It is being worked on but I can't provide a timetable. We do recognize that the lack of reverse DNS support is a major blocker for many customers.

Reverse dns is desperately needed!

It is still in the works, at least for the control panel for next-gen servers. It is possible to use the API to set up reverse DNS for a next-gen server, but it's not as easy a process. There's a forum post here that describes using a script that automates it somewhat:

https://community.rackspace.com/products/f/25/t/48.aspx

I also think that applicability of the new generation servers is severely limited without reverse DNS support. Actually I assumed that this was just working, and after setting up a server discovering that it is not...

Thanks Maarten. You can set up reverse DNS through the API for now, and one of our support techs put together a handy script to help with the process until PTR records are added to the next-gen control panel. It's described in the forum post linked in a previous comment, but a direct link to the script's github page is here:

https://github.com/cloudnull/ptrcreate

You can now manage reverse DNS for all Cloud Servers instances through the new control panel. You can find the control on the Server Details screen.

Wouldn't it be nice if we could upload a zone file and be done with it? Transferring my dns is going to be a right pain.

The functionality isn't in the control panel yet, but you can import a zone file into our DNS through our DNS API:

http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/import_domain.html

If you can't use the API for the import, open a support ticket or give Support a call and they can assist you with the import.

Add new comment