Stenographic marking using network addressing
Abstract
Systems, methods, apparatuses, and software for a content delivery network that caches content for delivery to end user devices is presented. In one example, a method includes establishing address translations which translate domain names into network addresses usable by the end user devices for reaching content at the cache nodes, with portions of the network addresses comprising stenographic information, and responsive to domain name translation requests from the end user devices, providing ones of the network addresses. The method includes receiving content requests transferred by the end user devices that comprise the network addresses, and performing one or more actions based on the stenographic information in the network addresses.
Claims
exact text as granted — not AI-modified1 - 20 . (canceled)
21 . A method of operating a communication network, comprising:
receiving a first domain name system (DNS) translation request; identifying locality information related to a source of the first DNS request; responsive to the first DNS translation request, providing a first Internet Protocol (IP) address, the first IP address configured to:
route network traffic to a cache node; and
convey the locality information to the cache node;
receiving a second DNS translation request; and responsive to the second DNS request, providing a second IP address, wherein the second IP address is configured to route network traffic to the cache node and the second IP address is distinct from the first IP address.
22 . The method of claim 21 , wherein the first IP address is further configured to convey to the cache node a function to be executed by the cache node responsive to receiving a content request containing the first IP address.
23 . The method of claim 22 , wherein the function to be executed by the cache node is a traffic handling function.
24 . The method of claim 22 , wherein the function to be executed by the cache node is a logging function.
25 . The method of claim 22 , wherein the function to be executed by the cache node is a traffic blocking function.
26 . The method of claim 21 , wherein the locality information comprises a geographical location of an end user that submitted the first DNS translation request.
27 . The method of claim 21 , wherein the locality information comprises identification of an Internet Service Provider that provided the first DNS translation request.
28 . The method of claim 21 , wherein the locality information comprises identification of a DNS server that processed the first DNS translation request.
29 . The method of claim 21 , wherein the first IP address is configured to convey the locality information to the cache node at least by comprising the locality information in an encrypted form.
30 . The method of claim 21 , wherein the locality information is associated with a network attack.
31 . A Domain Name System (DNS) node, comprising:
a processor; non-transitory computer-readable media; and software stored on the non-transitory computer-readable media, which, when executed by the processor, causes the DNS node to: receive a first DNS translation request; identify locality information related to a source of the first DNS request; responsive to the first DNS translation request, provide a first Internet Protocol (IP) address, the first IP address configured to:
route network traffic to a cache node; and
convey the locality information to the cache node;
receiving a second DNS translation request; and responsive to the second DNS request, provide a second IP address, wherein the second IP address is configured to route network traffic to the cache node and the second IP address is distinct from the first IP address.
32 . The DNS node of claim 31 , wherein the first IP address is further configured to convey to the cache node a function to be executed by the cache node responsive to receiving a content request containing the first IP address.
33 . The DNS node of claim 32 , wherein the function to be executed by the cache node is a traffic handling function.
34 . The DNS node of claim 32 , wherein the function to be executed by the cache node is a logging function.
35 . The DNS node of claim 32 , wherein the function to be executed by the cache node is a traffic blocking function.
36 . The DNS node of claim 31 , wherein the locality information comprises a geographical location of an end user that submitted the first DNS translation request.
37 . The DNS node of claim 31 , wherein the locality information comprises identification of an Internet Service Provider that provided the first DNS translation request.
38 . The DNS node of claim 31 , wherein the locality information comprises identification of a DNS server that processed the first DNS translation request.
39 . The DNS node of claim 31 , wherein the first IP address is configured to convey the locality information to the cache node at least by comprising the locality information in an encrypted form.
40 . The DNS node of claim 31 , wherein the locality information is associated with a network attack.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.