IP Library Granted Patent US 10,305,800
Granted Patent B2
US 10,305,800 · App. 14/687,695 · Granted May 28, 2019

Preferential selection of IP protocol version with domain name matching on proxy servers

Inventors: Robert James Torres (New Market, MD); Nagesh Javali (Germantown, MD); Venkatasubramaniam Ganesan (Germantown, MD); Ganeshan Ramachandran (Frederick, MD); Mark Petronic (Gaithersburg, MD)
Assignee: HUGHES NETWORK SYSTEMS, LLC
H04L45/741H04B7/2126H04L41/12H04L61/1511H04L67/2842H04L61/6013H04L61/6059H04L61/6068
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,305,800
App. No.
14/687,695
Granted
May 28, 2019
Kind
B2
Abstract

Systems and methods for the preferential selection or blocking of Internet Protocol (IP) version addresses, e.g., IPv4 and IPv6 addresses, are provided. During a process where address or domain name resolution is performed, an entity may access a domain bypass list to ascertain whether or not to proceed with requests utilizing an IPv4 address, an IPv6 address, or neither. Such a list may be dynamically or manually created and/or updated such that known issues associated with the use of a particular type of IP version address can be avoided for subsequent resolution requests to access network resources such as web pages, DNS entries, etc.

Claims (40)

1. A method, comprising;

a proxy server receiving a domain name service (DNS) request for a domain; the proxy server determining whether the domain matches an entry stored within a domain bypass list, the domain list comprising a list of preferred Internet Protocol (IP) version to domain name mappings;

upon a determination that the domain does not match at least one entry stored within the domain bypass list, looking up the domain in a cache of the proxy server; and

upon a determination that the domain does match at least one entry stored within the domain bypass list, determining whether to allow or block one or more types of traffic based upon a preferentially selected IP version, the preferentially selected IP version comprising at least one of an IPv4 address and an IPv6 address.

2. The method of claim 1 , wherein the proxy server comprises a DNS proxy server implemented within a very small aperture terminal (VSAT) of a broadband satellite network.

3. The method of claim 1 , wherein the proxy server comprises a web acceleration server implemented within a gateway of a broadband satellite network.

4. The method of claim 1 , further comprising, upon looking up the domain in the cache of the proxy server, responding to a requesting device with a DNS answer record if the domain is found in the cache of the proxy server.

5. The method of claim 4 , wherein the DNS answer record comprises a single-A DNS record if the DNS request is a single-A DNS request.

6. The method of claim 4 , wherein the DNS answer record comprises a quad-A DNS record if the DNS request is a quad-A DNS request.

7. The method of claim 1 , further comprising, upon looking up the domain in the cache of the proxy server, forwarding a single-A and a quad-A DNS request to one of a subsequent DNS server or DNS server list if the domain is not found in the cache of the proxy server.

8. The method of claim 1 , wherein determining whether to allow or block one or more types of traffic based upon a preferentially selected Internet Protocol (IP) version further comprises one of blocking 1 Pv4 traffic while allowing IPv6 traffic, allowing IPv4 traffic while blocking IPv6 traffic, or blocking both IPv4 and IPv6 traffic.

9. The method of claim 8 , further comprising, upon determining to block IPv4 traffic while allowing IPv6 traffic, sending an error message to a requesting device if the DNS request is a single-A DNS request, and forwarding a quad-A DNS request to one of a subsequent DNS server or a DNS server list.

10. The method of claim 8 , further comprising, upon determining to allow IPv4 traffic while blocking IPv6 traffic, looking up the domain in a cache of the proxy server if the DNS request is a single-A DNS request, and determining if the domain matches an entry in the cache of the proxy server.

11. The method of claim 10 , further comprising, upon a determination that the domain matches an entry in the cache of the proxy server, responding to a requesting device with a Single-A DNS answer record.

12. The method of claim 10 , further comprising, upon a determination that the domain does not match an entry in the cache of the proxy server, forwarding a single-A DNS request to one of a subsequent DNS server or a DNS server list.

13. The method of claim 8 , further comprising, upon determining to block both IPv4 traffic and IPv6 traffic, sending an error message to a requesting device.

14. The method of claim 8 , further comprising, upon determining to block IPv4 traffic while allowing IPv6 traffic, looking up the domain in a cache of the proxy server if the DNS request is a quad-A DNS request, and determining if the domain matches an entry in the cache of the proxy server.

15. The method of claim 14 , further comprising, upon a determination that the domain matches an entry in the cache of the proxy server, responding to a requesting device with a quad-A DNS answer record.

16. The method of claim 14 , further comprising, upon a determination that the domain does not match an entry in the cache of the proxy server, forwarding a quad-A DNS request to one of a subsequent DNS server or a DNS server list.

17. The method of claim 8 , further comprising, upon determining to allow IPv4 traffic while blocking IPv6 traffic, sending an error message to a requesting device if the DNS request is a quad-A DNS request, and forwarding a single-A DNS request to one of a subsequent DNS server or a DNS server list.

18. The method of claim 1 , wherein determining whether the domain matches an entry stored within a domain bypass list comprises one of finding a first entry and ending the determination or finding any entry having a matching domain.

19. The method of claim 1 , wherein the domain bypass list is at least one of created, updated, and maintained dynamically and automatically based on monitoring of the one or more types of traffic.

20. A very small aperture terminal (VSAT) of a satellite network, comprising:

a domain name service (DNS) proxy server for receiving a DNS request for a domain from a requesting device;

a DNS proxy server cache, wherein the DNS proxy server determines whether the domain matches an entry stored within a domain bypass list, the domain list comprising a list of preferred Internet Protocol (IP) version to domain name mappings;

at least one processor; and

at least one memory unit storing program instructions adapted to cause the at least processor to:

upon a determination that the domain does not match at least one entry stored within the domain bypass list, look up the domain in the DNS proxy server cache; and

upon a determination that the domain does match at least one entry stored within the domain bypass list, determine whether to allow or block one or more types of traffic based upon a preferentially selected IP version, the preferentially selected IP version comprising at least one of an IPv4 address and an IPv6 address.

21. The VSAT of claim 20 , wherein the preferentially selected IP version comprises one of IPv4 or IPv6.

22. The VSAT of claim 21 , wherein determining whether to allow or block one or more types of traffic comprises one of blocking IPv4 traffic while allowing IPv6 traffic, allowing IPv4 traffic while blocking IPv6 traffic, or blocking both IPv4 and IPv6 traffic.

23. A satellite gateway, comprising:

a web acceleration server for receiving a request from a requesting device;

a cache, wherein the web acceleration server determines whether a domain matches an entry stored within a domain bypass list in relation to the request, the domain list comprising a list of preferred Internet Protocol (IP) version to domain name mappings;

at least one processor; and

at least one memory unit storing program instructions adapted to cause the at least processor to:

upon a determination that the domain does not match at least one entry stored within the domain bypass list, look up the domain in the cache; and

upon a determination that the domain does match at least one entry stored within the domain bypass list, determine whether to allow or block one or more types of traffic based upon a preferentially selected IP version, the preferentially selected IP version comprising at least one of an IPv4 address and an IPv6 address.

24. The satellite gateway of claim 23 , wherein the preferentially selected IP version comprises one of IPv4 or IPv6.

25. The satellite gateway of claim 24 , wherein determining whether to allow or block one or more types of traffic comprises one of blocking IPv4 traffic while allowing IPv6 traffic, allowing IPv4 traffic while blocking IPv6 traffic, or blocking both IPv4 and IPv6 traffic.

Assignments (5)
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE APPLICATION NUMBER 15649418 PREVIOUSLY RECORDED ON REEL 050600 FRAME 0314. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF PATENT SECURITY AGREEMENTS. Recorded Sep 3, 2020
From: WELLS FARGO, NATIONAL BANK ASSOCIATION
To: U.S. BANK NATIONAL ASSOCIATION
Reel/Frame 053703/0367 →
ASSIGNMENT OF PATENT SECURITY AGREEMENTS Recorded Oct 1, 2019
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: U.S. BANK NATIONAL ASSOCIATION
Reel/Frame 050600/0314 →
SECURITY INTEREST Recorded Aug 5, 2019
From: HUGHES NETWORK SYSTEMS, LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION - AS COLLATERAL AGENT
Reel/Frame 049953/0714 →
SECURITY INTEREST Recorded Feb 13, 2017
From: HUGHES NETWORK SYSTEMS, LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION - AS TRUSTEE AND COLLATERAL AGENT
Reel/Frame 041695/0966 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2016
From: TORRES, ROBERT JAMES; JAVALI, NAGESH; GANESAN, VENKATASUBRAMANIAM; RAMACHANDRAN, GANESHAN; PETRONIC, MARK
To: HUGHES NETWORK SYSTEMS, LLC
Reel/Frame 037954/0854 →
Continuity (1)
Related Publication 20160308818A1 · Oct 20, 2016
Cited By (1)
US 12,457,191