Browse Prior Art Database

Method to Pass a Name for a Point-to-Point Protocol Client to Dynamic Domain Name Server

IP.com Disclosure Number: IPCOM000119078D
Original Publication Date: 1997-Nov-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 120K

Publishing Venue

IBM

Related People

Goetze, LM: AUTHOR [+2]

Abstract

Disclosed is a method to pass a name for a Point-to-Point Protocol (PPP) client to Dynamic Domain Name Server (DDNS). The PPP server access userID is used as the host name for the Internet Protocol (IP) address that is obtained from a Dynamic Host Configuration Protocol (DHCP) server on behalf of a PPP client.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 44% of the total text.

Method to Pass a Name for a Point-to-Point Protocol Client to Dynamic
Domain Name Server

      Disclosed is a method to pass a name for a Point-to-Point
Protocol (PPP) client to Dynamic Domain Name Server (DDNS).  The PPP
server access userID is used as the host name for the Internet
Protocol (IP) address that is obtained from a Dynamic Host
Configuration Protocol  (DHCP) server on behalf of a PPP client.

      The method for passing a name for a PPP client to a DDNS is
based on information contained in the following Internet Request for
Comments (RFC) documents:
  o  RFC 951 - BOOTSTRAP Protocol (BOOTP)
  o  RFC 1533 - DHCP Options and BOOTP Vendor Extensions
  o  RFC 1541 - Dynamic Host Configuration Protocol
  o  RFC 1661 - The Point to Point Protocol
  o  Internet Draft draft-ietf-dhc-dhcp-dns-02.txt - Interaction
      between DHCP and DNS

The networking components are assumed to have the following
capabilities:
  o  The PPP server has an integrated DHCP client capability.
  o  The PPP server has a security component which allows
      assignment of unique userIDs to PPP clients.
  o  The DHCP server supports a Fully Qualified Domain Name
      (FQDN) as an option.
  o  The DDNS allows someone other than the client to update
      the fully qualified domain name to IP address mappings.

      The DHCP client component of the PPP server must be able to
send the following DHCP options in a DHCPREQUEST message:
  o  Option 81 - Client Fully Qualified Domain Name option
       This option allows the DHCP server to update the DDNS
      name-to-address mappings on behalf of the DHCP client.
  o  Option 12 - Host Name option
       This option specifies the name of the client.  The name
      may or may not be qualified with the local domain name.
  o  Option 15 - Domain Name option
       This option specifies the domain name that the client
      should use when resolving host names via the Domain Name
      System.

      The Host Name option and the Domain Name option are sent to the
DHCP server just in case the server supports A record (name to IP
address mapping) and PTR (IP address to name mapping) record updates
based on these options.  If both are recognized by the DHCP server,
the FQDN client option has precedence.

      Keywords and parameters to enable and configure the DHCP
options on the PPP server are stored in an ASCII configuration file
on the PPP server.

The following keywords and parameters are defined:

DDNS
     The DDNS keyword indicates whether the PPP Server access
    userID should be used as the host name that is associated
    with an IP  address that is obtained from a DHCP server.

     The following shows how to specify the two parameters:
          DDNS=YES
          DDNS=NO
      YES or NO can be specified but not both.  If YES is
    specified, the DDNS is updated...