It is really not a good idea to let your naked record go to a 3rd party. If you need your root to be an A name, go with a DNS provider that will do URL redirects. If you trust them with DNS resolution of your domain you can trust them to not go crazy with your root record.
EDIT:
If you are looking for a host that will do this, http://NameCheap.com is how I do it but I understand GoDaddy and Hover does it too. Seriously... go with a reputable registrar that has these simple features it will pay off in the end.
I agree with this 100% If anyone wants to implement something like this on a server which you have control over, here is the mod_rewrite line which enables this "service":
when I saw someone retweet about this service in my stream it was a bit confusing... can't really see the purpose myself, when you, as you mention, you can handle this within the confines of your own registrar.
I'm curious as to why the developer felt the need to make this.
I may be wrong here, but I think there's one good reason to use anything.example.com instead of example.com: with the naked domain, you can't have a separate domain for static assets which the client doesn't send the cookie to (for performance improvement). If you set a cookie with the domain example.com, it will still get sent to static.example.com.
Granted, you could use examplecdn.com or something, but then you have to register and manage more domains.
only reason www is usefull is because common cms (forums, blogs, comments, ....) convert www.example.com to a clickable link, but example.com not. yeah stupidbutthats the way it is.....
What the website advocates, redirecting site traffic through them, is a very bad idea. If you don't know why this might be so, stop and ask yourself why you are in charge of modifying the zone records.
It's a pretty clever idea, I've come across loads of sites that have a naked domain but no www.
As clever as it is though, it serves no real world purpose, anyone clever enough to setup up their own domain will be able to set up a www subdomain, be it dns level or using a 301 redirect.
[+] [-] achew22|15 years ago|reply
EDIT: If you are looking for a host that will do this, http://NameCheap.com is how I do it but I understand GoDaddy and Hover does it too. Seriously... go with a reputable registrar that has these simple features it will pay off in the end.
[+] [-] awormus|15 years ago|reply
RewriteRule (.*) http://www.%{HTTP_HOST}/$1 [R=301,L]
[+] [-] bradleyjoyce|15 years ago|reply
I'm curious as to why the developer felt the need to make this.
[+] [-] falseflags|15 years ago|reply
[+] [-] jamuraa|15 years ago|reply
[+] [-] storborg|15 years ago|reply
Granted, you could use examplecdn.com or something, but then you have to register and manage more domains.
[+] [-] calloc|15 years ago|reply
At least, that is what I use it for myself.
[+] [-] trafficlight|15 years ago|reply
[+] [-] bauchidgw|15 years ago|reply
[+] [-] twir|15 years ago|reply
Don't most self-respecting DNS providers allow you to do this?
[+] [-] vinhboy|15 years ago|reply
[+] [-] amoore|15 years ago|reply
[+] [-] bugsy|15 years ago|reply
[+] [-] makethetick|15 years ago|reply
As clever as it is though, it serves no real world purpose, anyone clever enough to setup up their own domain will be able to set up a www subdomain, be it dns level or using a 301 redirect.
[+] [-] unknown|15 years ago|reply
[deleted]
[+] [-] gcr|15 years ago|reply
[+] [-] Fileformat|15 years ago|reply
[+] [-] upinsmoke|15 years ago|reply
[+] [-] TomasSedovic|15 years ago|reply
But as others pointed out, decent DNS registrars will let you do this in your DNS administration account. Which is much safer.