1. The software first checks redirect.hostname.domainname.com for a TXT record, since technically, CNAME records may not have sibling resources. Using the TXT record on the same hostname as a CNAME was causing problems on one known DNS provider (Amazon Route 53). 2. The path is only appended if the location contains two slashes. Previously the path was always being appended, such that: Given the location "http://foo.com/xyz", if the user went to "http://abc.com/123", the target would be "http://foo.com/xyz123". The location field should now be used as following: location=http://google.com -- if you want domfo to append the path automatically location=http://google.com/xyz -- if you want to hardcode a certain path location=http://google.com/ -- if you want to hardcode /
|Failed to load latest commit information.|
|event.d||renaming script to be more aligned with future versions of upstart|
|.gitignore||added plugin code to use twistd|
|README||added plugin code to use twistd|
|domfo.py||Two notable changes:|
domfo ===== Domain Forwarder This is a simple web server that redirects requests to the location found in the TXT record for the domain in the host of the incoming request. There is no security, so if somebody knows the host/IP of your running domfo instance, they can use it to forward their domain. Here's how you use it once it's running. Say it's running on port 80 at redirect.domdori.com ... so if you want to use it to redirect your new domain "superdomain.com" to "http://myblog.com", you set up two DNS records for superdomain.com: * CNAME record to redirect.domdori.com * TXT record with "location=http://myblog.com" And you're done! Requests to http://superdomain.com will redirect to http://myblog.com once DNS propagates.