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

DNS - Creating a DNS Record for Cloud Servers


NOTE: This article is written for our First-Generation Cloud Control Panel. A version of this article is also available for our Next-Generation Cloud Control Panel.

Creating DNS records for your domain is easy to do within the Cloud Server Control Panel. In this article, we will look at creating a DNS zone for your domain and adding basic A, MX, and CNAME records using the Cloud Server Control Panel.

Contents

//

Log In

The first thing we have to do is log into the Cloud Server Control Panel which can be found at https://manage.rackspacecloud.com.

DNS Panel

When you log in, navigate to your Cloud Server overview page, by selecting Hosting > Cloud Servers.

Cloud Control Panel Menu

This opens an overview page of your Cloud Servers. Click on the link for your Cloud Server. Next, click on the DNS tab at the top. This is where you will modify your DNS records.

Adding a Domain

The first step in setting up DNS is to add your domain. Click on the Add button. In the window that appears type your domain name in the Domain Name field. Do not enter www or anything like that. Press OK when you are done.

Adding an A Record

Now we need to add our first A record to the domain. Click on the domain in the Domain Management screen.

Click on the Add button to add our first record — a new window should appear. In this screen you will enter several pieces of information. For our example, A record we will be creating the contosso.com A record and pointing it to the IP of 12.34.56.78. Use the list below to help you fill them in:

·       Name - This is the fully qualified domain name. If you are creating a domain such as contosso.com you will enter contosso.com.

·       Content - For an A record this is going to be the IP address of the server. Enter 12.34.56.78.

·       TTL - This is the Time-To-Live value for the record. You may enter any value you want but we recommend using 300 (seconds).

·       Type - This is the record type. Leave it set to A.

Press the OK button to save your record.

You will see an A record listed for contosso.com pointing to 12.34.56.78.

Adding an MX Record

Now we would like to add an MX record so users of that domain can receive e-mail. For our example, we will set our MX record to mail.contosso.com. The creation process is just like it is with an A record but we need to modify the values below:

·       Name - This should match your domain. Set this to contosso.com.

·       Content - This is what your MX record will point to. Set this to mail.contosso.com.

·       Priority - This sets the priority of your MX record. For your first record set it to 10. Subsequent records will have 20, 30, 40, etc.

·       TTL - Set your Time-To-Live value to 300.

·       Type - Set your record time to MX.

Press the OK button to save your record.

You will see an MX record listed for contosso.com pointing to mail.contosso.com.

Adding a CNAME Record

Now we would like to add a CNAME record for www.contosso.com and point it to contosso.com. This will make it so people who go to contosso.com in their web browser will be able to find our website.

Click the Add button again and follow the same procedure. Use the information below to help you fill out the fields:

·       Name - This should be set to www.contosso.com.

·       Content - This should be set to the location where your CNAME should point. Enter contosso.com here.

·       TTL - Set this to 300 seconds.

·       Type - Set the type to CNAME.

Press OK and the record will be added.

You will see the new CNAME record added.

If you used your own domain for mail (like mail.contosso.com), you should also add a CNAME entry for mail.contosso.com that points to contosso.com.

Deleting a Record

If you made a mistake and would like to delete a record, clickthe check box to the right of the record and click the Delete button at the top. Accept the confirmation and the record will be deleted.

Deleting a Domain

If you would like to delete your domain entirely (and all records) you need to be in the Domain Management screen. This is the first tab you come to when you click on the DNS tab in your Cloud Server. Click on the check box to the right of the domain and click Delete at the top. Accept the confirmation and the domain will be deleted.

What are the DNS servers for my Cloud Server?

·       dns1.stabletransit.com

·       dns2.stabletransit.com



© 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

26 Comments

you state "we will set our MX record to mail.contosso.com" but nowhere do you enter the "mail.".

Hey Cyberg, what exactly were you trying to accomplish? Can you provide us with any specific examples with what you're trying to do, or inform us on? We'd love to help!

I am trying to set up the MX record by following your instructions. Under name, I enter mydomain.com. Under content, I enter mydomain.com again. Where do I enter <strong>mail.</strong>mydomain.com? You said "For our example, we will set our MX record to mail.contosso.com." but I don't see you doing that in the example.

It looks like the MX record section of the article could use a fix, actually. The article should recommend putting mail.contosso.com into the content field. We'll get that part fixed. Basically, put "mail.mydomain.com" into the MX field and that should do what you're after. You'd also need to create an A or CNAME record describing what "mail.mydomain.com" points to.

If I delete the cloud server associated with the domain, or all my cloud servers, does this also delete the domains and records from DNS?

No, the DNS information should remain after deleting servers.

Hi...

Is it possible to create my own DNS domain name? Instead of use dns1.stabletransit.com and dns2.stabletransit.com, use my own domain like ns1.mysite.com and ns2.mysite.com?

Thanks!

At this time, I'm afraid it's not possible to point your own address to our name servers. Servers doing lookups will expect reverse DNS to resolve to the address they use, which wouldn't happen if you're pointing your address to our servers.

You can use our [feedback forum](http://feedback.rackspacecloud.com/forums/71021-product-feedback) to suggest custom-labeled DNS servers as a feature.

What If my server is running on port 8080 , compared to port 80?

Your DNS entries won't actually refer to any ports - DNS points only to the server's IP address. The port is selected by the browser, and by default they'll try port 80 instead of 8080.

If you want users to get to your server on port 8080 you'd either need to set up a web server to listen to port 80 and redirect behind the scenes to 8080 (like mod_proxy for apache) or you'd want to give them a URL like:

http://www.example.com:8080

That will explicitly tell the browser to go to port 8080 instead of port 80.

Why do you not offer TXT records fro creating 'spf' entries?

It's an omission in our control panel, but if you submit a support ticket we can set a TXT record for you. We also have a DNS API available that allows you to set TXT records directly.

The next version of our control panel will include the ability to add TXT records, I'm told. I can't say just when it will be ready, but it's definitely in the works.

I have just setup a LAMP server on a Cloud Server account. I setup DNS from my domain www.damkostudios.com to my IP 50.56.225.227. Apache is listening on port 80 and if I curl the domain and or IP on the server it comes back as 200 but curling it from my local machine I get could not connect to host. If I browse to it I get Firefox can't establish a connection to the server at www.damkostudios.com:88. I do not have port 88 listening on the server so I have no idea where this is coming from. Am I missing somthing?

Hello Derek,
We'd love to help you resolve the issue that you are having being able to connect to your site. Our Fanatical Support staff is available 24 hours a day, and have access to check your account settings, and verify the functionality of our infrastructure. The best way to get assistance with this would be to open a chat with support (from the Cloud Control Panel under Support - follow the Live Chat link), or open a ticket documenting your steps so far, and we will be happy to investigate this with you. Thank you for your patience.

Hi,
I have set up bind on my server and I would like to manage the *.yyy.zzz subdomains
from my server (probably with a script or something like that). Is there any support
for NS type records? Or any way I can delegate all the subdomain queries to my
own server?

Thanks in advance,

NVlass

But could you please verify?

http://www.rackspace.com/knowledge_center/node/2066

It seems that I can add NS records using your API,
is this correct??

TIA,

NVlass

There is indeed a [DNS API](http://docs.rackspace.com/cdns/api/v1.0/cdns-devguide/content/index.html) available to our customers. It lets you manage the information that would be served up by our DNS servers for a domain and subdomains, including NS records pointing a subdomain's DNS to your own server.

Its a very good and easy tutorial for creating a DNS Record for Cloud Servers. I just followed it and it works great.

Why are DNS records tied to a particular server or load balancer? This makes is particularly inflexible. If I delete a cloud server, I've deleted my DNS records. DNS records should have their own control panel, separate from any particular cloud server.

I worked with an agent to move our DNS to rackspace. I mentioned I was scared about the mail server going down. The next day I had was informed by some customers that they could not reach us by email and it was auto returned to them by their local mail server.

So it's now 24 hours later and I work with the same agent as the day before and I found out that rackspace cloud servers are blacklisted by some email providers. I was given these links for a workaround.

The agent is sending you to http://www.postfix.org/docs.html.
The agent is sending you to http://www.rackspace.com/knowledge_center/index.php/Setting_up_a_Mail_Relay.
The agent is sending you to http://www.rackspace.com/knowledge_center/sendgrid.

Why is there not a warning in the rackspace system about this potential email problem?

Hello
I have a domain e.g. mydomain.com. During DNS-server registration I need in MX records to add records like HOST & POINTS TO. What does it mean? Does it mean Host=www.mydomain.com & ponts to:???, I don´t know. Where I get my IP-number? I am sorry to ask you these stupid questions. Thanks & kind regards.

The "MX" record refers to the address of a mail server that will be used to receive email going to your domain. If you're using a service to host email for the domain you should contact their support to get the MX host (like "mail.example.com"). You would also need to add a number that represents that mail server's priority in case you add a second sometime (if you just have one you can enter something like "10" for priority and be fine).

I'm not sure what "points to" would mean in the context of an MX record. It seems like "points to" would normally refer to the IP address of the domain. Usually that's set in the "A" record. So the best I can figure, it refers to setting up an A record for your mail server domain ("mail.example.com" might point to "1.2.3.4"), then you'd have to set that domain as your MX record.

Can someone update me with the procedure to add a MX Entry for a subdomain, e.g. my primary domain is abcd.com and MX is pointed to mail.abcd.com, now I am adding xyz.abcd.com as a sub domain, and want to add MX Entry to this subdomain pointing to mail.xyz.abcd.com in cloud panel.

You should be able to create a new "domain" using that subdomain. So if you have example.com, you can create a separate domain entry (rather than just an A record) for subdomain.example.com. From there you can set up the MX records for the subdomain.

If I try to add a domain that is currently set to ns.rackspace.com, I get an error.

What should I do?

What sort of error? The ns.rackspace.com address should work as a nameserver value. Could you have already configured the domain through another of our services (like Cloud Sites) and be running into a conflict there?

Add new comment