Azure DNS

These terms describe the origin API served by the adapter, not direct calls to the target service. Management-request latency covers accepting and handling the API call; it does not promise that a cloud resource finishes provisioning within that time.

​

Service level agreements

Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider’s own SLA. Each origin-to-target pair has its own terms or an explicit pending status. See the SLA tables, measurement rules, and scaling conditions.

​

Azure DNS to Route53

Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability. What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA. How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded. Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

​

What this adapter does

For aws::1.0.0::route53, the adapter maps zone identity, supported record sets and target-specific aliases. The request timer ends at the correct origin-shaped response; DNS publication, recursive cache expiry and health-check convergence are separate. A low control API latency does not make a cached answer change immediately. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.

​

How the latency targets were chosen

DNS zone changes: 20 ms monthly p99. Zones_CreateOrUpdate, Zones_Delete. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Bounded DNS record-set changes: 20 ms monthly p99. RecordSets_CreateOrUpdate, RecordSets_Delete, RecordSets_Update. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Private-zone and network-link changes: 20 ms monthly p99. PrivateZones_CreateOrUpdate, PrivateZones_Delete, VirtualNetworkLinks_CreateOrUpdate, VirtualNetworkLinks_Delete. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

​

What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

​

Availability and failures

The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.

​

Scaling and target-service capacity

Scale API handlers and background workers separately. The agreement bounds resource count, concurrent changes, status polling, configuration size and burst growth. More replicas do not remove a shared metadata-store bottleneck or a target API quota. Tensor9 is responsible for adapter capacity within that envelope; the customer supplies target capacity and permissions. Native resource readiness is monitored separately from request acceptance. DNS change bursts should be bounded by records as well as requests. Many aliases or network links can add dependency lookups. Application DNS query volume normally reaches native authoritative/resolver infrastructure, not this management request path. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

​

Data and behavior guarantees

Preserve names, types, TTL values and supported record content without widening zone visibility. Target-specific apex aliases, routing policies, private-zone links and automatic registration retain their documented limits. A record accepted by the adapter must not silently refer to the wrong resource; propagation delay alone is not evidence of a bad mapping.

​

Example and diagnosis

Update the A record for api.example.test and its TTL. The record-change response can meet 20 ms while existing recursive caches retain the previous answer until expiry. Compare the translated authoritative record with the application’s resolver result before deciding whether the failure is in adapter translation or DNS caching. Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

​

Azure DNS to Cloud DNS

Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability. What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA. How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded. Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

​

What this adapter does

For google::1.0.0::dns, the adapter maps zone identity, supported record sets and target-specific aliases. The request timer ends at the correct origin-shaped response; DNS publication, recursive cache expiry and health-check convergence are separate. A low control API latency does not make a cached answer change immediately. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.

​

How the latency targets were chosen

DNS zone changes: 20 ms monthly p99. Zones_CreateOrUpdate, Zones_Delete. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Bounded DNS record-set changes: 20 ms monthly p99. RecordSets_CreateOrUpdate, RecordSets_Delete, RecordSets_Update. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Private-zone and network-link changes: 20 ms monthly p99. PrivateZones_CreateOrUpdate, PrivateZones_Delete, VirtualNetworkLinks_CreateOrUpdate, VirtualNetworkLinks_Delete. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

​

What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

​

Availability and failures

The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.

​

Scaling and target-service capacity

Scale API handlers and background workers separately. The agreement bounds resource count, concurrent changes, status polling, configuration size and burst growth. More replicas do not remove a shared metadata-store bottleneck or a target API quota. Tensor9 is responsible for adapter capacity within that envelope; the customer supplies target capacity and permissions. Native resource readiness is monitored separately from request acceptance. DNS change bursts should be bounded by records as well as requests. Many aliases or network links can add dependency lookups. Application DNS query volume normally reaches native authoritative/resolver infrastructure, not this management request path. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

​

Data and behavior guarantees

Preserve names, types, TTL values and supported record content without widening zone visibility. Target-specific apex aliases, routing policies, private-zone links and automatic registration retain their documented limits. A record accepted by the adapter must not silently refer to the wrong resource; propagation delay alone is not evidence of a bad mapping.

​

Example and diagnosis

Update the A record for api.example.test and its TTL. The record-change response can meet 20 ms while existing recursive caches retain the previous answer until expiry. Compare the translated authoritative record with the application’s resolver result before deciding whether the failure is in adapter translation or DNS caching. Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

​

Debug this service

For requests through a service adapter, use Explain and request diagnostics to investigate the selected mapping. Follow the BYOC service-adapter debugging runbook to capture and interpret the diagnostic evidence. Service Catalog.