Manage encrypted network traffic using DNS responses

A system comprising:

• memory for storing data;
• and
• one or more processors operable to perform operations comprising:
• requesting, by a first server, an address associated with a particular domain name from a resolution server, the particular domain name included in a predetermined set of domain names for which secure requests are to be identified;
• receiving, by the first server, a response from the resolution server including a plurality of addresses associated with the particular domain name;
• determining, by the first server, a single address from the plurality of addresses based on the single address not being previously assigned with any domain name by the first server;
• assigning, by the first server, the single address selected from the received plurality of addresses to the particular domain name, wherein the first server is configured to each of the plurality of addresses to at most one domain name;
• receiving, by the first server, a request to resolve the particular domain name from a client device;
• sending, by the first server, a response to the request to resolve the particular domain name to the client device, the sent response including the single address assigned to the particular domain name;
• receiving, by a second server associated with the single address, an encrypted request for a resource from the client device, the encrypted request directed to the single address assigned to the particular domain name, wherein the second server is different than the first server;
• and
• determining, by the second server, that encrypted request is directed to the particular domain name based on the assignment of the single address to the particular domain name.

A non-transitory, computer-readable medium encoded with instructions that, when executed, cause one or more processors to perform operations comprising:

• requesting, by a first server, an address associated with a particular domain name from a resolution server, the particular domain name included in a predetermined set of domain names for which secure requests are to be identified;
• receiving, by the first server, a response from the resolution server including a plurality of addresses associated with the particular domain name;
• determining, by the first server, a single address from the plurality of addresses based on the single address not being previously assigned with any domain name by the first server;
• assigning, by the first server, the single address selected from the received plurality of addresses to the particular domain name, wherein the first server is configured to each of the plurality of addresses to at most one domain name;
• receiving, by the first server, a request to resolve the particular domain name from a client device;
• sending, by the first server, a response to the request to resolve the particular domain name to the client device, the sent response including the single address assigned to the particular domain name;
• receiving, by a second server associated with the single address, an encrypted request for a resource from the client device, the encrypted request directed to the single address assigned to the particular domain name, wherein the second server is different than the first server;
• and
• determining, by the second server, that encrypted request is directed to the particular domain name based on the assignment of the single address to the particular domain name.