When authenticating, do I use the same API user & key that I use when connect to other Cloud APIs?
What account number do I use to access the service?
What is the difference between US and UK Cloud DNS?
What DNS management operations does the Cloud DNS API support?
What record types does Cloud DNS support?
Can I import and export domains?
What are the Rackspace DNS servers?
What type of DNS network does Rackspace use?
What are the limitations of the search functionality?
Do my TTL settings expire?
The Domain Name System (DNS) is a system by which internet domain name-to-address and address-to-name resolutions are determined. All domains and their components, such as mail servers, utilize DNS to resolve to the appropriate locations. For example, DNS is used to turn 'www.rackspace.com' into the computer addressable IP address '184.108.40.206'.
DNS servers are usually set up in a master-slave relationship such that failure of the master invokes the slave. DNS servers may also be clustered or replicated such that changes made to one DNS server are automatically propagated to other active servers.
Anyone who has a Rackspace Cloud account can access the Cloud DNS service. Existing Cloud customers will have access to the Rackspace Cloud DNS by default.
Cloud DNS is free and intended for use with Cloud accounts that have provisioned and active resources.
No. The Cloud DNS service is only available for Cloud account resources. Managed / Dedicated customers with Rack Connect (i.e. those customers who also have a Cloud account) have access, but can only use the service to manage DNS for their Rackspace Cloud resources.
Absolutely; in addition to managing DNS in the Cloud Sites Control Panel, you can view, edit and delete Cloud Sites domains can be viewed, edited and deleted via Cloud DNS API. Domain registration is not supported by the Cloud DNS API, but you can still register domains through the existing Cloud Sites Control Panel.
How does this work for Hybrid customers?
A Hybrid customer will be able to continue to utilize MyRackspace.com to manage domains for their dedicated resources, and will be able to utilize Cloud DNS to manage domains for their Cloud resources.
**Duplicate domains may not exist between Managed Hosting and Cloud Hosting resources.**
The process for authenticating with the Cloud DNS API is the same when authenticating with all other Rackspace Cloud APIs.
To authenticate, you must supply your username and API access key in x-headers.
For full authentication details, see the Cloud DNS Developers Guide.
Customers should use their existing Cloud account number.
The functionality is the same. The only difference is US and UK each have their own separate API endpoint:
Customers can create, modify, remove and list domains, subdomains and records.
Additionally, users can search domains by filtering. We do not support filtering records.
For a full list of supported API operations, see the Cloud DNS Developers Guide.
The Cloud DNS API currently supports the following record types:
The service supports DKIM and SPF records through formatting TXT records with custom attributes indicating the record type. We do not currently support the SPF RR type as defined in RFC 4408.
Yes, via API. You can import a domain from external providers using a valid bind9-formatted zone file. Similarly, you can export their domain to a bind9-formatted file. Currently, you will not be able to export zone files from MyRackspace to Cloud DNS and should contact Support to request a domain transfer from dedicated resources to Cloud resources.
Our default DNS servers are:
Rackspace leverages a globally distributed anycast network. Currently we have DNS servers located in Texas, Virginia, Chicago, Hong Kong, and London. Using anycast, we broadcast the IP addresses for ns.rackspace.com and ns2.rackspace.com from each location. All DNS queries will generally go to the geographically closest nameservers, giving you faster results no matter where your queries originate. Additionally, all of our DNS servers are monitored 24/7 and if an entire datacenter were to fail, or even if all of the DNS servers within a specific datacenter were to fail, the DNS queries will automatically start going to the next best location.
You will be able to search for domains within your own account. The functionality does not allow you to search for records.
When a domain and/or record is created, and no TTL (Time To Live) is specified, a default value of 3600 seconds is used. When the domain and/or record TTL is supplied by the user via a create or update operation, the specified TTL values must be 300 seconds or more.
Typical DNS propagation to Rackspace nameservers (globally) may take up to one minute. This refers to the amount of time it takes after a change (add/delete/update) is made to a customer's records via API, DNS Manager, MyRackspace Customer Portal, Cloud Control, etc. before the change is live on our nameservers. Large amount of changes made simultaneously may take 2-3 minutes.
If a new domain is added or an existing domain is deleted, this may take up to a few minutes to propagate to our Rackspace nameservers.
When changing nameservers for a domain, complete propagation will take about 2 days for most domains. This is enforced by the registries.
All accounts, by default, have a preconfigured set of thresholds (or limits) to manage capacity and prevent abuse of the system. The system recognizes two kinds of limits: rate limits and absolute limits. Rate limits are thresholds that are reset after a certain amount of time passes. Absolute limits are fixed. See the developers guide for more information on rate limits.
Contact Support via phone, chat, or ticket. All requests will require reasonable justification and must be approved before limits can be adjusted.
You may submit Cloud DNS tickets via existing DNS ticket options available in the Control Panel.
© 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