Forum Moderators: phranque
I have never done this before, so I'm a bit lost. I have set up an A record and the set up basically works. But I would like to get it set up correctly.
1) There is an A record for domain.com to the host IP address. I also want to direct www.domain.com to the host's IP (and will resolve canononical problems there with htaccess). Currently there is a CNAME record for www.domain.com. Would it be best to delete this and set up an A record for www.domain.com?
2) TTL for A records - the IP address for the host is static. What would be the standard TTL to use?
3) Email - I don't want to set up anything fancy. I just want to ensure that emails to anything@domain.com gets routed to my host server. Do I need to set up MX records, or is it best not to?
I'm a newbie when it comes to DNS, so any help will be appreciated.
Currently there is a CNAME record for www.domain.com. Would it be best to delete this and set up an A record for www.domain.com?
It's a nuance that you probably should not concern yourself with at this point. It would be every so slightly faster for your users if you use an A record. It would be ever so slightly more convenient for you if you use a CNAME, and you were ever to change the IP address in the future. (Because you would only have to change it on one record.)
2) TTL for A records - the IP address for the host is static. What would be the standard TTL to use?
1-2 days. This normally defaults to a reasonable value if you do not change it.
When/if you do move your site, it's useful to change the TTL to a small value in advance of the actual move, then push it back up after the move. That keeps your users in limbo for less time.
3) Email - I don't want to set up anything fancy. I just want to ensure that emails to anything@domain.com gets routed to my host server. Do I need to set up MX records, or is it best not to?
It's best not to - if you don't want to get any mail. ;)
Yes, you need an MX record. Records (plural) if you have a backup mail server.
While you are at it, play nice and set up an SPF record. This will help protect you from spam that spoofs your domain name. It's actually a specially-formatted TXT record. There's a setup wizard for this at openspf.org