Does DNS happen before every HTTP request?
A client generally needs an address for a hostname before establishing a new connection, but caches can reuse DNS answers and an existing connection can carry additional requests without a new lookup.
Answered in
One Request Across the Network: DNS, TCP or QUIC, TLS, HTTP, and WebSocketsTrace how application data crosses name resolution, transport, encryption and protocol layers—and correct common shortcuts about UDP, QUIC and DNS.
Read the full analysisOther questions this article answers
More network protocols questions
- Did HTTP/1.0 always open a new TCP connection for every resource?
- Does HTTP/2 eliminate every form of head-of-line blocking?
- Does HTTP/3 make packet loss irrelevant?
- Does HTTP/2 multiplexing prevent TCP head-of-line blocking?
- Does one lost QUIC packet stop every HTTP/3 stream?
- Is HTTP/3 always faster than HTTP/2?
- Is UDP an unreliable protocol with no congestion control?
- Is QUIC just UDP with encryption?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Network Protocols beat.