as of 9/1/2019 (and earlier due to vendor support), this service is not longer available, I would highly recommend using google domains’ synthetic records to perform these tasks.
Thank you for using my Anycast 301-www, all this IP Does is redirect users to here (if you enter the naked IP) or to the www.$domain of your domain.
Why you ask? Because 3rd party CDN’s and other hosting companies want you to point your domain to a CNAME, you can’t CNAME your root domain (https://tools.ietf.org/html/rfc2181#section-10). So you can now do this instead.
@ IN A 198.251.86.133; 301 service
www IN CNAME website.example.com
Simply point your naked domain to my anycast IP of 198.251.86.133 and I will redirect your user via 301 to www.example.com
@ IN A 198.251.86.133
If you’d like to help support my efforts, BeerME (donate)
If you’re curious who else uses this service, check the bots!
https://www.robtex.com/?dns=198.251.86.133
Anycast uses BGP Routing to broadcast the IP address in multiple datacenters, so you’ll automatically route to the nearest one!
Thanks!
I’m using this redirection in my self-hosted blog. At first I was skeptical, but it has been like 3 months since i configured it and works perfect. Thanks!
Thanks glad you found it useful.
Your BeerMe link does not seem to be working. Wrong DNS configuration maybe ? ;D
This forwarding service works like a charm. Is it supposed to be stable in the long term? If it ever stops working, what do you suggest we do?
Thanks for your help. It’s very much appreciated.
DOH! Yeah I ran out of resource records on my google domains account, I’ll update the post with a donate button.
I have zero intentions on dropping this service, as long as my upstream provider provides the service to me. In the event I am no longer able to host, I would email the hostmaster@example.com that the 301 service is going away. At some point I would like to have the option for users to enable HSTS Subdomain Preload and SSL with Letsencrypt, but not at this time.
Hi thanks for this service. I have set up 1 domain but it seems to redirect http:/www…. to https://www… which results in a browser message with invalid cert. Something I’ve set up wrong?
Steve
Looks the initial hit right to me Steve,
curl -I fleetriteparts.co.nz
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 02 Dec 2018 19:24:41 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: http://www.fleetriteparts.co.nz/
However www is redirecting http to https, so that’s on your end.
curl -I http://www.fleetriteparts.co.nz
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 02 Dec 2018 19:25:55 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 331
Connection: keep-alive
Location: https://www.fleetriteparts.co.nz/
Age: 116
X-Cache: HIT