1 # PowerDNS RADOS Gateway backend
3 A backend for PowerDNS to direct RADOS Gateway bucket traffic to the correct regions.
5 For example, two regions exist, US and EU.
10 A global domain o.myobjects.com exists.
12 Bucket 'foo' exists in the region EU and 'bar' in US.
14 foo.o.myobjects.com will return a CNAME to foo.o.myobjects.eu
15 bar.o.myobjects.com will return a CNAME to foo.o.myobjects.us
17 The HTTP Remote Backend from PowerDNS is used in this case: http://doc.powerdns.com/html/remotebackend.html
19 PowerDNS must be compiled with Remote HTTP backend support enabled, this is not default.
21 For more information visit the [Blueprint](http://wiki.ceph.com/Planning/Blueprints/Firefly/PowerDNS_backend_for_RGW)
27 remote-connection-string=http:url=http://localhost:6780/dns
30 Usage for this backend is showed by invoking with --help. See rgw-pdns.conf.in for a configuration example
32 The ACCESS and SECRET key pair requires the caps "metadata=read"
36 $ curl -X GET http://localhost:6780/dns/lookup/foo.o.myobjects.com/ANY
38 Should return something like:
43 "content": "foo.o.myobjects.eu",
45 "qname": "foo.o.myobjects.com",
52 You can run this backend directly behind an Apache server with mod_wsgi
54 WSGIScriptAlias / /var/www/pdns-backend-rgw.py
56 Placing that in your virtualhost should be sufficient.
58 Afterwards point PowerDNS to localhost on port 80:
61 remote-connection-string=http:url=http://localhost/dns