Managing request routing information utilizing client identifiers

A computer-implemented system comprising:

• one or more computing devices comprising a processor configured with specific computer executable instructions to:
• obtain, by a service provider, a first request for content from a first client computing device;
• determine, by the service provider, a first address associated with the first client computing device;
• generate, by the service provider, an alternative identifier responsive to the first request for content from the first client computing device, the alternative identifier comprising a uniform resource locator (URL), the alternative identifier including information related to the first address associated with the first client computing device and additional information not included in the first request for content in a domain name service (DNS) portion of the URL, the additional information associated with routing or processing the request for content, and the additional information comprising timestamp information associated with a first time corresponding to the first request for content from the first client computing device;
• transmit, by the service provider, at least one instruction causing the first client computing device to generate a second request for content based on the alternative identifier;
• wherein the second request is associated with a second address corresponding to a DNS resolver component;
• receive, by the service provider at a DNS server component, the second request for content based on the alternative identifier, the second request comprising a DNS query;
• correlate, by the service provider at the DNS server component, the at least a portion of the first address associated with the first client computing device and the additional information included in the DNS portion of the URL with the second address and a second time corresponding to the second request for content for comparison with the first time corresponding to the first request for content to form correlated information;
• obtain, by the service provider, a second DNS query from a second client computing device;
• and
• responsive to the second DNS query, at the service provider:
• determine a class associated with the second client computing device based at least in part on the correlated information;
• and
• resolve the second DNS query based on the determined class.