Why DNS Redirect?

Migrating to a new domain is a hassle. It doesn't have to be.

Migrating from one domain to another can cause a lot of problems. Some of the issues may be broken links, bookmarks and a hit to your SEO. DNS Redirect provides an easy and affordable service for ensuring that users and search engines can still find your content.

How does DNS Redirect work?

DNS Redirect inspects HTTP requests coming into the service. If the requests orginated from one of the configured source domains, we'll forward the client to the correct domain using an HTTP redirect. You can configure the status code you'd like to return. We maintain the path and query string parameters provided.

HTTPS support is provided by Let's Encrypt. We provision and renew certificates automatically and store them securely in AWS.

How does DNS validation work?

We take advantage of the Let's Encrypt HTTP-01 challenge. After you configure DNS, you can add your domain to DNS Redirect and we'll use Let's Encrypt to validate you are the owner the domain.

Are there limitations on the number of subdomains I can register?

While we do not enforce subdomain limits for paid subscriptions, Let's Encrypt does have a particular rate limit of 50 certificates per Registered Domain, per week. If you need to register more than 50 subdomains, contact us about wildcard certificates.

Why not use registrar forwarding?

It is true that registrars like GoDaddy provide a service for forwarding domains and subdomains to another domain using an HTTP redirect. The problem with services like this are they are limited to the domain itself and do not take into account the path and query string. This results in a forward to the new domain but a failure to forward to the proper path. This results in 404 errors for your end users. DNS Redirect also provides transformations for paths and query strings.

Aren't there free services that do this?

It's true that there are services like redirect.center that provide this functionality. The problem with services such as this is that they don't handle HTTPS certificates so your HTTPS redirects will not work. Users will see warnings because of the certificate mismatch. We provide end to end HTTPS. Even our free service provides HTTPS support.

Can't I implement this myself?

Sure! It's certainly possible implement this type of functionality yourself. We just make it easy so there are no websites to develop and no certificates to manage.