I have configured my DNS.The two main domains following the Google instruction for blogger/blogspot sites.
-www.error418.fr for the french version of the blog
-www.error418.org for the english version.
In fact, I had to be patient and wait for the DNS propagation. You can track the propagation with some sites like http://www.whatsmydns.net/
Reducing the TTL may be an good idea, but you must do it the night before the change to be sure it is active.
The domain 418error.net is redirected to error418.org, with an .htaccess file 301 redirection.
Options +FollowSymLinks
RewriteEngine on
RewriteRule (.*) http://www.error418.org [R=301,L]
Other forms of redirection may be penalized by the Google search engine, which could be considered as "duplicate content".
To do the expriment I redirected www.error418.net with the simple redirection interface of my registar.
The www.htcpcp.net, domain will be used for my teapot, with an simple 'A' record.
After switching to a new web host, and to tell you if most of the world is accessing your site at the old server or the new one! As an alternative to whatsmydns.net, you can refer to https://dnschecker.org/, with the display of 27 public serves to check the live propagation worldwide results instantly.
ReplyDeleteGreat write-up on the DNS setup. The tip about lowering the TTL the night before a change is one a lot of people learn the hard way. Using a 301 redirect in .htaccess instead of a registrar's basic forwarding is also much cleaner for search engines. It's a good reminder that choosing the right tool for the job saves headaches, whether that's a proper redirect or something physical like an adjustable spreader bar for a lift where a fixed length won't work. Looking forward to seeing how the teapot turns out!
ReplyDelete