Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

When I register a domain with a registrar and want to host it at a hosting company, I usually set the hosting compan's DNS servers in the interface at the registrar. But I now see a hosting company which is asking me to set "A Records" at the registrar and does not provide DNS servers.

Do these two approaches accomplish the same thing?


(I note this related question, which discusses the architecture but does not explain whether the two approaches are functionally the same.)

share|improve this question

closed as off-topic by TomTom, Andrew Schulman, kasperd, mdpc, Ward Oct 28 at 6:05

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – TomTom, Andrew Schulman, kasperd, Ward
If this question can be reworded to fit the rules in the help center, please edit the question.

1  
ietf.org/rfc/rfc1035.txt –  MDMarra Oct 28 '11 at 13:40

3 Answers 3

up vote 3 down vote accepted

Two good answers already, although I don't think either of them answer the question particularly clearly.

Do these two approaches accomplish the same thing?
Yes (if you're just talking about getting the website working)
Ultimately, both end up with an A record (as you can tell from the other answers, a type of DNS record) for your website pointing to your host's web server, which results in your website being accessible from your domain name.

Version 1) You configure your domain settings at the registrar to point to your host's DNS servers
This hands control of DNS for the domain to the host; the host's DNS servers will already be set up with all of the records you need (eg, A records) for your domain so you don't need to worry about setting up individual records. www.yourdomain.com will point to your website, ftp.youdomain.com will probably point to the address for ftp, the mail will already be set up etc.

Version 2) You use your registrars DNS servers, and configure an A record pointing to your host's web server
This leaves control of DNS for the domain with your registrar, you have to set up any DNS records yourself. They've given you the details for the record to set up the website, but you may also want to set up records for FTP and mail - this is main difference you'll see between the two approaches.

share|improve this answer

The registrar's technical service typically consists of running a DNS server that hands out an NS record pointing at your DNS server, which you then configure to give out A records for the names that should be resolvable.

When you are with a provider that offers DNS service as well as hosting, the registrar points at their DNS server (NS), which points at their hosting (A). If your new provider does not provide a DNS server, your options are to get that service separately and have the registrar point their NS there, or to ask the registrar to configure an A record directly, removing the need for a separate DNS server for your domain.

Whether that is a sensible thing to do depends on the registrar as you lose a bit of flexibility for creating subdomains and some registrars charge extra for the service and/or changes to the zone data.

share|improve this answer

You're getting confused with terminology, which isn't helped by hosting providers using unclear "friendly" language.

An "A Record" is just one type of record which is exists within DNS. It's all a matter of context. See this list:

http://en.wikipedia.org/wiki/List_of_DNS_record_types

Those are all the things that you COULD configure within your DNS server. In other words, you've never been configuring DNS as such - someone else has done that - you're just configuring a field within their servers.

But yes, generally, when you're configuring Y's DNS servers, you're probably setting up an "A Record".

You may have also come across a "CNAME" which lets you point to another DNS name, rather than an IP address.

I hope that make some sense - it's a little hard to explain from scratch. This Wiki page explains more of the fundementals of DNS:

http://en.wikipedia.org/wiki/Domain_Name_System

share|improve this answer
    
easiest way to remember cnames is its basically an alias. so Cname of vpn.yourdomain.com may point to netserver.yourdomain.com which has an A record that gives an IP of 123.123.123.123. –  Sirex Oct 28 '11 at 10:51

Not the answer you're looking for? Browse other questions tagged or ask your own question.