When a scraper requests `https://example.com`, the operating system's DNS resolver looks up the IP address associated with the domain by querying a recursive resolver, which in turn consults authoritative name servers. The result is cached for a period defined by the record's TTL (Time To Live). DNS resolution adds latency to the first request to each domain; subsequent requests use the cached IP.
For large-scale scraping, DNS can become a bottleneck or a detection surface. DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) encrypt resolver queries, preventing network-level DNS snooping. Some scraping proxy providers handle DNS resolution server-side so that the client's IP is never exposed in DNS traffic.
IP rotation via proxies means the scraper's DNS-resolved IP changes with each request or session. However, if the scraper and its proxy share the same DNS resolver, query patterns can reveal that many seemingly distinct IPs are controlled by the same entity.