Hmmm, I'm not seeing the value proposition here. Or, I'm unclear why I'd use this service.

Here's how I understand redirect.name working:

===

1. An A/ALIAS/ANAME record for "example.com" points to a redirect.name service (self-hosted or otherwise).

2. The service sees the "example.com" HTTP request via the host header.

3. Service does a DNS lookup for a matching TXT record redirect rule.

4. When found, the service issues a 301/302 HTTP redirect, according to the matching rule.

===

Is this correct?

If so, compare to:

===

1. Create an A record for "example.com" that points to my Apache server.

2. Apache detects "example.com" via the host header.

3. Virtual host config for matching domain issues a 301/302 HTTP redirect.

===

Aside from shuffling the redirect config from Apache to DNS, what's the advantage of using redirect.name?

Additionally, every domain name registrar I've used includes a feature called "URL forwarding" that can redirect all HTTP requests for a domain to another. Again, what benefit does redirect.name provide that URL forwarding doesn't?

I'd love to hear the use cases.