Difference between revisions of "Swift/ideas/txt lookup middleware"
Jean.caron (talk | contribs) (TXT lookup middleware) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
'''TXT lookup middleware''' | '''TXT lookup middleware''' | ||
| − | Why ? | + | Why ? |
| − | How ? | + | to be able to remap without using the CNAME record. |
| + | Some DNS providers use the "CNAME Flattening" to resolve on their side the destination. | ||
| + | Therefore, the CNAME value is not available. | ||
| + | example with Cloudflare : | ||
| + | -> https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root | ||
| + | |||
| + | How ? | ||
* Proposed dns entry : | * Proposed dns entry : | ||
| Line 19: | Line 25: | ||
contact #openstack-swift : jcaron | contact #openstack-swift : jcaron | ||
| + | |||
| + | |||
| + | see https://community.runabove.com/kb/en/object-storage/how-to-put-object-storage-behind-your-domain-name.html | ||
Latest revision as of 21:36, 25 January 2017
TXT lookup middleware
Why ?
to be able to remap without using the CNAME record. Some DNS providers use the "CNAME Flattening" to resolve on their side the destination. Therefore, the CNAME value is not available. example with Cloudflare : -> https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root
How ?
- Proposed dns entry :
('_swift-remap.' + subdomain) IN TXT "account={ACCOUNT_NAME} container={CONTAINER_NAME}"
-> https://tools.ietf.org/html/rfc1464
- proposed implementations :
create a dedicated middleware : txt_lookup.py ? rename cname_lookup.py to dns_lookup.py and add the txt lookup feature ?
contact #openstack-swift : jcaron
