so for example for each new zone I'd create with their utility I have to run two more queries to add the appropriate key
I haven't checked the api for that
id (string) – Opaque zone id (string), assigned by the server, should not be interpreted by the application. Guaranteed to be safe for embedding in URLs.
name (string) – Name of the zone (e.g. “example.com.”) MUST have a trailing dot
type (string) – Set to “Zone”
url (string) – API endpoint for this zone
kind (string) – Zone kind, one of “Native”, “Master”, “Slave”
rrsets ([RRSet]) – RRSets in this zone (for zones/{zone_id} endpoint only; omitted during GET on the …/zones list endpoint)
serial (integer) – The SOA serial number
notified_serial (integer) – The SOA serial notifications have been sent out for
edited_serial (integer) – The SOA serial as seen in query responses. Calculated using the SOA-EDIT metadata, default-soa-edit and default-soa-edit-signed settings
masters ([string]) – List of IP addresses configured as a master for this zone (“Slave” type zones only)
dnssec (boolean) – Whether or not this zone is DNSSEC signed (inferred from presigned being true XOR presence of at least one cryptokey with active being true)
nsec3param (string) – The NSEC3PARAM record
nsec3narrow (boolean) – Whether or not the zone uses NSEC3 narrow
presigned (boolean) – Whether or not the zone is pre-signed
soa_edit (string) – The SOA-EDIT metadata item
soa_edit_api (string) – The SOA-EDIT-API metadata item
api_rectify (boolean) – Whether or not the zone will be rectified on data changes via the API
zone (string) – MAY contain a BIND-style zone file when creating a zone
account (string) – MAY be set. Its value is defined by local policy
nameservers ([string]) – MAY be sent in client bodies during creation, and MUST NOT be sent by the server. Simple list of strings of nameserver names, including the trailing dot. Not required for slave zones.
master_tsig_key_ids ([string]) – The id of the TSIG keys used for master operation in this zone
slave_tsig_key_ids ([string]) – The id of the TSIG keys used for slave operation in this zone
It would be pretty sweet if there were a "master" tsig key used for all zones on the same server, could be rotated or what not
I can annotate that list and get back to you. The zone 'kind' refers to replication, where 'Native' is the back-end db native replication and the other two refer to the usual DNS AXFR roles
have a good evening...
for SQS should the queue type be standard or FIFO? I see standard mentioned in the docs: https://www.vinyldns.io/operator/setup-sqs but in code its FIFO
looks like FIFO queues aren't supported
Anything in particular you are looking for?
we have error rate, latency, including count in several places. The web api, database calls, etc.
There is also a /health endpoint exposed for general system health
no problem though, we'll figure it out :)
Not that that’s an excuse, but it is part of the reason we didn’t prioritize metrics
for metrics
All db calls start with
repo for metrics
so for metrics, you will have
Endpoint.createZone.latency and Endpoint.createZone.errorRate
Those all use standard codeahale / dropwizard metrics. Latency is a histogram, errorRate is a meter
There is more info on the metrics in general, but should give you a better idea of what each metric means
https://github.com/vinyldns/vinyldns-python/blob/0e49e2faf636ede752e7a8b3e8a3aa212b5b7150/tests/sampledata.py#L48 - shows creating an NS record, adding multiple records in the array should be fine
if you are using batch changes (dns requests) instead of creating the recordsets directly, this is an example in python of creating the batch change (you would need to replace AData with NSData) - https://github.com/vinyldns/vinyldns-python/blob/0e49e2faf636ede752e7a8b3e8a3aa212b5b7150/tests/test_batch_change.py#L70
batch changes are a little tricky, as you need multiple
AddRecord, each with a single NSData
That was helpful! I got the add working now.. for others reference this is my code block, (DEFAULT_NAMESERVERS is a list of ns strings)..
for record in DEFAULT_NAMESERVERS:
record_list.append(NSData(record))
record_set = RecordSet(parent_zone_object.id, zone_name, RecordType.NS, 3600,records=record_list)
VINYLDNS_CLIENT.create_record_set(record_set)
actually, search function should be there (maybe not released?) - https://github.com/vinyldns/vinyldns-python/blob/0e49e2faf636ede752e7a8b3e8a3aa212b5b7150/src/vinyldns/client.py#L568
For delete recordset, you can get the record set to get the ID and then issue the delete https://github.com/vinyldns/vinyldns-python/blob/0e49e2faf636ede752e7a8b3e8a3aa212b5b7150/src/vinyldns/client.py#L505