Separate DNS-SD enumeration from SRV reachability and TXT metadata

Treat this document as a focused evidence review: Separate DNS-SD enumeration from SRV reachability and TXT metadata. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 6763 — DNS-Based Service Discovery from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• DNS-SD enumeration queries a service-type name for PTR records whose targets are the available service-instance names. The research record locates this support at Section 4.1 (Structured Service Instance Names).
• After choosing an instance, a client queries that instance name for SRV and TXT records; SRV supplies target host and port, while TXT supplies service metadata. The research record locates this support at Section 5 (Service Instance Resolution).
• Every DNS-SD service advertisement has a TXT record with the same name as its SRV record, even when the TXT payload is empty. The research record locates this support at Section 6 (Data Syntax for DNS-SD TXT Records).

The source support ends with the statements listed above. Use them to examine authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers in the applicable environment, not to imply a wider guarantee.

What the source does not establish

This RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. No current deployment state or change approval follows from the source alone. Validate Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Section 4.1 (Structured Service Instance Names), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 5 (Service Instance Resolution), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 6 (Data Syntax for DNS-SD TXT Records), which observable configuration, record, or test can confirm applicability here?
• Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?
• Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

A reviewer should be able to retrace the decision from Section 4.1 (Structured Service Instance Names); Section 5 (Service Instance Resolution); Section 6 (Data Syntax for DNS-SD TXT Records) through zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior. Record what was collected, where, when, by whom, and which system or role it represents.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• RFC 6763 — DNS-Based Service Discovery — RFC Editor / Internet Engineering Task Force