Bases: designate.plugin.DriverPlugin
Base class for backend implementations
Create a DNS zone.
Parameters: |
|
---|
Bases: designate.exceptions.BadRequest, designate.backend.impl_akamai.EnhancedDNSException
Raised when an attempt to delete a zone which is still delegated to Akamai is made
Bases: designate.exceptions.DuplicateZone, designate.backend.impl_akamai.EnhancedDNSException
Raised when an attempt to create a zone which is registered to another Akamai account is made
Bases: object
EnhancedDNS SOAP API Client
Bases: designate.exceptions.Backend
Bases: suds.transport.https.HttpAuthenticated
Bases: designate.exceptions.Forbidden, designate.backend.impl_akamai.EnhancedDNSException
Raised when an attempt to modify a zone which is registered to another Akamai account is made.
This appears to be returned when creating a new subzone of zone which already exists in another Akamai account.
Bind 9 backend. Create and delete zones by executing rndc
Bases: object
DynECT service client.
The API might return a job nr in the response in case of a async response: https://github.com/fog/fog/issues/575
Bases: designate.exceptions.Backend
The base exception class for all HTTP exceptions.
Bases: designate.exceptions.BadRequest, designate.backend.impl_dynect.DynClientError
Bases: designate.backend.base.Backend
Support for DynECT as a secondary DNS.
Knot DNS agent backend
Create, update, delete zones locally on a Knot DNS resolver using the knotc utility.
Supported Knot versions: >= 2.1, < 3
Warning
Untested, do not use in production.
Note
If the backend is killed during a configuration transaction it might be required to manually abort the transaction with sudo knotc conf-abort
Configured in [service:agent:knot2]
Bases: designate.backend.agent_backend.base.AgentBackend
Run the Knot client and check the output
Parameters: |
|
---|
Create or delete a zone while locking, and within a Knot transaction. Knot supports only one config transaction at a time.
Raises: | exceptions.Backend |
---|
Instruct Knot to request an AXFR from MiniDNS. No need to lock or enter a configuration transaction.
Create a new Zone by executing knotc Do not raise exceptions if the zone already exists.
Parameters: | zone (raw pythondns Zone) – zone to be created |
---|
Delete a new Zone by executing knotc Do not raise exceptions if the zone does not exist.
Parameters: | zone_name (str) – zone name |
---|
gdnsd agent backend
Create, update, delete zones locally on a gdnsd resolver using the gdnsd utility.
Supported Knot versions: >= 2.1, < 3
Warning
Untested, do not use in production.
Note
If the backend is killed during a configuration transaction it might be required to manually abort the transaction with sudo gdnsd conf-abort
Configured in [service:agent:gdnsd]
Bases: designate.backend.agent_backend.base.AgentBackend
Generate a filename for a zone file “/” is traslated into “@” Non-valid characters are translated into NNN where NNN is a decimal integer in the range 0 - 255 The filename is lowercase
Returns: | valid filename (string) |
---|
Create or update a zone file atomically. The zone file is written to a unique temp file and then renamed
Query the local resolver for a zone Times out after SOA_QUERY_TIMEOUT
Djbdns DNS agent backend
Create, update, delete zones locally on a Djbdns DNS resolver using the axfr-get utility.
Warning
Untested, do not use in production.
Configured in [service:agent:djbdns]
Bases: designate.backend.agent_backend.base.AgentBackend
Concatenate all zone datafiles into ‘data’
Instruct axfr-get to request an AXFR from MiniDNS.
Raises: | exceptions.Backend on error |
---|
Rebuild data.cdb file from zone datafiles Requires global lock
On zone creation, axfr-get creates datafiles atomically by doing rename. On zone deletion, os.remove deletes the file atomically Globbing and reading the datafiles can be done without locking on them. The data and data.cdb files are written into a unique temp directory
Bases: designate.backend.agent_backend.base.AgentBackend