Proxy DNS Resolution for Satellite Link Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Satellite communications experience significant delays due to high latency in resolving domain name services (DNS) queries, which can be frustrating for users, especially when multiple messages are required to be sent across high-latency links.
Innovation Solution
A system where a placeholder address is generated in response to a DNS request, allowing subsequent connection requests to use this placeholder, which is then resolved by a hub server, reducing the need for separate DNS queries and responses across the network link.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If conventional DNS query method is used across satellite link, then DNS resolution can be completed, but significant delay of half second or more occurs due to round-trip transmission time
Solution Approach 1:
The system performs preliminary DNS resolution at the hub processor before the client needs the resolved address. The hub processor receives the client's IP address, queries the DNS server locally (without satellite transmission), obtains the resolved address, and caches it. When the client subsequently needs to connect to the domain, the pre-resolved address is already available at the hub, eliminating the need for round-trip DNS queries across the satellite link.
Solution Approach 2:
The hub processor acts as an intermediary between the client and the DNS server. Instead of the client directly querying the DNS server across the satellite link, the hub processor intercepts the client's connection requests, performs the DNS resolution locally using its own DNS server, and then establishes the connection using the resolved address. This intermediary approach eliminates satellite transmission delays for DNS queries.
2Reliability
If multiple messages are sent across satellite link for DNS resolution and connection establishment, then proper communication can be established, but user-perceived delay increases due to multiple round-trips
Solution Approach 1:
The system merges the DNS resolution process with the connection establishment process. Instead of separately sending a DNS query message and then a connection request message across the satellite link, the hub processor combines these functions by performing DNS resolution locally and directly using the resolved address to establish the connection. This merging reduces the number of separate message exchanges required across the high-latency satellite link.
Solution Approach 2:
The system extracts the DNS resolution function from the satellite communication path. By implementing a local DNS server at the hub processor and performing resolution there, the patent removes the DNS query and response messages from the satellite link transmission sequence. Only essential connection establishment messages need to cross the satellite link, reducing the total number of round-trips and improving user-perceived performance.
Data Source
AI summary
Systems and methods are provided for resolving domain name services (DNS) queries for address information about hosts on a network. The queries are posited from remote users across a satellite or other remote link to a network. In response to a domain name services request from the client containing a name of the server, a placeholder address is generated and provided in response to the client. After a subsequent request for a connection to the server is received, the name of the server is re-associated with the placeholder address and the connection request containing the proper host name is forwarded across the data link. A hub processor receives the request for connection, resolves the name of the server to an address on the network, and establishes a connection between the client and the server using the address on the network.