TXT DNS Record can not be found for www.hendricksonphotographyweddings.com
If you have just updated your DNS record, please allow at most 48 hours for your DNS provider to propagate the change.
Why HTTP 301?
If you've moved your site to a new domain,
it's very important to redirect your existing users and search engine to your new URL.
Your existing users should still be ok with other
redirection or even
alias, but search engines don't.
Here is an
from Google explains why it is important to use
We try to provide the easiest way to setup a HTTP 301 redirection.
No registration, no installation, not even login to a web server.
All you need to do is to update two DNS records.
Steps with example
Let's say we want to redirect all URLs from
First we need to login to DNS hosting console:
Create an A Record of the domain / sub-domain you want to redirect with address of:
in this case we will need to make sure A Recordblog.example.org is pointing to 184.108.40.206
Create a TXT record (the redirect instruction) of the domain / sub-domain you want to redirect, with value of:
Note that the [Destination URL] is not merely a host name, it should be protocol://hostname:port/path
In our case, TXT record blog.example.org shall having a value of 200please.redirect=http://www.exampleblog.org/blog/
Refresh and Verify your settings
Once you created / updated above DNS settings, you can input your from hostname (in above example blog.example.org) to make sure the settings are correct.
Update / Cancel Redirection
Redirection will be cached in order to have a better performance.
If you want to change your redirection, you will need to use above refresh / verify tool to refresh our cache once you have updated TXT record (created in above Step 2).
If you do not want to use our redirection anymore. Simply remove the A Record (created in above Step 1). You can keep the TXT record for future use. No side effect, promise.
There are several other options to setup a redirection.
Use your own HTTP Server
You can always use your own HTTP server to perform HTTP 301 redirect.
Nowadays all popular web servers should support HTTP redirection.
This is exactly the same way as we do.
It may take couple of hours to setup and verify if you are not familiar with them.
You can use our free HTTP monitoring tool to make sure you web server are using 301 redirect correctly.
DNS / Web hosting provider
Some DNS / Web hosting company provides this feature to use their web server to redirect too.
The setup will be easier compared with the first alternative.
This is also working in the same way.
Again, you can use our HTTP monitoring tool to verify redirection.
Use Google App to redirect naked domain
We have to admit, though it brings us great shame to say: Google's servers are usually faster than ours.
Click here to check performance difference when redirecting 200plz.com.
Google is used to redirect from 200plz.com to www.200plz.com, and our server will redirect from www.200plz.com to www.200please.com
However, there are several limitations for this approach:
Create DNS records to map new domains to the same server Not recommended
You can create CNAME / A records to make new domain resolves to the existing servers. But just don't do this.
A web site can NEVER be moved in this way.
Your users will still visit your old site and search engine will still crawl you old pages.
Your new site will be treated as merely another site with duplicated content.