US20110075591A1 - Method and apparatus for looking up configuration information for a network node - Google Patents

Method and apparatus for looking up configuration information for a network node Download PDF

Info

Publication number
US20110075591A1
US20110075591A1 US12961729 US96172910A US2011075591A1 US 20110075591 A1 US20110075591 A1 US 20110075591A1 US 12961729 US12961729 US 12961729 US 96172910 A US96172910 A US 96172910A US 2011075591 A1 US2011075591 A1 US 2011075591A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
network node
dns
configuration information
service
packet
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
US12961729
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

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1505Directories; Name-to-address mapping involving standard directories or standard directory access protocols
    • H04L61/1511Directories; Name-to-address mapping involving standard directories or standard directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/30Arrangements for managing names, e.g. use of aliases or nicknames
    • H04L61/303Name structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/18Network-specific arrangements or communication protocols supporting networked applications in which the network application is adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/34Network-specific arrangements or communication protocols supporting networked applications involving the movement of software or configuration parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0803Configuration setting of network or network elements
    • H04L41/0823Configuration optimization
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2007Address allocation internet protocol [IP] addresses
    • H04L61/2015Address allocation internet protocol [IP] addresses using the dynamic host configuration protocol [DHCP] or variants

Abstract

One embodiment of the present invention provides a system for looking up location-specific configuration information for a network node or a subnet. During system operation, a network node creates a query message containing a key that comprises an Internet Protocol (IP) prefix and a string, wherein the IP prefix identifies the network node or the subnet, and the string specifies the type of configuration information. The network node then sends the query message to a name server, which is part of a distributed system that provides a global naming service, wherein the name server additionally stores configuration information. Finally, the network node receives a response message from the name server, wherein the response message contains the requested configuration information.

Description

    RELATED APPLICATION
  • The present patent is a continuation of, and hereby claims priority under 35 U.S. §120 to, pending U.S. patent application Ser. No. 10/877,401, entitled “Method and Apparatus for Looking up Configuration Information for a Network Node,” by inventor Stuart D. Cheshire, filed on 25 Jun. 2004 (Attorney Docket No. APL-P3398).
  • BACKGROUND
  • 1. Field of the Invention
  • The present invention relates to the process of looking up configuration information for a network node. More specifically, the present invention relates to the process of looking up configuration information for a network node by sending a query message to a name server, which is part of a distributed system that provides a global naming service.
  • 2. Related Art
  • The Internet is permeating more and more aspects of our lives—from buying cameras to buying real estate, and from reading a newspaper to watching a movie.
  • Due to the Internet's complexity, a network node, such as a computer, that wants to participate in the Internet needs to lookup a large amount of configuration information. For example, a network node typically needs to look up the name of an e-mail server, before it can send or receive e-mail.
  • The configuration information that a network node needs to lookup tends to be location specific. For example, the name of an e-mail server for a network node in an organization can be different from the name of an e-mail server for another network node within the same organization. Furthermore, it is cumbersome to ask the user to lookup the configuration information. Hence, there is a strong need for a mechanism that allows a network node to automatically lookup configuration information on its own.
  • DHCP (Dynamic Host Configuration Protocol) is a commonly-used protocol that was designed to automatically assign IP addresses to network nodes. It has subsequently been extended to allow a network node to lookup configuration information. Today, many network nodes use DHCP for looking up configuration information.
  • Unfortunately, there are many drawbacks in using DHCP for looking up configuration information. Since DHCP is typically used only once during system boot, the network node gets only one chance to lookup configuration information. This is a severe limitation, because it forces the network node to guess what kind of configuration information it is going to need in the future. For example, if the network node does not lookup the NetBIOS (Network Basic Input Output System) name server during system boot, the network node may not be able to provide this information to an application that requires this information during normal system operation, thereby preventing the application from running properly.
  • Furthermore, since configuration information can change over time, the configuration information that was obtained using DHCP during system boot can be out of date.
  • Note that, although it is possible to use DHCP to lookup configuration information during normal system operation, such lookup operations may not be supported by all DHCP servers. Moreover, performing a lookup during normal system operation may cause the DHCP server to assign a new IP address to the network node, which can cause many applications to malfunction.
  • Furthermore, DHCP can only support up to 255 types of configuration information, which places a hard limit on the types of configuration information that can be looked up using DHCP.
  • In addition, one of the benefits of IPv6 is that it allows a network node to configure IPv6 addresses for its interfaces without requiring a DHCP server. This is beneficial because it reduces the burden on network operators by reducing the number of servers they need to maintain. However, if network operators have to continue using DHCP servers even after upgrading to IPv6, one of the important advantages of using IPv6 will be eliminated.
  • Hence, what is needed is a method and apparatus for looking up a wide range of location-specific configuration information for a network node, wherein the method and apparatus does not have the drawbacks described above.
  • SUMMARY
  • One embodiment of the present invention provides a system for looking up location-specific configuration information for a network node or a subnet. During system operation, a network node creates a query message containing a key that comprises an Internet Protocol (IP) prefix and a string, wherein the IP prefix identifies the network node or the subnet, and the string specifies the type of configuration information. The network node then sends the query message to a name server, which is part of a distributed system that provides a global naming service, wherein the name server additionally stores configuration information. Finally, the network node receives a response message from the name server, wherein the response message contains the requested configuration information.
  • In a variation on this embodiment, a name server receives a query message from a network node, wherein the query message contains a key that comprises an IP prefix and a string, wherein the IP prefix identifies a network node or a subnet, and the string specifies the type of configuration information. The name server then looks up the configuration information in a configuration database using the key. Finally, the name server sends a response message to the network node, wherein the response message contains the configuration information.
  • In a variation on this embodiment, the IP prefix can include all of the bits of an IP address.
  • In a variation on this embodiment, the key is created by first reversing the bytes of the IP prefix, and representing the reversed bytes of the IP prefix as a string. Next, a string that specifies the type of configuration information is prepended to the reversed-IP-prefix string. Finally, the string “.in-addr.arpa.” is appended to the resulting string to form the entire key.
  • In a variation on this embodiment, the name server belongs to the Domain Name System (DNS).
  • In a variation on this embodiment, the query message can be a DNS-query message.
  • In a variation on this embodiment, the response message can be a DNS-response message.
  • In a variation on this embodiment, the IP prefix can be an IP version 4 prefix or an IP version 6 prefix.
  • BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 illustrates a network that is connected to multiple network nodes, namely, a computer, an SMTP (Simple Mail Transfer Protocol) server, an NTP (Network Time Protocol) server, an NetBIOS (Network Basic Input Output System) server, a POP3 (Post Office Protocol 3) server, and a DNS (Domain Name System) name server containing configuration information in accordance with an embodiment of the present invention.
  • FIG. 2 illustrates a DNS packet that contains multiple pieces of information that can be used by a network node, such as a computer, to exchange information with a DNS name server in accordance with an embodiment of the present invention.
  • FIG. 3 illustrates the structure of a query that makes up the queries field in a DNS packet in accordance with an embodiment of the present invention.
  • FIG. 4 illustrates the structure of a resource record that can be used by the DNS name server to provide information in response to a query in accordance with an embodiment of the present invention.
  • FIG. 5 presents a flowchart illustrating a process that a network node, such as a computer, can use to lookup configuration information by querying a DNS name server containing configuration information 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 intended to be 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), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.
  • Network
  • FIG. 1 illustrates a network 104 that is connected to multiple network nodes, namely, a computer 102, an SMTP (Simple Mail Transfer Protocol) server 118, an NTP (Network Time Protocol) server 120, an NetBIOS (Network Basic Input Output System) server 122, a POP3 (Post Office Protocol 3) server 124, and a DNS (Domain Name System) name server containing configuration information 116 in accordance with an embodiment of the present invention.
  • Network 104 can generally include any type of wire or wireless communication channel capable of coupling together network nodes. This includes, but is not limited to, a local area network, a wide area network, or a combination of networks. In one embodiment of the present invention, network 104 includes the Internet.
  • A network node, such as a computer 102, can generally include any type of communication device capable of communicating with other network nodes via a network. This includes, but is not limited to, a computer system based on a microprocessor, a mainframe computer, a server, a printer, a video camera, an external disk drive, a router, a switch, a personal organizer, and a mobile phone.
  • Network 104 allows a source network-node, such as a computer 102, to communicate with a target network-node, such as an SMTP server 118.
  • But, before the communication can take place, the source network-node, computer 102, needs to know the name or the IP address of the target network-node, SMTP server 118. Typically, such configuration information can be obtained by computer 102 using DHCP during system boot and can be stored for later use.
  • Configuration Information
  • FIG. 1 illustrates a collection of configuration information 106 that can be stored on a computer 102 in accordance with an embodiment of the present invention. This collection of configuration information 106 includes one or more pieces of configuration information, such as, an SMTP server name 108, an NTP server name 110, a POP3 server name 112, and a NetBIOS server name 114. Among other uses, collection of configuration information 106 allows computer 102 to provide various services to its users. For example, computer 102 can use the SMTP server name 108, which is part of collection of configuration information 106, to communicate with the SMTP server 118, thereby providing e-mail services to its end users.
  • Structure of a DNS Packet
  • FIG. 2 illustrates a DNS packet 200 that contains multiple pieces of information that can be used by a network node, such as a computer 102, to exchange information with a DNS name server 116 in accordance with an embodiment of the present invention.
  • DNS-query packets and DNS-response packets both use the same DNS packet format. Specifically, a DNS packet 200 contains an identification field 202, which allows a network node, such as a computer 102, to match queries to the corresponding responses. DNS packet 200 also contains a flags field 204, which among other things, indicates whether the DNS packet 200 is a query or a response.
  • Furthermore, DNS packet 200 contains four variable-length fields, namely, queries 214, response resource-records 216, authority response-records 218, and additional information response-records 220. These variable-length fields are used for exchanging information between a network node, computer 102, and a DNS name server 116.
  • Additionally, DNS packet 200 contains four other fields, namely, a number of queries field 206, a number of response resource-records field 208, a number of authority resource-records field 210, and a number of additional information resource-records field 212, which specify the number of entries in the four variable-length fields.
  • Structure of a Query
  • FIG. 3 illustrates the structure of a query 300 that makes up the queries field 214 in accordance with an embodiment of the present invention. Query 300 contains a domain name field 302, which specifies the domain name that is being queried. Furthermore, query 300 includes a query type field 304, and a query class field 306, which specifies the type and the class of the query 300, respectively.
  • Structure of a Resource Record
  • FIG. 4 illustrates the structure of a resource record 400 that can be used by a DNS name server 116 to provide information in response to a query in accordance with an embodiment of the present invention.
  • Specifically, resource record 400 contains a domain name field 402, which specifies the domain name under consideration. Resource record 400 also contains a resource-record type field 404 and a resource-record class field 406, which specifies the type and class of the resource record, respectively. Additionally, resource record 400 includes a time to live field 408, which specifies the amount of time (in seconds) that the resource record can be cached by a network node, such as a computer 102. Furthermore, resource record 400 contains a resource data field 412, which is a variable-length field that can be used by DNS name server 116 to provide information to the network node, computer 102, in response to a query. Resource record 400 also contains a resource data length field 410, which specifies the amount of data in the variable-length resource data field 412.
  • Process of Looking up Configuration Information
  • FIG. 5 presents a flowchart illustrating the process that a network node, such as a computer 102, can use to lookup configuration information by querying a DNS name server containing configuration information 116 in accordance with an embodiment of the present invention.
  • First, computer 102 creates a DNS-query packet 200, which includes a query 300 containing a key (step 502). More specifically, the domain name 302 in the query 300 comprises the key, which is created by first reversing the bytes of the IP prefix and representing the reversed IP-prefix as a string. Next, a string that specifies the type of configuration information is prepended to the reversed-IP-prefix string. Finally, the string “.in-addr.arpa.” is appended to the resulting string form the entire key. Note that the string “.in-addr.arpa.” represents a special domain in DNS that is used for address-to-name mappings.
  • For example, if the computer 102, whose IP address is 17.255.12.34 with subnet mask 255.255.0.0, wants to lookup the NTP server name 110, it would create a query 300 with domain name 302 that contains the key “4.dhcpopt.255.17.in-addr.arpa”, wherein “4.dhcpopt.” is a string that specifies the type of configuration information, “255.17” is a string representation of the reversed IP-prefix, and “.in-addr.arpa.” is the appended string. Note that, the string “4.dhcpopt.” refers to DHCP option 4, which corresponds to the NTP server name, as defined in IETF (Internet Engineering Task Force) RFC (Request for Comments) 2132. It will be readily apparent to one skilled in the art that every DHCP option defined in IETF RFC 2132 can be similarly converted into a string that specifies the type of configuration information.
  • Next, the computer sends the DNS-query packet 200 (step 504) to a DNS name server containing configuration information 116. The DNS name server containing configuration information 116 then receives the DNS-query packet 200 (step 506). Next, the DNS name server containing configuration information 116 looks up the configuration information in its database using the key in the query (step 508), which is contained in the DNS-query packet 200. The DNS name server containing configuration information 116 then sends a response message containing the configuration information (step 510). Finally, computer 102 receives the response message (step 512) containing the configuration information, thereby allowing computer 102 to use the configuration information to perform its task.
  • Furthermore, a network node, such as a computer 102, can send multiple queries to the DNS name server containing configuration information 116 to lookup configuration information at different levels of granularity. For example, the network node can send a query containing the key “4.dhcpopt.34.12.255.17.in-addr.arpa” to find host-specific configuration that applies to that host alone. On the other hand, the network node can send a query containing the key “4.dhcpopt.255.17.in-addr.arpa” to find subnet-specific configuration information that applies to all network nodes on that subnet. Moreover, the network node can send a query containing the key “4.dhcpopt.17.in-addr.arpa” to find company-wide configuration information that applies uniformly to all the network nodes in a company.
  • Note that DNS was designed so that network nodes could query it during normal system operation. Hence, by using DNS instead of DHCP to store configuration information, the present invention overcomes one of the limitations of DHCP, in which the network node was restricted to lookup configuration information during system boot only. Furthermore, a network node can keep its configuration information up to date by periodically querying a DNS name server containing configuration information. Moreover, in the present invention, the type of configuration information is specified by an arbitrary string, such as “4.dhcpopt.”. Hence, the present invention can potentially support infinite types of configuration information, whereas DHCP can support only up to 255 types of configuration information.
  • The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. 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 (20)

  1. 1. A method for configuring a service in a network node, the method comprising:
    creating a Domain Name System (DNS) query packet at the network node, wherein the DNS query packet specifies a service that is to be configured at the network node;
    sending the DNS query packet to a DNS server that is configured to provide a name resolution service, wherein the DNS server is further configured to provide configuration information for the service;
    receiving a DNS response packet from the DNS server, wherein the DNS response packet includes configuration information for the service; and
    configuring the service at the network node using the configuration information from the DNS response packet.
  2. 2. The method of claim 1, wherein the configuration information is specific to a corresponding level of granularity.
  3. 3. The method of claim 2, wherein the level of granularity is one of: a host, a network node, a subnet, a location, or a company.
  4. 4. The method of claim 1, wherein creating the DNS query packet comprises:
    prepending a configuration-identifier associated with the service to an address or a subnet of the network node to obtain a query string;
    appending “.in-addr.arpa.” to the query string to create a key; and
    writing the key into a DNS query field in the DNS query packet.
  5. 5. A method for providing configuration for configuring a service in a network node, the method comprising:
    at a DNS server,
    receiving a DNS query packet from a network node, wherein the DNS query packet specifies a service that is to be configured at the network node;
    retrieving configuration information for the service from a database in the DNS server;
    creating a DNS response packet that includes the configuration information; and
    sending the DNS response packet from the DNS server to the network node, wherein the configuration information in the DNS response packet facilitates the network node configuring the service at the network node.
  6. 6. The method of claim 5, wherein the configuration information that is retrieved from the database in the DNS server is specific a corresponding level of granularity.
  7. 7. The method of claim 6, wherein the level of granularity is one of: a host, a network node, a subnet, a location, or a company.
  8. 8. The method of claim 5, retrieving the configuration information from the database in the DNS server comprises accessing one or more resource-records.
  9. 9. A computer-readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method for configuring a service in a network node, the method comprising:
    creating a DNS query packet at the network node, wherein the DNS query packet specifies a service that is to be configured at the network node;
    sending the DNS query packet to a DNS server that is configured to provide a name resolution service, wherein the DNS server is further configured to provide configuration information for the service;
    receiving a DNS response packet from the DNS server, wherein the DNS response packet includes configuration information for the service; and
    configuring the service at the network node using the configuration information from the DNS response packet.
  10. 10. The method of claim 9, wherein the configuration information is specific to a corresponding level of granularity.
  11. 11. The method of claim 10, wherein the level of granularity is one of:
    a host, a network node, a subnet, a location, or a company.
  12. 12. The computer-readable storage medium of claim 9, wherein creating the DNS query packet comprises:
    prepending a configuration-identifier associated with the service to an address or a subnet of the network node to obtain a query string;
    appending “.in-addr.arpa.” to the query string to create a key; and
    writing the key into a DNS query field in the DNS query packet.
  13. 13. A computer-readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method for providing configuration for configuring a service in a network node, the method comprising:
    at a DNS server,
    receiving a DNS query packet from a network node, wherein the DNS query packet specifies a service that is to be configured at the network node;
    retrieving configuration information for the service from a database in the DNS server;
    creating a DNS response packet that includes the configuration information; and
    sending the DNS response packet from the DNS server to the network node, wherein the configuration information in the DNS response packet facilitates the network node configuring the service at the network node.
  14. 14. The computer-readable storage medium of claim 13, wherein the configuration information that is retrieved from the database in the DNS server is specific a corresponding level of granularity.
  15. 15. The computer-readable storage medium of claim 14, wherein the level of granularity is one of: a host, a network node, a subnet, a location, or a company.
  16. 16. The computer-readable storage medium of claim 13, retrieving the configuration information from the database in the DNS server comprises accessing one or more resource-records.
  17. 17. An apparatus used for configuring a service in a network node, the apparatus comprising:
    in the network node,
    a creating mechanism in the network node configured to create a DNS query packet, wherein the DNS query packet specifies a service that is to be configured at the network node;
    a sending mechanism configured to send the DNS query packet to a DNS server that is configured to provide a name resolution service, wherein the DNS server is further configured to provide configuration information for the service;
    a receiving mechanism configured to receive a DNS response packet from the DNS server, wherein the DNS response packet includes configuration information for the service; and
    a configuring mechanism configured to configure the service at the network node using the configuration information from the DNS response packet.
  18. 18. The apparatus of claim 17, wherein the configuration information is specific to a corresponding level of granularity from one of: a host, a network node, a subnet, a location, or a company.
  19. 19. An apparatus for providing configuration for configuring a service in a network node, the apparatus comprising:
    in a DNS server,
    a receiving mechanism configured to receive a DNS query packet from a network node, wherein the DNS query packet specifies a service that is to be configured at the network node;
    a looking up mechanism configured to retrieve configuration information for the service from a database in the DNS server;
    a creating mechanism configured to create a DNS response packet that includes the configuration information; and
    a sending mechanism configured to send the DNS response packet from the DNS server to the network node, wherein the configuration information in the DNS response packet facilitates the network node configuring the service at the network node.
  20. 20. The apparatus of claim 19, wherein the configuration information is specific to a corresponding level of granularity from one of: a host, a network node, a subnet, a location, or a company.
US12961729 2004-06-25 2010-12-07 Method and apparatus for looking up configuration information for a network node Abandoned US20110075591A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10877401 US7864709B2 (en) 2004-06-25 2004-06-25 Method and apparatus for looking up configuration information for a network node
US12961729 US20110075591A1 (en) 2004-06-25 2010-12-07 Method and apparatus for looking up configuration information for a network node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12961729 US20110075591A1 (en) 2004-06-25 2010-12-07 Method and apparatus for looking up configuration information for a network node

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10877401 Continuation US7864709B2 (en) 2004-06-25 2004-06-25 Method and apparatus for looking up configuration information for a network node

Publications (1)

Publication Number Publication Date
US20110075591A1 true true US20110075591A1 (en) 2011-03-31

Family

ID=34960768

Family Applications (2)

Application Number Title Priority Date Filing Date
US10877401 Active 2027-10-02 US7864709B2 (en) 2004-06-25 2004-06-25 Method and apparatus for looking up configuration information for a network node
US12961729 Abandoned US20110075591A1 (en) 2004-06-25 2010-12-07 Method and apparatus for looking up configuration information for a network node

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10877401 Active 2027-10-02 US7864709B2 (en) 2004-06-25 2004-06-25 Method and apparatus for looking up configuration information for a network node

Country Status (6)

Country Link
US (2) US7864709B2 (en)
EP (1) EP1759510B1 (en)
JP (1) JP4405553B2 (en)
CN (1) CN1951081B (en)
CA (1) CA2562889C (en)
WO (1) WO2006011908A1 (en)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7552202B2 (en) * 2005-03-10 2009-06-23 International Business Machines Corporation System and method to uniquely identify identically configured branches in a distributed enterprise
US8400947B2 (en) * 2006-07-20 2013-03-19 Tekelec, Inc. Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types
CN101212486A (en) * 2006-12-28 2008-07-02 华为技术有限公司 Parameter information acquisition method, system, and parameter information feedback device
US20090055751A1 (en) * 2007-08-24 2009-02-26 Microsoft Corporation Management System for Local and Remote Services
CN101803343B (en) 2007-09-18 2014-02-12 惠普开发有限公司 Identifying subnet address range from DNS information
CN101442436A (en) * 2007-11-20 2009-05-27 国际商业机器公司 IP network management method and system
US8782278B2 (en) * 2008-03-21 2014-07-15 Qualcomm Incorporated Address redirection for nodes with multiple internet protocol addresses in a wireless network
US8244814B1 (en) * 2008-03-31 2012-08-14 Symantec Corporation Methods and systems for managing email configuration
US8578055B2 (en) * 2009-07-09 2013-11-05 International Business Machines Corporation Propogation of DNS server IP addresses in a private network
US8103795B2 (en) * 2009-07-09 2012-01-24 International Business Machines Corporation TCP/IP host name resolution on a private network
US8140669B2 (en) * 2009-08-31 2012-03-20 International Business Machines Corporation Resolving hostnames on a private network with a public internet server
CN101674311B (en) 2009-10-10 2012-07-04 成都市华为赛门铁克科技有限公司 Address inquiring method, gateway or user device, and server
US8990356B2 (en) 2011-10-03 2015-03-24 Verisign, Inc. Adaptive name resolution
CN103793217B (en) * 2012-10-31 2017-03-01 国际商业机器公司 Method and system for rapid configuration of software
US9917905B2 (en) 2013-05-13 2018-03-13 International Business Machines Corporation Location-based domain name system service discovery
US9900281B2 (en) 2014-04-14 2018-02-20 Verisign, Inc. Computer-implemented method, apparatus, and computer-readable medium for processing named entity queries using a cached functionality in a domain name system

Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6092178A (en) * 1998-09-03 2000-07-18 Sun Microsystems, Inc. System for responding to a resource request
US6167449A (en) * 1997-11-19 2000-12-26 Apple Computer, Inc. System and method for identifying and locating services on multiple heterogeneous networks using a query by type
US6178451B1 (en) * 1998-11-03 2001-01-23 Telcordia Technologies, Inc. Computer network size growth forecasting method and system
US6324582B1 (en) * 1997-07-01 2001-11-27 Sitara Networks, Inc. Enhanced network communication
US20020099803A1 (en) * 2001-01-19 2002-07-25 Stuart Cheshire Presentation during network address acquisition
US20030002496A1 (en) * 2001-06-27 2003-01-02 Niels Beier Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US20030007482A1 (en) * 2001-07-06 2003-01-09 Robert Khello Method and apparatus for resolving an entity identifier into an internet address using a domain name system (DNS) server and an entity identifier portability database
US20040083307A1 (en) * 2002-10-27 2004-04-29 Mr. Sezen Uysal Apparatus and method for transparent selection of an internet server based on geographic location of a user
US20040162892A1 (en) * 2003-02-18 2004-08-19 Hsu Raymond T. Provisioning server information in a mobile station
US20040215707A1 (en) * 2003-02-28 2004-10-28 Nec Corporation Name resolution server and packet transfer device
US6839421B2 (en) * 2001-10-29 2005-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus to carry out resolution of entity identifier in circuit-switched networks by using a domain name system
US20050005027A1 (en) * 2003-04-18 2005-01-06 International Business Machines Corporation Method and system for obtaining data through an IP transmission network by using an optimized domain name server
US20050021841A1 (en) * 2003-04-10 2005-01-27 Tetsuro Yoshimoto Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device
US20050124382A1 (en) * 2003-12-09 2005-06-09 Nokia Corporation System and method for service naming and related directory structure in a mobile data network
US7120675B1 (en) * 2000-09-26 2006-10-10 Microsoft Corporation Information location service
US20080016233A1 (en) * 1999-03-22 2008-01-17 Eric Schneider Methods, systems, products, and devices for processing dns friendly identifiers
US7328237B1 (en) * 2002-07-25 2008-02-05 Cisco Technology, Inc. Technique for improving load balancing of traffic in a data network using source-side related information
US20080059607A1 (en) * 1999-09-01 2008-03-06 Eric Schneider Method, product, and apparatus for processing a data request
US7472201B1 (en) * 2002-09-12 2008-12-30 Cisco Technology, Inc. Method and system for resolving domain name system queries in a multiprotocol communications network
US7797410B2 (en) * 2004-04-29 2010-09-14 Euro Convergence, Sarl Reverse IP method and system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0922363B1 (en) 1996-08-30 2007-01-31 Telefonaktiebolaget LM Ericsson (publ) System and method for incoming and outgoing interrogations for store-and-forward services
US7152099B1 (en) 2000-10-31 2006-12-19 Hewlett-Packard Development Company, Lp. Friend configuration and method for network devices

Patent Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6324582B1 (en) * 1997-07-01 2001-11-27 Sitara Networks, Inc. Enhanced network communication
US20010047421A1 (en) * 1997-07-01 2001-11-29 Sitara Networks, Inc. A Delaware Corporation Enhanced network communication
US6167449A (en) * 1997-11-19 2000-12-26 Apple Computer, Inc. System and method for identifying and locating services on multiple heterogeneous networks using a query by type
US6092178A (en) * 1998-09-03 2000-07-18 Sun Microsystems, Inc. System for responding to a resource request
US6178451B1 (en) * 1998-11-03 2001-01-23 Telcordia Technologies, Inc. Computer network size growth forecasting method and system
US20080016233A1 (en) * 1999-03-22 2008-01-17 Eric Schneider Methods, systems, products, and devices for processing dns friendly identifiers
US20080059607A1 (en) * 1999-09-01 2008-03-06 Eric Schneider Method, product, and apparatus for processing a data request
US7120675B1 (en) * 2000-09-26 2006-10-10 Microsoft Corporation Information location service
US20020099803A1 (en) * 2001-01-19 2002-07-25 Stuart Cheshire Presentation during network address acquisition
US20030002496A1 (en) * 2001-06-27 2003-01-02 Niels Beier Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US20030007482A1 (en) * 2001-07-06 2003-01-09 Robert Khello Method and apparatus for resolving an entity identifier into an internet address using a domain name system (DNS) server and an entity identifier portability database
US6839421B2 (en) * 2001-10-29 2005-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus to carry out resolution of entity identifier in circuit-switched networks by using a domain name system
US7328237B1 (en) * 2002-07-25 2008-02-05 Cisco Technology, Inc. Technique for improving load balancing of traffic in a data network using source-side related information
US7472201B1 (en) * 2002-09-12 2008-12-30 Cisco Technology, Inc. Method and system for resolving domain name system queries in a multiprotocol communications network
US20040083307A1 (en) * 2002-10-27 2004-04-29 Mr. Sezen Uysal Apparatus and method for transparent selection of an internet server based on geographic location of a user
US20040162892A1 (en) * 2003-02-18 2004-08-19 Hsu Raymond T. Provisioning server information in a mobile station
US20040215707A1 (en) * 2003-02-28 2004-10-28 Nec Corporation Name resolution server and packet transfer device
US20050021841A1 (en) * 2003-04-10 2005-01-27 Tetsuro Yoshimoto Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device
US20050005027A1 (en) * 2003-04-18 2005-01-06 International Business Machines Corporation Method and system for obtaining data through an IP transmission network by using an optimized domain name server
US20050124382A1 (en) * 2003-12-09 2005-06-09 Nokia Corporation System and method for service naming and related directory structure in a mobile data network
US7797410B2 (en) * 2004-04-29 2010-09-14 Euro Convergence, Sarl Reverse IP method and system

Also Published As

Publication number Publication date Type
US20050286514A1 (en) 2005-12-29 application
WO2006011908A1 (en) 2006-02-02 application
EP1759510A1 (en) 2007-03-07 application
US7864709B2 (en) 2011-01-04 grant
JP4405553B2 (en) 2010-01-27 grant
EP1759510B1 (en) 2017-11-15 grant
CN1951081B (en) 2010-06-16 grant
CN1951081A (en) 2007-04-18 application
CA2562889A1 (en) 2006-02-02 application
JP2007534237A (en) 2007-11-22 application
CA2562889C (en) 2011-09-27 grant

Similar Documents

Publication Publication Date Title
US7009941B1 (en) Node-search method, device, and medium on which a node-search program is recorded
US6058421A (en) Method and system for addressing network host interfaces from a cable modem using DHCP
US7734745B2 (en) Method and apparatus for maintaining internet domain name data
US7139818B1 (en) Techniques for dynamic host configuration without direct communications between client and server
US20090222541A1 (en) Dynamic sensor network registry
US20030061333A1 (en) System and method for universal networked device management
US20040111494A1 (en) Network location signature for disambiguating multicast messages in dual-IP stack and/or multi-homed network environments
Cheshire et al. Dynamic configuration of IPv4 link-local addresses
US20030208609A1 (en) Automatic configuration of advanced services over DSL
US7152118B2 (en) System, method and computer program product for caching domain name system information on a network gateway
US6754622B1 (en) Method for network address table maintenance in a data-over-cable system using destination reachibility
US6697862B1 (en) System and method for network address maintenance using dynamic host configuration protocol messages in a data-over-cable system
US8005981B2 (en) Computer network with unique identification
US20060159100A1 (en) Use of IPv6 in access networks
US20070214232A1 (en) System for Uniform Addressing of Home Resources Regardless of Remote Clients Network Location
US6654387B1 (en) Method for network address table maintenance in a data-over-cable system using a network device registration procedure
US7231660B1 (en) Method and system for preventing unauthorized server interference in an internet protocol network
US20050185658A1 (en) Gateway apparatus connected to a plurality of networks forming respective different network segments, and program and method for transferring IP packets
US20070053334A1 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
US20060010224A1 (en) Method and apparatus for facilitating long-lived DNS queries
US20100077023A1 (en) Method and Apparatus for Establishing a Session
US20030163722A1 (en) System, method and computer program product for selectively caching domain name system information on a network gateway
Cheshire et al. Nat port mapping protocol (nat-pmp)
US20050027834A1 (en) Bi-level addressing for internet protocol broadband access
US20020101836A1 (en) Method and apparatus in a portable subscriber unit for minimizing a connection setup time through a communication network