Registration Server for DNS-Free Hostname Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for resolving hostnames in network testing environments, especially those involving firewalls, NATs, or clouds, are hindered by the absence of DNS infrastructure and the complexity of mapping hostnames to IP addresses, particularly in private networks and clouds.

Innovation Solution

A registration server operating in a public network receives packets with hostname and IP address information, initiates connections, and associates hostnames with IP addresses based on connection success, enabling hostname resolution independent of DNS servers and external tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DNS infrastructure is used to resolve hostnames, then hostname resolution can be achieved in public networks, but it becomes inapplicable in private networks and cloud environments where DNS is not deployed

Engineering Contradiction:
Improvehostname resolution capabilityVSAvoiddependency on DNS infrastructure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a registration server as an intermediary component that maintains hostname-to-IP mappings. Instead of relying on DNS infrastructure, the registration server receives hostname registration requests from endpoints and stores these mappings in a database, enabling hostname resolution in environments without DNS support

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the hostname resolution function from the DNS infrastructure and implements it as a standalone registration server system. This allows hostname resolution to be performed independently of DNS, making it applicable in private networks and cloud environments where DNS is not deployed

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If IP addresses are used to identify hosts, then routing is straightforward, but network configuration changes require manual updates and reduce flexibility

Engineering Contradiction:
Improvehost identification flexibilityVSAvoidrouting stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates a mapping copy between hostnames and IP addresses in the registration server's database. This allows the system to work with flexible hostname identifiers while maintaining reliable routing by storing the corresponding IP address mappings, enabling automatic updates when IP addresses change

Inventive Principle:
Principle #26Copying

3Productivity

If conventional hostname resolution methods are used, then DNS queries can resolve hostnames, but additional external tools are needed in cloud environments and private networks

Engineering Contradiction:
Improvehostname resolution efficiencyVSAvoidnumber of external tools required
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent combines hostname registration, storage, and resolution functionality into a single registration server system. This integrated approach eliminates the need for separate external tools in cloud and private network environments, improving productivity by providing all hostname resolution capabilities within one system

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3219087B1Methods, systems, and computer readable media for facilitating the resolving of endpoint hostnames in test environments with firewalls, network address translators(NATS), or clouds
Publication Date: 2020.07.08 KEYSIGHT TECH SINGAPORE (SALES) PTE LTD
  • EP3219087B1 patent drawingFigure 1
  • EP3219087B1 patent drawingFigure 2
  • EP3219087B1 patent drawingFigure 3

AI summary

Methods, systems, and computer readable media for facilitating the resolving of endpoint hostnames in test environments with firewalls, network address translators (NATs), or clouds is disclosed. According to one exemplary method, the method occurs at a registration server configured to operate in a public network. The method includes receiving, from a first endpoint, a packet including a payload containing a first address and a hostname associated with the first endpoint. The method also includes identifying a second address from a header of the packet. The method also includes initiating, using the second address, a connection to the first endpoint. The method also includes determining whether the connection is successful. The method further includes associating the hostname of the first endpoint with one of the first address and the second address based on results of the determination.