Methods, systems, and computer readable media for facilitating the resolving of endpoint hostnames in test environments with firewalls, network address translators (NATs), or clouds

Patent metadata

Field	Value
Publication number	US-9769291-B2
Application number	US-201514619041-A
Country	US
Kind code	B2
Filing date	Feb 10, 2015
Priority date	Feb 9, 2015
Publication date	Sep 19, 2017
Grant date	Sep 19, 2017

Abstract

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.

First claim

What is claimed is:

1. A method for facilitating the resolving of a hostname of an endpoint, the method comprising:
at a registration server including at least one processor, the registration server configured to operate in a public network:
receiving, from a first endpoint, a packet including a payload containing a first address and a hostname associated with the first endpoint;
identifying a second address from a header of the packet;
initiating, using the second address, a connection to the first endpoint;
determining whether the connection is successful;
associating the hostname of the first endpoint with one of the first address and the second address based on results of the determination;
at a requesting entity separate from the first and second endpoints and the registration server:
transmitting a request message to the registration server to resolve the hostname of the first endpoint and the hostname of a second endpoint;
receiving a response from the registration server that includes an indication that the first endpoint is located in a public or semi-public network and an indication that the second endpoint is in a private network; and
preventing a test connection attempt from the first endpoint to the second endpoint by instructing the second endpoint to initiate a test connection with the first endpoint without instructing the first endpoint to initiate a connection with the second endpoint; and

transmitting test packets between the first and second endpoints over the test connection.

2. The method of claim 1 , comprising comparing the first address to the second address if the connection to the first endpoint is successful.

3. The method of claim 2 , wherein if the first address and the second address are different, then associating the hostname of the first endpoint with one of the first address and the second address comprises associating the hostname of the first endpoint with the second address.

4. The method of claim 2 , wherein if the first address and the second address are identical, then associating the hostname of the first endpoint with one of the first address and the second address comprises associating the hostname of the first endpoint with either one of the first address or the second address.

5. The method of claim 1 , wherein, if the connection to the first endpoint is unsuccessful, then associating the hostname of the first endpoint with one of the first address and the second address comprises associating the hostname of the first endpoint with the first address.

6. The method of claim 1 , comprising, at the registration server, storing the hostname of the first endpoint, a network location of a machine hosting the first endpoint, and the address associated with the hostname of the first endpoint.

7. The method of claim 1 , wherein the first address contained in the payload of the packet comprises an Internet protocol (IP) address inserted by the first endpoint into an IP payload of the packet, and wherein the second address identified from the header of the packet comprises a source IP address either inserted by the first endpoint or by a network address translator (NAT) into an IP header of the packet.

8. The method of claim 7 , comprising extracting the IP address and the hostname associated with the first endpoint from the IP payload of the packet.

9. A system for facilitating the resolving of a hostname of an endpoint, the system comprising:
at least one processor;
a registration server implemented by the at least one processor, the registration server configured to operate in a public network, wherein the registration server is configured to:
receive, from a first endpoint, a packet including a payload containing a first address and a hostname associated with the first endpoint,
identify a second address from a header of the packet,
initiate, using the second address, a connection to the first endpoint,
determine whether the connection is successful, and
associate the hostname of the first endpoint with one of the first address and the second address based on results of the determination;

a requesting entity separate from the first and second endpoints and the registration server and configured to:
transmit a request message to the registration server to resolve the hostname of the first endpoint and the hostname of a second endpoint;
receive a response from the registration server that includes an indication that the first endpoint is located in a public or semi-public network and an indication that the second endpoint is in a private network; and
prevent a test connection attempt from the first endpoint to the second endpoint by instructing the second endpoint to initiate a test connection with the first endpoint without instructing the first endpoint to initiate a connection with the second endpoint; and

wherein the first and second endpoints exchange test packets over the test connection.

10. The system of claim 9 , wherein the registration server is configured to compare the first address to the second address if the connection to the first endpoint is successful.

11. The system of claim 10 , wherein if the first address and the second address are different, then the registration server is configured to associate the hostname of the first endpoint with the second address.

12. The system of claim 10 , wherein if the first address and the second address are identical, then the registration server is configured to associate the hostname of the first endpoint with either one of the first address or the second address.

13. The system of claim 9 , wherein if the connection to the first endpoint is unsuccessful, then the registration server is configured to associate the hostname of the first endpoint with the first address.

14. The system of claim 9 , wherein the registration server is configured to store the hostname of the first endpoint, a network location of a machine hosting the first endpoint, and the address associated with the hostname of the first endpoint.

15. The system of claim 9 , wherein the first address contained in the payload of the packet comprises an Internet protocol (IP) address inserted by the first endpoint into an IP payload of the packet, and wherein the second address identified from the header of the packet comprises a source IP address either inserted by the first endpoint or by a network address translator (NAT) into an IP header of the packet.

16. The system of claim 15 , wherein the registration server is configured to extract the IP address and the hostname associated with the first endpoint from the IP payload of the packet.

17. A non-transitory computer readable medium comprising computer executable instructions embodied in the computer readable medium that when executed by a processor of a computer perform steps comprising:
at a registration server including at least one processor, the registration server configured to operate in a public network:
receiving, from a first endpoint, a packet including a payload containing a first address and a hostname associated with the first endpoint;
identifying a second address from a header of the packet;
initiating, using the second address, a connection to the first endpoint;
determining whether the connection is successful; and
associating the hostname of the first endpoint with one of the first address and the second address based on results of the determination
at a requesting entity separate from the first and second endpoints and the registration server:
transmitting a request message to the registration server to resolve the

Assignees

• Ixia

Inventors

• Nistor Marius Pavel
• Constantinescu Mihail Florin
• Ribault Nicolas

Classifications

• H04L61/2567

  for reachability, e.g. inquiring the address of a correspondent behind a NAT server · CPC title

• H04L61/15

  Electricity · mapped topic

• H04L61/2514

  between local and global IP addresses · CPC title

• H04L69/22 Primary

  Parsing or analysis of headers · CPC title

• H04L61/5076

  Update or notification mechanisms, e.g. DynDNS · CPC title