Split-DNS Gateway Resolving Multi-Network Host Names

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Clients configured to send initial DNS lookup requests to a single DNS server face challenges when simultaneously connected to multiple private networks, as they may not be able to resolve host names across both networks due to security restrictions and overlapping private address assignments, leading to unresolved DNS queries.

Innovation Solution

Implementing an internal DNS server that can resolve host names for both internal and local networks, providing DNS referrals to allow clients to send all initial DNS lookup requests to this server, enabling communication with hosts across both networks while maintaining security by dynamically updating mappings and using reverse DNS lookups to determine appropriate DNS server addresses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If clients send initial DNS lookup requests to a single DNS server, then the configuration is simple, but clients cannot resolve host names across multiple private networks due to security restrictions and overlapping address assignments

Engineering Contradiction:
ImproveDNS configuration simplicityVSAvoidMulti-network host name resolution capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a gateway device as an intermediary between clients and DNS servers. The gateway receives DNS lookup requests from clients, determines whether the requested host is local or remote, and forwards requests to appropriate DNS servers. This mediator resolves the contradiction by enabling multi-network resolution without requiring complex client-side configuration, as the gateway handles the complexity of selecting appropriate DNS servers based on network context.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the DNS resolution process into two distinct phases: local DNS resolution for hosts within the same private network, and remote DNS resolution for hosts in other networks. The gateway implements this segmentation by examining the requested host name, determining the appropriate DNS server based on network boundaries, and directing queries accordingly. This segmentation allows the system to maintain simple client configuration while achieving versatile multi-network resolution.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If a single DNS server is used for all networks, then the device complexity is reduced, but security restrictions prevent proper host name resolution across networks with overlapping addresses

Engineering Contradiction:
ImproveDNS server structureVSAvoidHost name resolution accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The gateway acts as a mediator that maintains simple DNS server structures while ensuring reliable resolution. It receives queries from clients, determines the appropriate DNS server based on the requested host and network context, and forwards queries accordingly. This approach preserves the simplicity of individual DNS servers while achieving reliable cross-network resolution through intelligent query routing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically selects which DNS server to query based on the requested host name and current network context. The gateway implements dynamic behavior by examining each DNS lookup request, determining whether the host is local or remote, and adapting the query path accordingly. This dynamic approach allows the system to maintain simple static DNS server configurations while achieving reliable resolution for both local and remote hosts.

Inventive Principle:
Principle #15Dynamics

3Stability of the object's composition

If DNS servers maintain static mappings, then the configuration is stable, but dynamic network changes require manual updates to maintain security and proper routing

Engineering Contradiction:
ImproveDNS mapping stabilityVSAvoidManual configuration effort
Core Design Contradiction:
Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The gateway implements feedback mechanisms by monitoring network changes and dynamically adjusting DNS query routing accordingly. When network topology changes or new hosts are added, the gateway detects these changes and adapts its resolution logic automatically. This feedback approach maintains stable DNS server configurations while eliminating the need for manual updates, as the system self-adjusts to network changes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The DNS resolution system performs self-service by automatically adapting to network changes without requiring manual configuration. The gateway autonomously determines appropriate DNS servers based on current network state and requested hosts, eliminating the need for administrators to manually update DNS mappings. This self-service capability maintains configuration stability while reducing manual effort.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8788708B2Split-domain name service
Publication Date: 2014.07.22 CA TECH INC
  • US8788708B2 patent drawing
  • US8788708B2 patent drawing
  • US8788708B2 patent drawing

AI summary

In one embodiment, a method includes receiving an address of a DNS server of a network. A secure communication tunnel is established with a client of the network. The client is notified that requests to the address of the DNS server of the network should not pass through the secure communication tunnel. A request for a DNS lookup of a name of a host of the network is received through the secure communication tunnel. A DNS referral that includes the address of the DNS server of the network is sent to the client.