Google, Inc. Cloudflare Many web interactions require a client to resolve a hostname before it can establish a connection to a service. While DNS is generally efficient, each lookup incurs some delay and exposes information about the user's browsing activity to the recursive resolver and upstream infrastructure. This document explores techniques by which a client may receive DNS-derived address data as part of an application-layer response, so that it can initiate a connection without performing a separate DNS lookup for the same target. The mechanisms discussed here are intended to reduce lookup latency and potentially improve privacy, but they also raise significant questions about trust, freshness, and security. The document does not prescribe a single normative mechanism; instead, it describes several design options and the trade-offs associated with each.