Difference between revisions of "Swift/ideas/txt lookup middleware"
Jean.caron (talk | contribs) (TXT lookup middleware) |
Jean.caron (talk | contribs) |
||
| 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 : | ||
Revision as of 16:56, 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
