Why it is derived
Provider associations make delegation movement comparable
Why it matters
Provider Resolution helps describe visible concentration, migration and delegation patterns across the fixed panel while keeping the underlying name-server evidence distinct.
What visible change may mean
A change may reflect direct provider use, reseller or white-labelled services, registrar DNS, delegated infrastructure or maintenance.
Interpretation limits
Association does not establish a commercial relationship
The derived association may be incomplete or ambiguous and does not establish a direct customer relationship, endorsement, service quality, ownership, responsibility or internal operating arrangement.
What .auDO derives
A provider association resolved from name-server evidence
The direct source evidence is the delegated name-server set. .auDO resolves known targets through versioned Provider Resolution rules and a versioned Provider Catalogue. The observed targets remain the evidence; the provider association is a derived classification. The Provider Resolution and Provider Catalogue versions used are retained as classification provenance.
Technical fields
Common retained observations
DNS-provider movement
A DNS-provider movement event requires both a change in the observed name-server target set and a change in resolved provider identity under the same current classification context. A catalogue-only label change with unchanged targets is retained as classification context, not observatory movement.
Where to use this evidence
View aggregate DNS-provider posture
Supporting concept
The delegation evidence behind the association
Related signals