KR100545738B1 - How to create unique domain name based on network device address - Google Patents

Abstract

The present invention relates to a method for automatically generating a unique domain name of each terminal in a network without a network manager, such as a home network or an ad-hoc network. In the existing DNS, in order for a user to be assigned his or her domain name, the domain administrator is informed of the user ID that he / she wants to use, and the administrator checks the redundancy of the user ID and applies if the requested ID is unique in the domain. Assign a user a domain name based on the requested user ID. If the ID is a duplicate, the administrator will ask the user to select a different user ID. According to the present invention, a user who wants his or her own ID without a network administrator's intervention in a home network or an ad hoc network that is temporarily formed of mobile terminals whose information does not have an existing authorized name server is configured as an electric appliance. It provides a method of automatically generating a unique domain name in the domain to which the terminal belongs while making it available. In addition, the present invention provides a method for detecting a domain name for a counterpart terminal through a unique domain name and an extended name server. The domain name of the present invention is composed of a user ID of the terminal, a network device address, and a domain to which the terminal belongs. Since the globally unique network device address is used, uniqueness of the domain name is ensured.

Description

How to create unique domain name based on network device address {METHOD FOR GENERATING UNIQUE DOMAIN NAME BASED ON NETWORK DEVICE IDENTIFIER}

1 illustrates a basic IPv6 unicast address structure;

2 is a diagram illustrating a method of converting an EUI-48 MAC address, which is a network device address, into an EUI-64 ID;

3 is a block diagram illustrating a network configuration of terminals participating in domain name generation according to the present invention;

4 is a diagram illustrating a structure of a domain name of the present invention and a domain name embodiment of the present invention comprising a user ID, an EUI-64 ID of a network device address, and a domain to which a terminal belongs, using FIG. 2;

5 is a flowchart illustrating step-by-step creation of the domain name of FIG. 4;

FIG. 6 is a flowchart illustrating a step-by-step operation of a name server that performs a DNS service for a domain name generated through FIG. 5; FIG.

<Explanation of symbols for main parts of the drawings>

10, 12, 14, 16, 18: terminal 1 to terminal 5

The present invention relates to a method of generating a unique domain name based on a network device identifier. In particular, each terminal has its own unique network in a network without a network manager such as a home network or an ad-hoc network. A method for automatically generating a domain name.

The 64-bit Extended Unique Identifier (EUI-64) format is the high-order 24-bit company ID (company_id) given by the "IEEE Registration Authority" and the 40-bit extension ID given by the company or organization that is assigned the company ID. It consists of an extension identifier. In addition, the EUI-48 format is similar to EUI-64, and is composed of a high 24-bit company ID given by the "IEEE Registration Authority" and a 24-bit extension ID given by a company or an organization that is granted the company ID. For example, the address of an Ethernet card is in EUI-48 format, where the upper 24 bits of the 48 bits are the company ID representing the Ethernet card company, and the lower 24 bits are the extension IDs, which are the serial numbers of the Ethernet card. There is a tendency to use the EUI-64 format with a larger extension ID field than the EUI-48 format. Therefore, the EUI-48 format, which is the Ethernet card identifier information, is widely used in the EUI-64 format. In IPv6, EUI-64 format is used as IID (Interface IDentifier), which is the lower 64 bits, in automatic configuration of IPv6 address of network device.

1 is a diagram illustrating a basic IPv6 unicast address structure, and FIG. 2 is a diagram illustrating a method of converting an EUI-48 MAC address, which is a network device address, into an EUI-64 IID. Note that in FIG. 2, the "Universal / Local (U / L) bit" in the sixth from the highest 24-bit MSB (Most Significant Bit) of the EUI-64 format must be made unconditionally 1. This is to indicate "Globally unique IPv6 IID". The present invention conforms to this method for converting an EUI-48 format network device address to an EUI-64 format whether the domain name is mapped to an IPv6 address or an IPv4 address.

The present invention has been made to solve the above-described drawbacks, each terminal automatically generates its own domain name in the network without a network manager, such as home network or Ad-hoc network and exchange domain name between terminals The purpose is to provide a unique domain name generation method based on the network device address.

In order to achieve the above object, the present invention provides a method for generating a unique domain name for each terminal connected to a network, the method comprising: a first step of storing a user ID in a pUser_id variable and storing domain information in a pDomain variable; Attaching an "EUI-64" string and a "." To a domain stored in the pDomain variable; Storing the network device address in a pEui_48 variable; A fourth step of converting the value stored in the pEui_48 variable into an EUI-64 format and storing the value in the pEui_64 variable; And a fifth step of storing the domain name generated by combining the pUser_id, pEui_64 variable, and pDomain variable in the pDomain_Name variable.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

3 is a block diagram illustrating a network configuration of terminals participating in domain name generation according to the present invention, wherein terminals 1 to 5 (10 to 18) participating in domain name generation constitute a network.

In the figure, terminals 1 to 5 (10 to 18) constituting the network automatically generate domain names independently with the network device address, which is the only information they have, without the help of any server or network administrator.

FIG. 4 is a diagram illustrating a structure of a domain name of the present invention and a domain name embodiment of the present invention including a user ID, an EUI-64 IID of a network device address, and a domain to which a terminal belongs, using FIG. 2. The domain name is composed of a user ID of the terminal, a network device address, and a domain to which the terminal belongs.

5 is a flowchart illustrating step-by-step creation of the domain name of FIG. 4.

First, the domain ID configuration file "domain-name.conf", in which the user ID and the domain information to which the terminal belongs, is opened to read the user ID and domain information (step S10).

The user ID is stored in the pUser_id variable and the domain information is stored in the pDomain variable (step S12).

The string "EUI-64" and "." before the domain stored in the pDomain variable. Paste the character string (step S14). The reason for prefixing the EUI-64 string with the domain stored in the pDomain variable is to explicitly indicate that the domain name is based on the network device address. For reference, the domain name including the "EUI-64" string cannot be set manually. Doing so ensures that the domain name is unique without performing domain name redundancy check after generating the domain name based on the network device address.

The network device address is read from the system and stored in the variable pEui_48 (step S16).

The MAC address of the EUI-48 format, which is the network device address stored in the pEui_48 variable, is converted into the EUI-64 format and stored in the variable pEui_64 variable (step S18). In order to prevent the exposure of user terminal network device address information included in the EUI-64 IID stored in the pEui_64 variable, a security service should be used.

Then, the domain name generated by combining the pUser_id, the pEui_64 variable, and the pDomain variable is stored in the pDomain_Name variable (step S20).

According to an embodiment of the present invention, when the user ID is "PAUL", the EUI-64 IID of the network device address is "34-56-78-9A-BC-DE" and the domain information to which the user belongs is "ADHOC". The domain name of the terminal is "PAUL.36-56-78-FF-FE-9A-BC-DE.EUI-64.ADHOC" as shown in the lower figure of FIG. This domain name is guaranteed uniqueness in the domain ADHOC to which the terminal belongs.

FIG. 6 is a flowchart illustrating a step-by-step operation of a name server that performs a DNS service for a domain name generated through FIG. 5.

First, a unique domain name is generated based on each network device address of the terminal (step S30).

A DNS resource record is generated with the domain name and the IP address of the network device and stored in the DNS zone file name.db (step S32). The resource record of step S32 is a record that stores IP address information associated with a domain name. Representative types of resource records include A type records that record IPv4 addresses and AAAA type records that record IPv6 addresses.

Join the multicast group for the DNS service (step S34). The reason for joining the multicast group for the DNS service in step S34 is to process the DNS service request when the counterpart terminal makes a DNS service request for an arbitrary object. Suppose there are three terminals A, B, and C in one subnet. Assume that each terminal uses the same user ID of "PAUL". Even if all three terminals use the same user ID, since the EUI-64 IIDs are different from each other, a unique domain name can be generated. Each terminal executes its own name server, and each name server generates a domain name as shown in FIG. 6 and combines an A or AAAA type resource record with an IP (IPv4 or IPv6) address assigned to the terminal's network device. Save to db To determine the domain name of the other terminal, the three terminals may use the type value of the DNS query 255. The type value 255 is used when the sender asks the other party to inform them of all the resource records they have. By sending such a query by multicast, it is possible to find out the domain names and IP addresses of all the terminals in the domain network where the terminals exist. Therefore, each nameserver must join a multicast group corresponding to a specific multicast address for the DNS service. The multicast address used to find the other party's domain name can be defined as follows. In IPv4 multicast, one can be selected in an IPv4 multicast address block, and in IPv6 multicast, one can be selected in an IPv6 multicast block. The UDP port number for multicast can also be set in common.

Wait for DNS query (step S36).

Step 5 identifies the type of DNS query when the DNS query is received (step S38).

As a result of the classification in step S38, if the DNS query is a DNS query for a specific resource record for its domain name, the response corresponding to the query is transmitted to the sender (query) who sent the query and the flow returns to step S36 (step 40). ).

As a result of the discrimination in step S38, if the DNS query is a DNS query requesting all resource records for its domain name, all resource records are sent to the query word and the flow returns to step S36 (step 42).

As described above, the present invention allows a terminal to use its own desired user ID without administrator's intervention in an environment where a network administrator or a centralized authorized DNS server (name server) is not operated. Since the domain name can be automatically generated, it is possible to implement the automation of DNS service in the ad hoc network which is temporarily formed by the home network or mobile terminals composed of information appliances. Not only can the DNS service be automated, it also reduces the overhead and cost of DNS service management.

Claims (3)

In the method for each terminal connected to the network to generate its own domain name, A first step of storing a user ID in a variable pUser_id and storing domain information in a pDomain variable; Attaching an "EUI-64" string and a "." To a domain stored in the pDomain variable; Storing the network device address in a pEui_48 variable; A fourth step of converting the value stored in the pEui_48 variable into an EUI-64 format and storing the value in the pEui_64 variable; And A fifth step of storing a domain name generated by combining the pUser_id, pEui_64 variable, and pDomain variable in a pDomain_Name variable Unique domain name generation method based on the network device address comprising a. The method of claim 1, And generating a unique domain name for each device when the number of network devices is plural. The method of claim 1, And generating a unique domain name based on the network device address in a fourth step, using a security service to prevent exposure of user terminal network device address information included in the EUI-64 IID stored in the pEui_64 variable.

Images