US20120311114A1 - Method and apparatus for detecting incorrect responses to network queries - Google Patents

Method and apparatus for detecting incorrect responses to network queries Download PDF

Info

Publication number
US20120311114A1
US20120311114A1 US13/590,477 US201213590477A US2012311114A1 US 20120311114 A1 US20120311114 A1 US 20120311114A1 US 201213590477 A US201213590477 A US 201213590477A US 2012311114 A1 US2012311114 A1 US 2012311114A1
Authority
US
United States
Prior art keywords
dns server
dns
query
functional limitation
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/590,477
Inventor
Stuart D. Cheshire
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority to US13/590,477 priority Critical patent/US20120311114A1/en
Publication of US20120311114A1 publication Critical patent/US20120311114A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]

Definitions

  • the present invention relates to techniques for detecting incorrect responses to network queries. More specifically, the present invention relates to a method and apparatus for using a test query to detect whether an Internet gateway device's configured domain-name system (DNS) server incorrectly responds to network queries.
  • DNS domain-name system
  • ISPs Internet Service Providers
  • IP Internet Protocol
  • NAT Network Address Translation
  • Internet gateway can include wired Internet gateways and wireless Internet gateways.
  • the Internet gateway can be implemented in a number of ways, including but not limited to: (1) a desktop or a laptop computer system coupled to the Internet, which is configured to share the Internet connection with devices on the LAN; or (2) a standalone device coupled to the Internet, which is configured to share the Internet connection with devices on the LAN.
  • the Internet gateway device typically has at least two physical interfaces and two Internet addresses: a public one that is used to communicate with the ISP's network, and a private internal one that is used to communicate with devices on the LAN. From the point of view of an outside observer, all the customer's local computers and other Internet-enabled devices are made to appear as a single device with a single public IP address.
  • the Internet gateway If the Internet gateway is configured to offer Dynamic Host Configuration Protocol (DHCP) service to the customer's devices, the Internet gateway usually assigns a private IP address to each Internet-enabled device coupled to the Internet gateway.
  • the Internet gateway also provides its own LAN IP address to these Internet-enabled devices as both the default gateway to which they should send outbound IP packets, and the default DNS server to which they should send DNS queries. Since usually the Internet gateway is not, itself, authoritative for any DNS domains, all it does with received DNS queries is forward them on to a more knowledgeable DNS server elsewhere, typically one operated by the customer's ISP.
  • DHCP Dynamic Host Configuration Protocol
  • a client device When communicating with services on the Internet, a client device sends IP packets via the Internet gateway.
  • the Internet gateway rewrites the source IP address in each packet to be the common shared public IP address, and then forwards it through the ISP's network to the Internet.
  • the Internet gateway typically keeps track of which packet was sent by which local Internet-enabled device, so that when response packet(s) return from the Internet via the ISP's network to the Internet gateway, the Internet gateway is able to route those response packets to the appropriate Internet-enabled device that originated the corresponding outgoing request packet.
  • FIG. 1 illustrates an Internet gateway 104 , which is coupled both to network 102 and local network 106 .
  • Local network 106 couples Internet gateway 104 with computers 108 , 110 , and 112 , and Ethernet device 114 .
  • Network 102 can generally include any type of wired or wireless communication channel capable of coupling together computing nodes. This includes, but is not limited to, a local area network, a wide area network, or a combination of networks, such as the Internet.
  • An Internet gateway typically includes a mechanism for forwarding DNS queries to DNS servers which can provide answers to the DNS queries. This mechanism allows Internet gateway 104 to function as the default “configured DNS server” for all devices on local network 106 .
  • a “configured DNS server” can include any DNS-enabled device which can return a response to a DNS query, such as (1) an authoritative DNS server, (2) a recursive DNS server, and (3) a forwarding DNS server.
  • An authoritative DNS server answers DNS queries directed to a domain or a set of domains that have been delegated to the authoritative DNS server. In doing so, the authoritative DNS server maintains DNS records for the delegated domain or set of domains, and is the only type of DNS server that can answer authoritatively for the delegated domain or set of domains.
  • a recursive DNS server receives DNS queries, and performs queries to lookup the requested domain.
  • the recursive DNS server caches the answer in its local DNS cache. If a query is made for a DNS record which was previously-cached in the local DNS cache, the recursive DNS server uses the cached information to answer the DNS query instead of performing another DNS query.
  • a forwarding DNS server (a DNS relay) forwards DNS queries to either a recursive DNS server or to an authoritative DNS server.
  • DNS relays typically contain simple DNS relays, which function as the “configured DNS server” for local devices that communicate through the Internet gateway.
  • Internet gateways are typically able to enable multiple Internet-enabled devices to share a single Internet connection successfully, some of these Internet gateways have functional limitations.
  • One such functional limitation causes the Internet gateway to incorrectly handle the forwarding of valid DNS queries to DNS servers.
  • functionally-limited Internet gateways can crash and completely cease functioning when processing certain valid DNS queries, thereby disrupting their ability to perform their intended function, namely providing Internet access to local computers and similar Internet-enabled devices.
  • One embodiment of the present invention provides a system that determines if a DNS server suffers from a particular known functional limitation.
  • the system sends an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a functional limitation in the DNS server without causing the DNS server to fail.
  • the system receives an answer to the exploratory query from the DNS server. If the DNS server gives an incorrect response, the system can take actions as may be desired for the implementation. For example, the system may display a message identifying the functional limitation, or the system may establish a mode of operation where it avoids performing those types of DNS queries known to present a risk of crashing the particular Internet gateway.
  • the system concludes that the DNS server does not have the functional limitation that the special query was constructed to detect.
  • the DNS server can include: a DNS server, a DNS cache, or a DNS relay.
  • the exploratory query is constructed so as to not cause the DNS server to communicate with a DNS root name server whether or not the functional limitation exists.
  • the special query is a “reverse-lookup” DNS query for a name that is a sub-domain of the “reverse-lookup” DNS name for the IP loopback address.
  • the exploratory query is for a name that should be known locally by the DNS server to have no records, without recourse to outside authority.
  • the format for the exploratory query is for the name “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
  • the system concludes that the DNS server does not have the functional limitation that the exploratory query was constructed to detect.
  • the remedial action involves disabling a networking feature in an application which would cause it to issue DNS queries that have the potential to crash the DNS server.
  • the networking feature is Wide Area Bonjour, which allows clients to discover network services on a network.
  • One embodiment of the present invention provides a computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for determining if a domain name system (DNS) server is functionally-limited.
  • DNS domain name system
  • the instructions When executed, the instructions cause the computer to send an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a functional limitation in the DNS server without causing the DNS server to crash or otherwise fail in a disruptive manner.
  • the instructions then configure the computer to receive an answer to the exploratory query from the DNS server. If the answer indicates that a functional limitation exists in the DNS server, the instructions cause the computer to perform a remedial action.
  • One embodiment of the present invention provides a method for determining if a domain name system (DNS) server is functionally-limited.
  • DNS domain name system
  • the method sends an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a flaw functional limitation in the DNS server without causing the DNS server to fail.
  • the method receives an answer to the exploratory query from the DNS server. If the answer indicates that a flaw functional limitation exists in the DNS server, the method performs a remedial action.
  • One embodiment of the present invention provides a system that tests a domain-name (DNS) server to determine if the DNS server exhibits a functional limitation.
  • DNS domain-name
  • the system transmits a test query to the DNS server, wherein the test query is constructed to prompt a first response if the functional limitation exists on the DNS server, and a second response if the functional limitation does not exist on said DNS server.
  • the system receives a response to the test query from the DNS server. The system then determines whether the functional limitation exists on the DNS server.
  • One embodiment of the present invention provides a system that evaluates the response of a local area network (LAN) domain-name server (DNS) coupled to a wide-area network (WAN) to a query of a type known to cause an undesired operation in some DNS servers.
  • the system transmits a test query from a client on the LAN to the LAN DNS server, wherein the query is constructed to generate a first response from the DNS server if the DNS server is of a configuration known to exhibit the undesired operation, and to generate a second response if the DNS server is not of a configuration known to exhibit the undesired response.
  • the system receives the response from the DNS server at a LAN client.
  • the system determines whether the DNS server is of a type known to exhibit the undesired operation. If so, the system performs a remedial action at the client in response to the determination.
  • FIG. 1 illustrates an Internet gateway coupled to a network.
  • FIG. 2 presents a flow chart illustrating the process of determining if a configured DNS server suffers from a particular known functional limitation in accordance with an embodiment of the present invention.
  • a computer-readable storage medium which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
  • Some configured DNS servers that reside within Internet gateways have functional limitations that can produce incorrect answers or can cause the Internet gateway to crash.
  • a configured DNS server can include any DNS-enabled device including a DNS server, a DNS relay, or a DNS cache.
  • Such functionally-limited configured DNS servers assume that if a client performs a PTR-type DNS query, the only possible request the client is making is to perform an IPv4 “reverse lookup” DNS query, translating from an IP address to a name.
  • IPv4 “reverse-lookup” domain name query is “2.1.168.192.in-addr.arpa.”
  • This query and ones like it may be performed by software, or by the user with a DNS utility such as “nslookup”.
  • the DNS query type is PTR and the DNS query is “2.1.168.192.in-addr.arpa.”
  • a PTR query is frequently a “reverse-lookup” DNS query, which performs a mapping from an IP address to a corresponding domain name.
  • the PTR-type DNS query “2.1.168.192.nonsense.” is a properly-formed DNS query, but does not yield any answer records since the top-level domain “nonsense” does not actually exist.
  • the domain “in-addr.arpa” is the proper domain suffix to use when performing a “reverse lookup” DNS query.
  • Some functionally-limited Internet gateways examine only the first four labels of the PTR-type DNS query (“labels” in a domain name are the groups of characters separated by periods) and ignore the remainder of the name. In the “2.1.168.192.nonsense.” example, the first four labels are “2.1.168.192.” Therefore, for these functionally-limited Internet gateways, the PTR-type DNS query “2.1.168.192.nonsense.” is indistinguishable from the PTR-type DNS query “2.1.168.192.in-addr.arpa.”
  • these same functionally-limited Internet gateways assume that the first four labels are decimal numbers between 0 and 255. If the first four labels of the PTR-type DNS query are not numbers between 0 and 255, these functionally-limited Internet gateways crash. Note that a crash of the Internet gateway can include, but is not limited to the Internet Gateway: failing completely; rebooting; ceasing to respond to network traffic; responding slowly to network traffic; and resetting the configuration of the Internet Gateway.
  • One embodiment of the present invention detects such functionally-limited Internet gateways by performing a special DNS query that is constructed to detect the existence of a functional limitation in the configured DNS server without crashing it.
  • the special query which detects a functional limitation in the Internet gateway's configured DNS server is the PTR-type DNS query “2.1.168.192.nonsense.”, which produces a NXDOMAIN answer (i.e. domain does not exist) in a properly functioning Internet gateway without the functional limitation.
  • PTR-type DNS query “2.1.168.192.nonsense.” which produces a NXDOMAIN answer (i.e. domain does not exist) in a properly functioning Internet gateway without the functional limitation.
  • they will attempt to give a host name in response to the 2.1.168.192.nonsense query, even though the query was not in fact an “in-addr.arpa” name lookup query.
  • the special query is constructed so that the configured DNS server does not communicate with a DNS root name server whether or not the functional limitation exists.
  • the special query can be “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
  • the address “127.0.0.1” is the “loopback address.”
  • the loopback address is a special IP address available for use when two pieces of network software on the same machine want to communicate with each other using IP networking mechanisms and programming interfaces, independent of whether conventional (inter-machine) IP networking is available.
  • every DNS server is supposed to contain a fixed DNS record which maps “1.0.0.127.in-addr.arpa.” to the name “localhost”.
  • any names that are sub-domains of the name “1.0.0.127.in-addr.arpa.” are properly-formed and valid, but are names that are known to have no associated DNS records.
  • “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.” is a legal name, but any queries for that name should yield no results. Therefore, an Internet gateway with a properly functioning configured DNS server returns an NXDOMAIN answer (i.e. domain name does not exist) without having to communicate with a DNS root name server to make that determination.
  • an Internet gateway with the functional limitation that the special query is constructed to detect does not communicate with a DNS root name server.
  • an Internet gateway with a functionally-limited configured DNS server only uses the first four labels of the PTR-type DNS query, and interprets this PTR-type DNS query as the PTR-type DNS query “1.0.0.127.in-addr.arpa.” Since the functionally-limited Internet gateway's configured DNS server knows that the correct answer for a PTR-type DNS query for “1.0.0.127.in-addr.arpa.” should be “localhost,” the Internet gateway returns the answer “localhost” without communicating with any DNS root name server.
  • the PTR-type DNS query string using the loopback address does not query the root DNS servers, it is preferable to use this query string format to detect the functional limitation in a DNS server.
  • other PTR-type DNS query strings not using the loopback address can also be used to detect the functional limitation in a DNS server.
  • FIG. 2 presents a flow chart illustrating the process of determining if a configured DNS server is functionally-limited in accordance with an embodiment of the present invention.
  • the process begins when the system sends a special query to the configured DNS server (step 202 ).
  • the special query is the PTR-type DNS query “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
  • the system receives an answer from the configured DNS server (step 204 ). If the answer is the correct response (step 206 —YES), the system concludes that the configured DNS server is not functionally-limited (step 212 ).
  • the correct response is an NXDOMAIN error code, which indicates that a domain name does not exist.
  • step 206 If the answer is incorrect (step 206 —NO), the system concludes that the configured DNS server is functionally-limited (step 208 ) and performs a remedial action (step 210 ).
  • the remedial action involves taking steps to avoid performing those certain valid DNS queries that are believed to have a high likelihood of crashing that particular device.
  • the valid DNS queries to be avoided are those used by Wide-Area Bonjour, a networking technology that allows clients to discover network services on a wide-area network.
  • a computer-readable storage medium which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
  • One embodiment of the present invention tests a domain-name (DNS) server to determine if the DNS server exhibits a functional limitation.
  • DNS domain-name
  • a test query is transmitted to the DNS server.
  • the test query is constructed to prompt a first response if the functional limitation exists on the DNS server, and a second response if the functional limitation does not exist on said DNS server.
  • a response to the test query is received from the DNS server.
  • a determination is made as to whether the functional limitation exists on the DNS server.
  • One embodiment of the present invention evaluates the response of a local area network (LAN) domain-name server (DNS) coupled to a wide-area network (WAN) to a query of a type known to cause an undesired operation in some DNS servers.
  • a test query is transmitted from a client on the LAN to the LAN DNS server.
  • the query is constructed to generate a first response from the DNS server if the DNS server is of a configuration known to exhibit the undesired operation, and to generate a second response if the DNS server is not of a configuration known to exhibit the undesired response.
  • the response from the DNS server is received at a LAN client.
  • a determination is made as to whether the DNS server is of a type known to exhibit the undesired operation. If so, a remedial action is performed at the client in response to the determination.

Abstract

A system that determines if a DNS server suffers from a particular known functional limitation. During operation, the system sends an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a functional limitation in the DNS server without causing the DNS server to fail. Next, the system receives an answer to the exploratory query from the DNS server. If the DNS server gives an incorrect response, the system can take actions as may be desired for the implementation. For example, the system may display a message identifying the functional limitation, or the system may establish a mode of operation where it avoids performing those types of DNS queries known to present a risk of crashing the particular Internet gateway.

Description

    RELATED APPLICATION
  • This application is a continuation of, and hereby claims priority under 35 U.S.C. §120 to, pending U.S. patent application Ser. No. 11/445,609, entitled “Method and Apparatus for Detecting Incorrect Responses to Network Queries,” by inventor Stuart D. Cheshire, filed on 02 Jun. 2006 (atty. docket no. APL-P3624US2), which is hereby incorporated by reference.
    • BACKGROUND Field of the Invention
  • The present invention relates to techniques for detecting incorrect responses to network queries. More specifically, the present invention relates to a method and apparatus for using a test query to detect whether an Internet gateway device's configured domain-name system (DNS) server incorrectly responds to network queries.
    • Related Art
  • Internet Service Providers (ISPs) typically provide a single Internet Protocol (IP) address per Internet connection account, which would conventionally imply that only one Internet-enabled device per account can be coupled to the ISP's network at any given time. This is unfortunate, given that today many households have multiple computers and other Internet-enabled devices that the customer may desire to have connected to the ISP's network concurrently.
  • A common solution to this Internet connection-sharing problem is to use a Network Address Translation (NAT) device (commonly called an “Internet gateway”) to share a single IP address with multiple Internet-enabled devices, which are coupled to the Internet gateway through a local area network (LAN). Note that an Internet gateway can include wired Internet gateways and wireless Internet gateways. Furthermore, note that the Internet gateway can be implemented in a number of ways, including but not limited to: (1) a desktop or a laptop computer system coupled to the Internet, which is configured to share the Internet connection with devices on the LAN; or (2) a standalone device coupled to the Internet, which is configured to share the Internet connection with devices on the LAN. The Internet gateway device typically has at least two physical interfaces and two Internet addresses: a public one that is used to communicate with the ISP's network, and a private internal one that is used to communicate with devices on the LAN. From the point of view of an outside observer, all the customer's local computers and other Internet-enabled devices are made to appear as a single device with a single public IP address.
  • If the Internet gateway is configured to offer Dynamic Host Configuration Protocol (DHCP) service to the customer's devices, the Internet gateway usually assigns a private IP address to each Internet-enabled device coupled to the Internet gateway. The Internet gateway also provides its own LAN IP address to these Internet-enabled devices as both the default gateway to which they should send outbound IP packets, and the default DNS server to which they should send DNS queries. Since usually the Internet gateway is not, itself, authoritative for any DNS domains, all it does with received DNS queries is forward them on to a more knowledgeable DNS server elsewhere, typically one operated by the customer's ISP.
  • When communicating with services on the Internet, a client device sends IP packets via the Internet gateway. The Internet gateway rewrites the source IP address in each packet to be the common shared public IP address, and then forwards it through the ISP's network to the Internet. During this process, the Internet gateway typically keeps track of which packet was sent by which local Internet-enabled device, so that when response packet(s) return from the Internet via the ISP's network to the Internet gateway, the Internet gateway is able to route those response packets to the appropriate Internet-enabled device that originated the corresponding outgoing request packet.
  • For example, FIG. 1 illustrates an Internet gateway 104, which is coupled both to network 102 and local network 106. Local network 106 couples Internet gateway 104 with computers 108, 110, and 112, and Ethernet device 114. Network 102 can generally include any type of wired or wireless communication channel capable of coupling together computing nodes. This includes, but is not limited to, a local area network, a wide area network, or a combination of networks, such as the Internet.
  • An Internet gateway (or any other Internet sharing device) such as Internet gateway 104, typically includes a mechanism for forwarding DNS queries to DNS servers which can provide answers to the DNS queries. This mechanism allows Internet gateway 104 to function as the default “configured DNS server” for all devices on local network 106.
  • Note that a “configured DNS server” can include any DNS-enabled device which can return a response to a DNS query, such as (1) an authoritative DNS server, (2) a recursive DNS server, and (3) a forwarding DNS server. An authoritative DNS server answers DNS queries directed to a domain or a set of domains that have been delegated to the authoritative DNS server. In doing so, the authoritative DNS server maintains DNS records for the delegated domain or set of domains, and is the only type of DNS server that can answer authoritatively for the delegated domain or set of domains.
  • A recursive DNS server (a DNS cache) receives DNS queries, and performs queries to lookup the requested domain. When an answer is received from an authoritative DNS server or from another recursive DNS server, the recursive DNS server caches the answer in its local DNS cache. If a query is made for a DNS record which was previously-cached in the local DNS cache, the recursive DNS server uses the cached information to answer the DNS query instead of performing another DNS query.
  • A forwarding DNS server (a DNS relay) forwards DNS queries to either a recursive DNS server or to an authoritative DNS server. As mentioned above, Internet gateways typically contain simple DNS relays, which function as the “configured DNS server” for local devices that communicate through the Internet gateway.
  • Although Internet gateways are typically able to enable multiple Internet-enabled devices to share a single Internet connection successfully, some of these Internet gateways have functional limitations. One such functional limitation causes the Internet gateway to incorrectly handle the forwarding of valid DNS queries to DNS servers. Furthermore, such functionally-limited Internet gateways can crash and completely cease functioning when processing certain valid DNS queries, thereby disrupting their ability to perform their intended function, namely providing Internet access to local computers and similar Internet-enabled devices.
  • Hence, what is needed is a method and an apparatus to determine if a configured DNS server suffers from this particular known functional limitation so that the client can determine when it should avoid performing those certain valid DNS queries that are known to have a high likelihood of crashing that particular device.
    • SUMMARY
  • One embodiment of the present invention provides a system that determines if a DNS server suffers from a particular known functional limitation. During operation, the system sends an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a functional limitation in the DNS server without causing the DNS server to fail. Next, the system receives an answer to the exploratory query from the DNS server. If the DNS server gives an incorrect response, the system can take actions as may be desired for the implementation. For example, the system may display a message identifying the functional limitation, or the system may establish a mode of operation where it avoids performing those types of DNS queries known to present a risk of crashing the particular Internet gateway.
  • In a variation on this embodiment, if the answer does not indicate that a functional limitation exists, the system concludes that the DNS server does not have the functional limitation that the special query was constructed to detect.
  • In a variation on this embodiment, the DNS server can include: a DNS server, a DNS cache, or a DNS relay.
  • In a further variation, the exploratory query is constructed so as to not cause the DNS server to communicate with a DNS root name server whether or not the functional limitation exists.
  • In a further variation, the special query is a “reverse-lookup” DNS query for a name that is a sub-domain of the “reverse-lookup” DNS name for the IP loopback address.
  • In a further variation, the exploratory query is for a name that should be known locally by the DNS server to have no records, without recourse to outside authority.
  • In a further variation, the format for the exploratory query is for the name “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
  • In a further variation, if the answer to the exploratory query indicates that a domain name specified in the exploratory query does not exist, the system concludes that the DNS server does not have the functional limitation that the exploratory query was constructed to detect.
  • In a variation on this embodiment, the remedial action involves disabling a networking feature in an application which would cause it to issue DNS queries that have the potential to crash the DNS server.
  • In a further variation, the networking feature is Wide Area Bonjour, which allows clients to discover network services on a network.
  • One embodiment of the present invention provides a computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for determining if a domain name system (DNS) server is functionally-limited. When executed, the instructions cause the computer to send an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a functional limitation in the DNS server without causing the DNS server to crash or otherwise fail in a disruptive manner. The instructions then configure the computer to receive an answer to the exploratory query from the DNS server. If the answer indicates that a functional limitation exists in the DNS server, the instructions cause the computer to perform a remedial action.
  • One embodiment of the present invention provides a method for determining if a domain name system (DNS) server is functionally-limited. During operation, the method sends an exploratory query to the DNS server, wherein the exploratory query is specially constructed so as to detect the existence of a flaw functional limitation in the DNS server without causing the DNS server to fail. Next, the method receives an answer to the exploratory query from the DNS server. If the answer indicates that a flaw functional limitation exists in the DNS server, the method performs a remedial action.
  • One embodiment of the present invention provides a system that tests a domain-name (DNS) server to determine if the DNS server exhibits a functional limitation. During operation, the system transmits a test query to the DNS server, wherein the test query is constructed to prompt a first response if the functional limitation exists on the DNS server, and a second response if the functional limitation does not exist on said DNS server. Next, the system receives a response to the test query from the DNS server. The system then determines whether the functional limitation exists on the DNS server.
  • One embodiment of the present invention provides a system that evaluates the response of a local area network (LAN) domain-name server (DNS) coupled to a wide-area network (WAN) to a query of a type known to cause an undesired operation in some DNS servers. During operation, the system transmits a test query from a client on the LAN to the LAN DNS server, wherein the query is constructed to generate a first response from the DNS server if the DNS server is of a configuration known to exhibit the undesired operation, and to generate a second response if the DNS server is not of a configuration known to exhibit the undesired response. Next, the system receives the response from the DNS server at a LAN client. The system then determines whether the DNS server is of a type known to exhibit the undesired operation. If so, the system performs a remedial action at the client in response to the determination.
    • BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 illustrates an Internet gateway coupled to a network.
  • FIG. 2 presents a flow chart illustrating the process of determining if a configured DNS server suffers from a particular known functional limitation in accordance with an embodiment of the present invention.
    •  DETAILED DESCRIPTION
  • The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
  • The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
    • Configured DNS Server Functional Limitation
  • Some configured DNS servers that reside within Internet gateways have functional limitations that can produce incorrect answers or can cause the Internet gateway to crash. (Note that a configured DNS server can include any DNS-enabled device including a DNS server, a DNS relay, or a DNS cache.) Such functionally-limited configured DNS servers assume that if a client performs a PTR-type DNS query, the only possible request the client is making is to perform an IPv4 “reverse lookup” DNS query, translating from an IP address to a name.
  • An example of a properly-formed IPv4 “reverse-lookup” domain name query is “2.1.168.192.in-addr.arpa.” This query and ones like it may be performed by software, or by the user with a DNS utility such as “nslookup”. The nslookup command and arguments for this example are: “nslookup−q=ptr 2.1.168.192.in-addr.arpa.” In this example, the DNS query type is PTR and the DNS query is “2.1.168.192.in-addr.arpa.” Note that a PTR query is frequently a “reverse-lookup” DNS query, which performs a mapping from an IP address to a corresponding domain name. However, other properly-formed DNS queries are possible even though they may not make any sense. For example, the PTR-type DNS query “2.1.168.192.nonsense.” is a properly-formed DNS query, but does not yield any answer records since the top-level domain “nonsense” does not actually exist. Note that the domain “in-addr.arpa” is the proper domain suffix to use when performing a “reverse lookup” DNS query.
  • Some functionally-limited Internet gateways examine only the first four labels of the PTR-type DNS query (“labels” in a domain name are the groups of characters separated by periods) and ignore the remainder of the name. In the “2.1.168.192.nonsense.” example, the first four labels are “2.1.168.192.” Therefore, for these functionally-limited Internet gateways, the PTR-type DNS query “2.1.168.192.nonsense.” is indistinguishable from the PTR-type DNS query “2.1.168.192.in-addr.arpa.”
  • Also note that these same functionally-limited Internet gateways assume that the first four labels are decimal numbers between 0 and 255. If the first four labels of the PTR-type DNS query are not numbers between 0 and 255, these functionally-limited Internet gateways crash. Note that a crash of the Internet gateway can include, but is not limited to the Internet Gateway: failing completely; rebooting; ceasing to respond to network traffic; responding slowly to network traffic; and resetting the configuration of the Internet Gateway.
    • Detecting a Functionally-Limited Internet Router
  • One embodiment of the present invention detects such functionally-limited Internet gateways by performing a special DNS query that is constructed to detect the existence of a functional limitation in the configured DNS server without crashing it.
  • For example, the special query which detects a functional limitation in the Internet gateway's configured DNS server is the PTR-type DNS query “2.1.168.192.nonsense.”, which produces a NXDOMAIN answer (i.e. domain does not exist) in a properly functioning Internet gateway without the functional limitation. However, in Internet gateways with functionally-limited configured DNS servers, they will attempt to give a host name in response to the 2.1.168.192.nonsense query, even though the query was not in fact an “in-addr.arpa” name lookup query.
  • Unfortunately, the PTR-type DNS query “2.1.168.192.nonsense”, when directed to a configured DNS server without the above-mentioned functional limitations, causes a DNS query to be sent to one of the DNS root name servers. Since in general the only way for a configured DNS server to know whether or not a particular top-level domain exists is to ask one of the root name servers, every such test query potentially results in a nuisance query being sent to the root name servers.
  • In one embodiment of the present invention, the special query is constructed so that the configured DNS server does not communicate with a DNS root name server whether or not the functional limitation exists.
  • For example, the special query can be “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.” In this exemplary query, the address “127.0.0.1” is the “loopback address.” The loopback address is a special IP address available for use when two pieces of network software on the same machine want to communicate with each other using IP networking mechanisms and programming interfaces, independent of whether conventional (inter-machine) IP networking is available.
  • Also note that every DNS server is supposed to contain a fixed DNS record which maps “1.0.0.127.in-addr.arpa.” to the name “localhost”. Hence, any names that are sub-domains of the name “1.0.0.127.in-addr.arpa.” are properly-formed and valid, but are names that are known to have no associated DNS records. In other words, “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.” is a legal name, but any queries for that name should yield no results. Therefore, an Internet gateway with a properly functioning configured DNS server returns an NXDOMAIN answer (i.e. domain name does not exist) without having to communicate with a DNS root name server to make that determination.
  • Note that since the last six labels in this PTR-type DNS query is “1.0.0.127.in-addr.arpa.”, an Internet gateway with a properly functioning configured DNS server will not forward the DNS query to the DNS root name server since the Internet gateway's configured DNS server knows that the IP address is a sub-domain of the loopback address. Since sub-domains of the loopback address are not used, the configured DNS server should respond with an NXDOMAIN answer without communicating with a DNS root name server.
  • Similarly, an Internet gateway with the functional limitation that the special query is constructed to detect does not communicate with a DNS root name server. Recall that an Internet gateway with a functionally-limited configured DNS server only uses the first four labels of the PTR-type DNS query, and interprets this PTR-type DNS query as the PTR-type DNS query “1.0.0.127.in-addr.arpa.” Since the functionally-limited Internet gateway's configured DNS server knows that the correct answer for a PTR-type DNS query for “1.0.0.127.in-addr.arpa.” should be “localhost,” the Internet gateway returns the answer “localhost” without communicating with any DNS root name server.
  • Note that since the PTR-type DNS query string using the loopback address does not query the root DNS servers, it is preferable to use this query string format to detect the functional limitation in a DNS server. However, other PTR-type DNS query strings not using the loopback address can also be used to detect the functional limitation in a DNS server.
  • FIG. 2 presents a flow chart illustrating the process of determining if a configured DNS server is functionally-limited in accordance with an embodiment of the present invention. The process begins when the system sends a special query to the configured DNS server (step 202). In one embodiment of the present invention, the special query is the PTR-type DNS query “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
  • Next the system receives an answer from the configured DNS server (step 204). If the answer is the correct response (step 206—YES), the system concludes that the configured DNS server is not functionally-limited (step 212). In one embodiment of the present invention, the correct response is an NXDOMAIN error code, which indicates that a domain name does not exist.
  • If the answer is incorrect (step 206—NO), the system concludes that the configured DNS server is functionally-limited (step 208) and performs a remedial action (step 210).
  • In one embodiment of the present invention, the remedial action involves taking steps to avoid performing those certain valid DNS queries that are believed to have a high likelihood of crashing that particular device.
  • In one embodiment of the present invention, the valid DNS queries to be avoided are those used by Wide-Area Bonjour, a networking technology that allows clients to discover network services on a wide-area network.
  • Note that the process described in FIG. 2 is stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs).
  • One embodiment of the present invention tests a domain-name (DNS) server to determine if the DNS server exhibits a functional limitation. A test query is transmitted to the DNS server. The test query is constructed to prompt a first response if the functional limitation exists on the DNS server, and a second response if the functional limitation does not exist on said DNS server. Next, a response to the test query is received from the DNS server. A determination is made as to whether the functional limitation exists on the DNS server.
  • One embodiment of the present invention evaluates the response of a local area network (LAN) domain-name server (DNS) coupled to a wide-area network (WAN) to a query of a type known to cause an undesired operation in some DNS servers. A test query is transmitted from a client on the LAN to the LAN DNS server. The query is constructed to generate a first response from the DNS server if the DNS server is of a configuration known to exhibit the undesired operation, and to generate a second response if the DNS server is not of a configuration known to exhibit the undesired response. Next, the response from the DNS server is received at a LAN client. A determination is made as to whether the DNS server is of a type known to exhibit the undesired operation. If so, a remedial action is performed at the client in response to the determination.
  • The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims (21)

1. A method for determining if a domain name system (DNS) server is functionally limited, comprising:
sending an exploratory query to the DNS server to detect a functional limitation in the DNS server, the functional limitation causing the DNS server to:
receive the exploratory query, which comprises receiving both a first portion and a second portion of the exploratory query; and
based on reading only the first portion of the exploratory query, send a response to the exploratory query;
receiving a response to the exploratory query from the DNS server; and
when the response indicates that the functional limitation exists in the DNS server, performing a remedial action.
2. The method of claim 1, wherein the exploratory query comprises “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
3. The method of claim 2, wherein the exploratory query is a “reverse lookup” DNS query that queries a PTR record.
4. The method of claim 1, wherein the exploratory query is configured to detect the functional limitation without at least one of:
causing the DNS server to fail; and
causing cause the DNS server to communicate with a DNS root name server.
5. The method of claim 1, wherein the method further comprises, when the response does not indicate that a functional limitation exists in the DNS server:
determining that the DNS server does not have the functional limitation; and
subsequently permitting the sending of DNS queries to the DNS server that the DNS server would not properly read if the DNS server had the functional limitation.
6. The method of claim 1, wherein the DNS server includes at least one of:
a DNS server;
a DNS cache; or
a DNS relay.
7. The method of claim 1, wherein the remedial action comprises:
subsequently avoiding sending DNS queries to the DNS server that the DNS server will not properly read due to the functional limitation.
8. A non-transitory computer-readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method for determining if a DNS server is functionally limited, the method comprising:
sending an exploratory query to the DNS server to detect a functional limitation in the DNS server, the functional limitation causing the DNS server to:
receive the exploratory query, which comprises receiving both a first portion and a second portion of the exploratory query; and
based on reading only the first portion of the exploratory query, send a response to the exploratory query;
receiving a response to the exploratory query from the DNS server; and
when the response indicates that the functional limitation exists in the DNS server, performing a remedial action.
9. The computer-readable storage medium of claim 8, wherein the exploratory query comprises “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
10. The computer-readable storage medium of claim 9, wherein the exploratory query is a “reverse lookup” DNS query that queries a PTR record.
11. The computer-readable storage medium of claim 8, wherein the exploratory query is configured to detect the functional limitation without at least one of:
causing the DNS server to fail; and
causing cause the DNS server to communicate with a DNS root name server.
12. The computer-readable storage medium of claim 8, wherein the method further comprises, when the response does not indicate that a functional limitation exists in the DNS server:
determining that the DNS server does not have the functional limitation; and
subsequently permitting the sending of DNS queries to the DNS server that the DNS server would not properly read if the DNS server had the functional limitation.
13. The computer-readable storage medium of claim 8, wherein the DNS server includes at least one of:
a DNS server;
a DNS cache; or
a DNS relay.
14. The computer-readable storage medium of claim 8, wherein the remedial action comprises:
subsequently avoiding sending DNS queries to the DNS server that the DNS server will not properly read due to the functional limitation.
15. An apparatus that determines if a DNS server is functionally limited, comprising:
a computer that performs operations for:
sending an exploratory query to the DNS server to detect a functional limitation in the DNS server, the functional limitation causing the DNS server to:
receive the exploratory query, which comprises receiving both a first portion and a second portion of the exploratory query; and
based on reading only the first portion of the exploratory query, send a response to the exploratory query;
receiving a response to the exploratory query from the DNS server; and
when the response indicates that the functional limitation exists in the DNS server, performing a remedial action.
16. The apparatus of claim 15, wherein the exploratory query comprises “1.0.0.127.dnsbugtest.1.0.0.127.in-addr.arpa.”
17. The apparatus of claim 16, wherein the exploratory query is a “reverse lookup” DNS query that queries a PTR record.
18. The apparatus of claim 15, wherein the exploratory query is configured to detect the functional limitation without at least one of:
causing the DNS server to fail; and
causing cause the DNS server to communicate with a DNS root name server.
19. The apparatus of claim 15, wherein the method further comprises, when the response does not indicate that a functional limitation exists in the DNS server:
determining that the DNS server does not have the functional limitation; and
subsequently permitting the sending of DNS queries to the DNS server that the DNS server would not properly read if the DNS server had the functional limitation.
20. The apparatus of claim 15, wherein the DNS server includes at least one of:
a DNS server;
a DNS cache; or
a DNS relay.
21. The apparatus of claim 15, wherein the remedial action comprises:
subsequently avoiding sending DNS queries to the DNS server that the DNS server will not properly read due to the functional limitation.
US13/590,477 2005-04-04 2012-08-21 Method and apparatus for detecting incorrect responses to network queries Abandoned US20120311114A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/590,477 US20120311114A1 (en) 2005-04-04 2012-08-21 Method and apparatus for detecting incorrect responses to network queries

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11/098,135 US7436783B2 (en) 2005-04-04 2005-04-04 Method and apparatus for detecting a router that improperly responds to ARP requests
US11/445,609 US8280991B2 (en) 2005-04-04 2006-06-02 Method and apparatus for detecting incorrect responses to network queries
US13/590,477 US20120311114A1 (en) 2005-04-04 2012-08-21 Method and apparatus for detecting incorrect responses to network queries

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/445,609 Continuation US8280991B2 (en) 2005-04-04 2006-06-02 Method and apparatus for detecting incorrect responses to network queries

Publications (1)

Publication Number Publication Date
US20120311114A1 true US20120311114A1 (en) 2012-12-06

Family

ID=36609229

Family Applications (4)

Application Number Title Priority Date Filing Date
US11/098,135 Active 2026-08-19 US7436783B2 (en) 2005-04-04 2005-04-04 Method and apparatus for detecting a router that improperly responds to ARP requests
US11/445,609 Active 2029-01-04 US8280991B2 (en) 2005-04-04 2006-06-02 Method and apparatus for detecting incorrect responses to network queries
US12/190,956 Active US7729292B2 (en) 2005-04-04 2008-08-13 Method and apparatus for detecting a router that improperly responds to ARP requests
US13/590,477 Abandoned US20120311114A1 (en) 2005-04-04 2012-08-21 Method and apparatus for detecting incorrect responses to network queries

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US11/098,135 Active 2026-08-19 US7436783B2 (en) 2005-04-04 2005-04-04 Method and apparatus for detecting a router that improperly responds to ARP requests
US11/445,609 Active 2029-01-04 US8280991B2 (en) 2005-04-04 2006-06-02 Method and apparatus for detecting incorrect responses to network queries
US12/190,956 Active US7729292B2 (en) 2005-04-04 2008-08-13 Method and apparatus for detecting a router that improperly responds to ARP requests

Country Status (8)

Country Link
US (4) US7436783B2 (en)
EP (2) EP2276223B1 (en)
AT (1) ATE493832T1 (en)
AU (1) AU2006232115C1 (en)
CA (1) CA2603571C (en)
DE (1) DE602006019218D1 (en)
HK (1) HK1113873A1 (en)
WO (1) WO2006108113A2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120110165A1 (en) * 2010-10-28 2012-05-03 Verisign, Inc. Evaluation of dns pre-registration data to predict future dns traffic
US20120113964A1 (en) * 2009-02-02 2012-05-10 Eloy Technology, Llc Remote participation in a local area network (lan) based media aggregation network
US20150067114A1 (en) * 2013-08-29 2015-03-05 MasterCard International Incoirporated Systems and methods for resolving data inconsistencies between domain name systems

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8676922B1 (en) 2004-06-30 2014-03-18 Google Inc. Automatic proxy setting modification
US7437364B1 (en) * 2004-06-30 2008-10-14 Google Inc. System and method of accessing a document efficiently through multi-tier web caching
US8224964B1 (en) 2004-06-30 2012-07-17 Google Inc. System and method of accessing a document efficiently through multi-tier web caching
US7730187B2 (en) * 2006-10-05 2010-06-01 Limelight Networks, Inc. Remote domain name service
US8301767B1 (en) 2005-12-21 2012-10-30 Mcafee, Inc. System, method and computer program product for controlling network communications based on policy compliance
CN100438517C (en) 2006-04-30 2008-11-26 中国移动通信集团公司 Family gateway equipment
US8107396B1 (en) * 2006-07-24 2012-01-31 Cisco Technology, Inc. Host tracking in a layer 2 IP ethernet network
US8812651B1 (en) 2007-02-15 2014-08-19 Google Inc. Systems and methods for client cache awareness
CN101094236B (en) * 2007-07-20 2011-08-10 华为技术有限公司 Method for processing message in address resolution protocol, communication system, and forwarding planar process portion
JP4430091B2 (en) * 2007-08-17 2010-03-10 富士通株式会社 Packet routing control method, packet routing control program, terminal device, and VPN server
US20100106854A1 (en) * 2008-10-29 2010-04-29 Hostway Corporation System and method for controlling non-existing domain traffic
JP5328472B2 (en) * 2009-05-13 2013-10-30 キヤノン株式会社 Network communication apparatus and method and program
US8949251B2 (en) 2010-04-20 2015-02-03 Verisign, Inc. System for and method of identifying closely matching textual identifiers, such as domain names
US8867439B2 (en) * 2010-04-30 2014-10-21 Qualcomm Incorporated Method and apparatus for establishing an interface between access points
US20130003600A1 (en) * 2011-06-29 2013-01-03 International Business Machines Corporation Configuration of Interfaces Communicatively Coupled to Link-Local Zones in a Network
US9225731B2 (en) 2012-05-24 2015-12-29 International Business Machines Corporation System for detecting the presence of rogue domain name service providers through passive monitoring
US8830869B2 (en) * 2012-07-18 2014-09-09 Accedian Networks Inc. Systems and methods of detecting and assigning IP addresses to devices with ARP requests
CN104869063B (en) * 2014-02-21 2019-02-12 华为技术有限公司 Host routes processing method and relevant device and communication system in virtual subnet
US9852172B2 (en) * 2014-09-17 2017-12-26 Oracle International Corporation Facilitating handling of crashes in concurrent execution environments of server systems while processing user queries for data retrieval
US9509587B1 (en) 2015-03-19 2016-11-29 Sprint Communications Company L.P. Hardware root of trust (HROT) for internet protocol (IP) communications
US10033699B2 (en) 2015-05-08 2018-07-24 Cloudflare, Inc. Transparent DNSSEC-signing proxy
US9954840B2 (en) 2015-05-08 2018-04-24 Cloudflare, Inc. Generating a negative answer to a domain name system query that indicates resource records as existing for the domain name regardless of whether those resource records actually exist for the domain name
CN106487942B (en) * 2015-08-31 2019-07-26 北京国双科技有限公司 A kind of display methods and device of domain name mapping information
US10270806B2 (en) * 2015-12-15 2019-04-23 Microsoft Technology Licensing, Llc Defense against NXDOMAIN hijacking in domain name systems
US9912739B1 (en) * 2017-01-12 2018-03-06 Red Hat Israel, Ltd. Open virtualized multitenant network scheme servicing virtual machine and container based connectivity
CN107707375B (en) * 2017-05-26 2018-07-20 贵州白山云科技有限公司 A kind of method and apparatus of positioning parsing failure
CN107579881A (en) * 2017-10-23 2018-01-12 上海斐讯数据通信技术有限公司 A kind of method of testing and system of router address analysis protocol
US11277442B2 (en) * 2019-04-05 2022-03-15 Cisco Technology, Inc. Verifying the trust-worthiness of ARP senders and receivers using attestation-based methods
US11012405B2 (en) * 2019-09-11 2021-05-18 Arista Networks, Inc. Distributing address resolution messages
BR102020003105A2 (en) * 2020-02-13 2021-08-24 Samsung Eletrônica da Amazônia Ltda. METHOD FOR DETECTION OF FAKE DNS SERVERS USING MACHINE LEARNING TECHNIQUES

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041324A (en) * 1997-11-17 2000-03-21 International Business Machines Corporation System and method for identifying valid portion of computer resource identifier
US20020073233A1 (en) * 2000-05-22 2002-06-13 William Gross Systems and methods of accessing network resources
US7426576B1 (en) * 2002-09-20 2008-09-16 Network Appliance, Inc. Highly available DNS resolver and method for use of the same
US7529852B2 (en) * 2004-05-17 2009-05-05 Cisco Technology, Inc. Method and apparatus for handling IPv4 DNS PTR queries across IPv4 and IPv6 networks
US7680104B2 (en) * 2004-11-09 2010-03-16 Cisco Technology, Inc. Address tagging for network address translation (NAT) traversal

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5724510A (en) 1996-09-06 1998-03-03 Fluke Corporation Method of configuring a valid IP address and detecting duplicate IP addresses in a local area network
US5708654A (en) 1996-11-27 1998-01-13 Arndt; Manfred R. Method for detecting proxy ARP replies from devices in a local area network
US6098108A (en) * 1997-07-02 2000-08-01 Sitara Networks, Inc. Distributed directory for enhanced network communication
US6332158B1 (en) * 1998-12-03 2001-12-18 Chris Risley Domain name system lookup allowing intelligent correction of searches and presentation of auxiliary information
JP3725376B2 (en) * 1999-09-29 2005-12-07 株式会社東芝 DNS inquiry apparatus, DNS inquiry method, and recording medium
US6993588B2 (en) * 2001-03-26 2006-01-31 Sumisho Computer Systems Corporation System and methods for securely permitting mobile code to access resources over a network
US7222359B2 (en) * 2001-07-27 2007-05-22 Check Point Software Technologies, Inc. System methodology for automatic local network discovery and firewall reconfiguration for mobile computing devices
US7200649B1 (en) * 2001-09-27 2007-04-03 Rockwell Automation Technologies, Inc. Adaptive method for duplicative IP address detection
GB2389023B (en) * 2002-05-20 2004-04-28 Sun Microsystems Inc Computer system, method and network
US7092990B2 (en) * 2002-06-26 2006-08-15 International Business Machines Corporation Handling node address failure in a distributed nodal system of processors
DE60334126D1 (en) * 2002-10-04 2010-10-21 Ericsson Telefon Ab L M ISOLATION OF HOSTS ASSOCIATED WITH AN ACCESS NETWORK
US7035257B2 (en) * 2002-11-14 2006-04-25 Digi International, Inc. System and method to discover and configure remotely located network devices
US7283544B2 (en) * 2002-12-05 2007-10-16 Hewlett-Packard Development Company, L.P. Automatic network device route management
JP3703457B2 (en) * 2003-01-21 2005-10-05 キヤノン株式会社 Address notification method, program, and apparatus
US7355996B2 (en) * 2004-02-06 2008-04-08 Airdefense, Inc. Systems and methods for adaptive monitoring with bandwidth constraints
JP4271988B2 (en) * 2003-05-19 2009-06-03 株式会社日立コミュニケーションテクノロジー Packet communication device
US20050095967A1 (en) * 2003-11-04 2005-05-05 Pan Jim L. Sole assembly for an orbital sander
US8037203B2 (en) * 2004-02-19 2011-10-11 International Business Machines Corporation User defined preferred DNS reference
US20050220106A1 (en) * 2004-03-31 2005-10-06 Pierre Guillaume Raverdy Inter-wireless interactions using user discovery for ad-hoc environments
US20060031394A1 (en) * 2004-04-20 2006-02-09 Tazuma Stanley K Apparatus and methods for transparent handling of browser proxy configurations in a network gateway device
US7808925B2 (en) * 2004-09-10 2010-10-05 Digital Envoy, Inc. Methods and systems for determining reverse DNS entries
US7471684B2 (en) * 2004-10-21 2008-12-30 International Machines Corporation Preventing asynchronous ARP cache poisoning of multiple hosts
US7594269B2 (en) * 2004-10-29 2009-09-22 Intel Corporation Platform-based identification of host software circumvention
US20060126614A1 (en) * 2004-12-09 2006-06-15 International Business Machines Corporation Automatic network configuration
US7626940B2 (en) * 2004-12-22 2009-12-01 Intruguard Devices, Inc. System and method for integrated header, state, rate and content anomaly prevention for domain name service
US20060176822A1 (en) * 2005-02-09 2006-08-10 International Business Machines Corporation Method, system, service, and computer program product for identifying incorrect domain name to internet protocol (IP) address mappings
US7801057B2 (en) * 2005-03-07 2010-09-21 AlgoSec Systems Ltd. Method and apparatus for converting a routing table into a collection of disjoint zones
US20060224704A1 (en) * 2005-04-01 2006-10-05 Vijay Parikh Auto-configuration for data collection terminals

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6041324A (en) * 1997-11-17 2000-03-21 International Business Machines Corporation System and method for identifying valid portion of computer resource identifier
US20020073233A1 (en) * 2000-05-22 2002-06-13 William Gross Systems and methods of accessing network resources
US7426576B1 (en) * 2002-09-20 2008-09-16 Network Appliance, Inc. Highly available DNS resolver and method for use of the same
US7529852B2 (en) * 2004-05-17 2009-05-05 Cisco Technology, Inc. Method and apparatus for handling IPv4 DNS PTR queries across IPv4 and IPv6 networks
US7680104B2 (en) * 2004-11-09 2010-03-16 Cisco Technology, Inc. Address tagging for network address translation (NAT) traversal

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120113964A1 (en) * 2009-02-02 2012-05-10 Eloy Technology, Llc Remote participation in a local area network (lan) based media aggregation network
US9191229B2 (en) * 2009-02-02 2015-11-17 Eloy Technology, Llc Remote participation in a Local Area Network (LAN) based media aggregation network
US20120110165A1 (en) * 2010-10-28 2012-05-03 Verisign, Inc. Evaluation of dns pre-registration data to predict future dns traffic
US9049229B2 (en) * 2010-10-28 2015-06-02 Verisign, Inc. Evaluation of DNS pre-registration data to predict future DNS traffic
US10257046B2 (en) 2010-10-28 2019-04-09 Verisign, Inc. Evaluation of DNS pre-registration data to predict future DNS traffic
US20150067114A1 (en) * 2013-08-29 2015-03-05 MasterCard International Incoirporated Systems and methods for resolving data inconsistencies between domain name systems
US9680790B2 (en) * 2013-08-29 2017-06-13 Mastercard International Incorporated Systems and methods for resolving data inconsistencies between domain name systems
US10091158B2 (en) * 2013-08-29 2018-10-02 Mastercard International Incorporated Systems and methods for resolving data inconsistencies between domain name systems

Also Published As

Publication number Publication date
AU2006232115B2 (en) 2009-11-19
WO2006108113A2 (en) 2006-10-12
DE602006019218D1 (en) 2011-02-10
EP1867141B1 (en) 2010-12-29
US20080298257A1 (en) 2008-12-04
US7436783B2 (en) 2008-10-14
AU2006232115C1 (en) 2010-03-18
EP2276223A1 (en) 2011-01-19
CA2603571A1 (en) 2006-10-12
AU2006232115A1 (en) 2006-10-12
CA2603571C (en) 2012-02-21
US8280991B2 (en) 2012-10-02
HK1113873A1 (en) 2008-10-17
WO2006108113A3 (en) 2007-01-18
EP1867141A2 (en) 2007-12-19
ATE493832T1 (en) 2011-01-15
US20060221979A1 (en) 2006-10-05
EP2276223B1 (en) 2012-08-22
US20060253612A1 (en) 2006-11-09
US7729292B2 (en) 2010-06-01

Similar Documents

Publication Publication Date Title
US8280991B2 (en) Method and apparatus for detecting incorrect responses to network queries
Cheshire et al. Nat port mapping protocol (nat-pmp)
Cheshire et al. Dynamic configuration of IPv4 link-local addresses
US7440453B2 (en) Determining availability of a destination for computer network communications
Cheshire et al. Multicast dns
US20230216884A1 (en) Method for minimizing the risk and exposure duration of improper or hijacked dns records
EP2556438B1 (en) Reverse dns lookup with modified reverse mappings
US8122113B2 (en) Dynamic host configuration protocol (DHCP) message interception and modification
US20060095585A1 (en) System and method for establishing communication between a client and a server in a heterogenous ip network
US9998321B2 (en) Method and apparatus for supporting duplicate suppression when issuing multicast queries using DNS-format message packets
US20120144483A1 (en) Method and apparatus for preventing network attack
Cheshire et al. Rfc 6762: Multicast dns
US20040230446A1 (en) Method and system of automatically registering domain name
Durand et al. Operational Considerations and Issues with IPv6 DNS
US7440466B2 (en) Method, apparatus and system for accessing multiple nodes on a private network
Cheshire et al. RFC 3927: Dynamic configuration of IPv4 link-local addresses
Howard Reverse dns in ipv6 for internet service providers
US20060126614A1 (en) Automatic network configuration
Cheshire et al. RFC 6886: Nat port mapping protocol (NAT-PMP)
JP3896361B2 (en) Communication path setting device, communication path setting method, and communication path setting program
ES2358811T3 (en) USE OF A TEST CONSULTATION TO DETERMINE IF A NETWORK DEVICE HAS A SOFTWARE ERROR OR A DESIGN FAILURE.
JP4288698B2 (en) DNS proxy for IPv6 / IPv4 translator
JP4425710B2 (en) Method, system, and medium for performing IPv6 communication
Cheshire RFC 8766: Discovery Proxy for Multicast DNS-Based Service Discovery
Howard RFC 8501: Reverse DNS in IPv6 for Internet Service Providers

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION