Hmmm, I'm not seeing the value proposition here. Or, I'm unclear why I'd use this service.<p>Here's how I understand redirect.name working:<p>===<p>1. An A/ALIAS/ANAME record for "example.com" points to a redirect.name service (self-hosted or otherwise).<p>2. The service sees the "example.com" HTTP request via the host header.<p>3. Service does a DNS lookup for a matching TXT record redirect rule.<p>4. When found, the service issues a 301/302 HTTP redirect, according to the matching rule.<p>===<p>Is this correct?<p>If so, compare to:<p>===<p>1. Create an A record for "example.com" that points to my Apache server.<p>2. Apache detects "example.com" via the host header.<p>3. Virtual host config for matching domain issues a 301/302 HTTP redirect.<p>===<p>Aside from shuffling the redirect config from Apache to DNS, what's the advantage of using redirect.name?<p>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?<p>I'd love to hear the use cases.