DNS Zones

By default each site will have a unique domain based on the top site domain, and the site name prepended. For example, if the Control Tower's domain is example.com and a site is named geo1 then its default domain will be geo1.example.com. Each host in a site will act as a name server for its domain. When applications has an ingress address, its name will be dynamically added to this domain. This can for example be used by other applications running in the same site.

If custom (and/or multiple) domains are required, it is possible to add them here. Applications can then use these when adding custom records in their per service dns-records or site-dns-records. It is only possible to add records from applications in zones that are configured here.

Update the dns

SecurityaccessToken
Request
query Parameters
validate
string <enumeration>

Validate the request but do not actually perform the requested operation

Value: "true"
Request Body schema:
Array of records (object) or error (object)
Responses
204

No Content

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

412

Precondition Failed

503

Service Unavailable (strongbox sealed)

patch/v1/config/dns
Request samples
zones:
  - name: default
    domain: curtainco.stockholm-sergel.site.example.acme.avassa.net

Delete the dns

SecurityaccessToken
Request
query Parameters
validate
string <enumeration>

Validate the request but do not actually perform the requested operation

Value: "true"
Responses
204

No Content

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

412

Precondition Failed

503

Service Unavailable (strongbox sealed)

delete/v1/config/dns

Replace or create the dns

SecurityaccessToken
Request
query Parameters
validate
string <enumeration>

Validate the request but do not actually perform the requested operation

Value: "true"
Request Body schema:
Array of records (object) or error (object)
Responses
201

Created

204

No Content

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

412

Precondition Failed

503

Service Unavailable (strongbox sealed)

put/v1/config/dns
Request samples
zones:
  - name: default
    domain: curtainco.stockholm-sergel.site.example.acme.avassa.net

Retrieve the configuration of dns

SecurityaccessToken
Request
query Parameters
fields
string

Retrieve only requested fields from the resource

See section fields

validate
string <enumeration>

Validate the request but do not actually perform the requested operation

Value: "true"
Responses
200

OK

304

Not Modified

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

412

Precondition Failed

503

Service Unavailable (strongbox sealed)

get/v1/config/dns
Response samples
zones:
  - name: default
    domain: curtainco.stockholm-sergel.site.example.acme.avassa.net

Retrieve the the state of dns

SecurityaccessToken
Request
query Parameters
fields
string

Retrieve only requested fields from the resource

See section fields

site
string

Send the request to the specfifed site

content
string <enumeration>

Filter descendant nodes in the response

Enum: "config" "nonconfig"
Responses
200

OK

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

503

Service Unavailable (strongbox sealed)

get/v1/state/dns
Response samples
zones:
  - name: default
    domain: curtainco.stockholm-sergel.site.example.acme.avassa.net
    records:
      - rr: _https._tcp.theater-room-manager 15 IN SRV 10 100 443 curtain-controller-1.theater-room-manager.curtainco.stockholm-sergel.site.example.acme.avassa.net.
      - rr: _http._tcp.theater-room-manager 15 IN SRV 20 100 80 curtain-controller-1.theater-room-manager.curtainco.stockholm-sergel.site.example.acme.avassa.net.
      - rr: curtain-controller-1.theater-room-manager 15 IN A 192.168.100.33
      - rr: curtain-controller.theater-room-manager 15 IN A 192.168.100.33
      - rr: cc.theater-room-manager 15 IN CNAME curtain-controller.theater-room-manager.curtainco.stockholm-sergel.site.example.acme.avassa.net