Method, name server, and system for directing network traffic utilizing profile records

• US 9,634,935 B2
• Filed: 04/24/2013
• Issued: 04/25/2017
• Est. Priority Date: 04/24/2013
• Status: Active Grant

• Current Assignee: Secured Connectivity, LLC
• Original Assignee: Secured Connectivity, LLC
• Inventors: Pechersky, Leonid
• Primary Examiner(s): Dailey, Thomas
• Application Number:
  US13/869,562
• Publication Number:
  US 20140325045A1
• Time in Patent Office: 1,462 Days
• Field of Search: None
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00

Abstract

A server, intermediation server, system and a method for directing network traffic are provided. The name server and intermediation server each include a network interface configured to communicate with a network, a memory configured to store the profile record a processor in communication with the memory and the network interface. The name server is for returning an assigned query result to a originating computing device when a destination identifier is associated with the profile record. The intermediation server is for perform a routing operation based on the request. The system includes an originating computing device a name server and an intermediation server all connected to a network. The method involves receiving a profile record and destination identifier, determining an association of the between the profile record and identifier, and returning with an assigned query result or a default query result.

Claims

1. A name server for directing network traffic from an originating computing device to a destination computing device, the server comprising:

a network interface configured to communicate with a network;

a memory configured to store;

a profile record mapping a source identifier associated with the originating computing device and a first destination identifier associated with a first destination computing device to an assigned query result comprising an intermediation server identifier identifying an intermediation server, and

a default record mapping a second destination identifier associated with a second destination computing device to a default query result comprising an address identifying the second destination computing device; and

a processor in communication with the memory and the network interface, the processor configured to;

receive a message from the originating computing device, the message comprising the source identifier identifying the originating computing device and a destination identifier identifying a destination computing device;

search for the destination identifier in the memory to determine if the destination identifier is in the profile record;

in response to a determination that the destination identifier is in the profile record;

determine whether the destination identifier is the first destination identifier which is associated with the first destination computing device;

return the assigned query result comprising the intermediation server identifier to the originating computing device using the source identifier, the assigned query result comprising an instruction to cause the originating computing device to communicate with the first destination computing device through the intermediation server instead of directly with the first destination computing device; and

in response to a determination that the destination identifier is not in the profile record;

return the default query result to the originating computing device using the source identifier in response to a determination that the destination identifier is associated with the second destination computing device, the default query result comprising the second destination identifier causing the originating computing device to communicate directly with the second destination computing device without going through the intermediation server.

2. The name server of claim 1, wherein the processor is further configured to request the assigned query result from the intermediation server.

3. The name server of claim 1, wherein the destination identifier is a request for an intended numerical address.

4. The name server of claim 3, wherein the processor is further configured to identify the originating computing device.

16. The name server of claim 1, wherein the name server is configured to communicate with the network to receive the profile record.

17. The name server of claim 1, wherein the instruction in the assigned query comprises a domain name of the intermediation server.

18. The name server of claim 1, wherein the name server is further configured to operate as a domain name system (DNS) server.

5. A system comprising:

an originating computing device connected to a network;

a name server for directing network traffic from the originating computing device to a destination computing device, the name server comprising;

a network interface configured to communicate with the network;

a memory configured to store;

a profile record, the profile record mapping a source identifier associated with the originating computing device and a first destination identifier associated with a first destination computing device to an assigned query result comprising an intermediation server identifier identifying an intermediation server, and

a default record mapping a second destination identifier associated with a second destination computing device to a default query result comprising an address identifying the second destination computing device; and

a processor in communication with the memory and the network interface, the processor configured to;

receive a message from the originating computing device, the message comprising the source identifier identifying the originating computing device and a destination identifier identifying a destination computing device;

search for the destination identifier in the memory to determine if the destination identifier in the profile record;

in response to a determination that the destination identifier is in the profile record;

determine whether the destination identifier is the first destination identifier which is associated with the first destination computing device;

return the assigned query result comprising the intermediation server identifier to the originating computing device using the source identifier, the assigned query result comprising an instruction to cause the originating computing device to communicate with the first destination computing device through the intermediation server instead of directly with the first destination computing device; and

in response to a determination that the destination identifier is not in the profile record;

return the default query result to the originating computing device using the source identifier in response to a determination that the destination identifier is associated with the second destination computing device, the default query result comprising the second destination identifier causing the originating computing device to communicate directly with the second destination computing device without going through the intermediation server.

19. The system of claim 5, wherein the intermediation server and the name server operate from the same computing device.

6. A method of directing network traffic, the method comprising:

receiving, at a name server, a message from an originating computing device, the message comprising a source identifier associated with the originating computing device and a destination identifier associated with a destination computing device;

searching, at the name server, for the destination identifier in the memory to determine, if the destination identifier is in a profile record, the profile record mapping the source identifier and the destination identifier to an assigned query result comprising an intermediation server identifying an intermediation server;

in response to a determination that the destination identifier is in the profile record;

returning, from the name server, the assigned query result comprising the intermediation server identifier to the originating computing device using the source identifier, the assigned query result comprising an instruction to cause the originating computing device to communicate with the destination computing device through the intermediation server instead of directly with the destination computing device; and

in response to a determination that the destination identifier is not in the profile record;

returning, from the name server, a default query result to the originating computing device using the source identifier, wherein the default query result comprises an address which identifies the destination computing device and comprises an instruction to cause the originating computing device to communicate directly with the destination computing device without going through the intermediation server.

7. The method of claim 6, wherein the name server requests the assigned query result from the intermediation server.

8. The method of claim 6, wherein the destination identifier is a request for an intended numerical address.

9. The method of claim 8, further comprising identifying, at the intermediation server, the originating computing device.

10. The method of claim 9, further comprising determining, at the intermediation server, a routing operation based on the originating computing device.

11. The method of claim 10, further comprising routing traffic in accordance with the routing operation.

12. The method of claim 11, wherein the routing operation involves blocking traffic between the originating computing device and the destination computing device.

13. The method of claim 11, wherein the routing operation involves providing, from the intermediation server to the originating computing device, a notification interrupt for inserting a notification page.

14. The method of claim 11, wherein the routing operation involves anonymizing the originating computing device.

15. A non-transitory computer readable medium comprising computer-executable instructions stored thereon that, when executed by a processor, cause the processor to:

receive a profile record for an originating computing device, the profile record mapping a source identifier associated with the originating computing device and a destination identifier associated with the destination computing device to an assigned query result comprising an intermediation server identifier identifying an intermediation server;

receive a message from the originating computing device, the message comprising the source identifier and the destination identifier;

search for the destination identifier to determine if the destination identifier is in the profile record;

return an assigned query result to the originating computing device in response to a determination that the destination identifier is in the profile record, the assigned query result comprising an instruction to cause the originating computing device to communicate with the destination computing device through the intermediation server instead of directly with the destination computing device; and

return a default query result to the originating computing device in response to a determination that the destination identifier is not in the profile record, wherein the default query result comprises an address which identifies the destination computing device and comprises an instruction to cause the originating computing device to communicate direct with the destination computing device without going through the intermediation server.