WO2012053163A1 - ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム - Google Patents
ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム Download PDFInfo
- Publication number
- WO2012053163A1 WO2012053163A1 PCT/JP2011/005688 JP2011005688W WO2012053163A1 WO 2012053163 A1 WO2012053163 A1 WO 2012053163A1 JP 2011005688 W JP2011005688 W JP 2011005688W WO 2012053163 A1 WO2012053163 A1 WO 2012053163A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- address
- entry
- record type
- terminal device
- name
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- 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/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/686—Types of network addresses using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks
Definitions
- the present invention relates to a name database server, a name resolution system, an entry search method, a name resolution method, and a name database server used when performing name resolution in a communication environment in which IPv4 (Internet Protocol version 4) and IPv6 (Internet Protocol version 6) are mixed. It relates to an entry search program.
- IPv4 Internet Protocol version 4
- IPv6 Internet Protocol version 6
- IPv6 communication environment has been newly introduced on the Internet that started with the IPv4 communication environment.
- the current Internet is in the process of introducing an IPv6 environment. Therefore, in the introduction process, a communication device that supports only IPv4, a communication device in which a part of the function corresponding to IPv6 is implemented in addition to the function that supports IPv4, and a function that supports IPv6 are completely implemented.
- a plurality of types of communication devices such as communication devices that can use all the functions corresponding to IPv4 and IPv6 are mixed.
- FIG. 15 is an explanatory diagram when name resolution is performed in an IPv4-only communication environment.
- FIG. 15 shows that two entries of IPv4 addresses p and q having a record type “A” are registered in a DNS (Domain Name System) server for the host name “hostX”.
- DNS Domain Name System
- the DNS server searches for an entry including the IPv4 address corresponding to the hostX. To do. Then, the DNS server transmits a packet including the searched IPv4 address to the client terminal.
- the DNS server transmits a packet including addresses p and q as the IPv4 address of hostX to the client terminal.
- a DNS query packet a packet that specifies a host name and a record type and inquires an address corresponding to the host name.
- FIG. 16 is an explanatory diagram illustrating an example of information stored in the DNS server in a communication environment in which IPv4 and IPv6 coexist.
- the record type of the IPv6 address is described as “AAAA”
- the record type of the IPv4 address is described as “A”.
- FIG. 16 shows that the host name “hostX” has two IPv4 addresses p and q entries with a record type “A” and two IPv6 addresses s and t entries with a record type “AAAA”. That is, a total of four entries are registered in a DNS (Domain Name System) server.
- DNS Domain Name System
- resolver Library which is a set of lower APIs that perform primitive processing, is used.
- the resolver library includes a command (for example, nslookup, dig, host, etc.) for performing a low-level process that directly extracts data stored in a database provided on the server side in the DNS.
- a communication application used in the userland generally uses a high-level API without directly calling the resolver library.
- the resolver library is used in the high-level API, the user does not need to be aware of the internal API.
- getbyname () was used as a high-level API.
- getbyname () corresponding to an IPv4 only communication environment is no longer used, and now getaddrinfo () is used.
- getaddrinfo () is a function corresponding to both IPv4 and IPv6 protocols (multiprotocol).
- a record type specifically, an address family representing the type of network address.
- IPv4 PF_INET
- IPv6 PF_INET6
- PF_UNSPEC PF_UNSPEC
- the userland application side is expected to be able to make inquiries without worrying about the record type.
- the DNS server side it is necessary to manage both IPv4 and IPv6 addresses. Therefore, in the event that the DNS server manages both IPv4 and IPv6 addresses, it is assumed that the client side makes an inquiry specifying PF_UNSPEC as the address family.
- a communication application is created without being aware of the record type (for example, specifying PF_UNSPEC).
- the resolver library when called from the high-level API, it specifies the record type for name resolution and inquires the DNS server for the address. This is because the DNS server needs an address and a record type when searching for an entry.
- FIGS. 17 to 21 are explanatory diagrams showing an operation of inquiring an address to a DNS server in a communication environment in which IPv4 and IPv6 are mixed.
- an entry including the IPv4 address is referred to as an A record
- an entry including the IPv6 address is referred to as an AAAA record.
- the method shown in FIG. 17 is a method in which the DNS server is first inquired of the A record corresponding to the host name, and after the response is returned (that is, after waiting until it returns), the AAAA record is inquired. .
- the client transmits a DNS query packet in which the host name “hostX” and the record type “A” are specified to the DNS server.
- the DNS server searches for the corresponding IPv4 addresses p and q, and transmits a packet including the searched addresses to the client.
- the client that has received the packet including the IPv4 address transmits a DNS query packet designating the host name “hostX” and the record type “AAAA” to the DNS server.
- the DNS server searches for the corresponding IPv6 addresses s and t, and transmits a packet including the searched addresses to the client.
- the method shown in FIG. 18 is a method in which the DNS server is first inquired about the A record corresponding to the host name, and it is determined whether or not to inquire the AAAA record according to the response content returned. That is, the method shown in FIG. 18 is different from the method shown in FIG. 17 in that it is determined whether or not an AAAAA record is inquired based on the response contents of the IPv4 addresses p and q.
- the client transmits a DNS query packet in which the host name “hostX” and the record type “A” are specified to the DNS server.
- the DNS server searches for the corresponding IPv4 addresses p and q, and transmits a packet including the searched addresses to the client.
- the client that has received the packet including the IPv4 address determines whether or not to transmit a DNS query packet specifying the host name “hostX” and the record type “AAAA” to the DNS server according to the content included in the packet. If it is determined that the DNS query packet is transmitted to the DNS server, the subsequent processing is the same as the method shown in FIG.
- the method shown in FIG. 19 is a method in which the DNS server is first inquired of the A record corresponding to the host name, and the AAAA record is inquired without waiting for the response.
- the client transmits a DNS query packet specifying the host name “hostX” and the record type “A” to the DNS server.
- the client transmits a DNS query packet specifying the host name “hostX” and the record type “AAAA” to the DNS server.
- the content of the packet sent from the DNS server to the client in response to the received DNS query packet is the same as the content shown in FIG.
- the method shown in FIG. 20 is a method in which the DNS server is first inquired of the AAAA record corresponding to the host name, and after the response is returned, the A record is inquired. That is, the method shown in FIG. 20 is different from the method shown in FIG. 17 in that the order of inquiring the A record and the AAAA record is reversed. Specifically, first, the client transmits a DNS query packet specifying the host name “hostX” and the record type “AAAA” to the DNS server. Then, the DNS server searches for the corresponding IPv6 addresses s and t, and transmits a packet including the searched addresses to the client.
- the client that has received the packet including the IPv6 address transmits a DNS query packet designating the host name “hostX” and the record type “A” to the DNS server. Then, the DNS server searches for the corresponding IPv4 addresses p and q, and transmits a packet including the searched addresses to the client.
- the method shown in FIG. 21 is a method in which the DNS server is first inquired of the AAAA record corresponding to the host name, and the A record is inquired without waiting for the response.
- the client transmits a DNS query packet specifying the host name “hostX” and the record type “AAAA” to the DNS server.
- the client transmits a DNS query packet designating the host name “hostX” and the record type “A” to the DNS server.
- the content of the packet sent from the DNS server to the client in response to the received DNS query packet is the same as the content shown in FIG.
- the client when the DNS server stores both IPv4 address and IPv6 address entries for the host name, the client sends a DNS query packet that specifies the record type of the host name and IPv4 address, and the host name and IPv6 address. A DNS query packet designating the record type is transmitted. In this way, the client can acquire both the IPv6 address and the IPv4 address for the host name.
- Patent Document 1 describes a communication device that performs name resolution in an environment in which IPv4 addresses and IPv6 addresses are mixed.
- the communication apparatus described in Patent Document 1 requests name resolution from a DNS server that performs name resolution in an IPv4 address space.
- the communication device requests the DNS proxy server that makes an inquiry to the DNS server that performs name resolution in the IPv6 address space to request name resolution again.
- each server since each server returns a response to each inquiry, the client cannot collect response contents at once. Therefore, it takes more time to complete the response by waiting for the other to respond. Further, assuming that a packet used for one of the inquiries is lost, the processing considering each response content is further complicated. Due to this complexity, problems that were not initially envisioned may occur.
- inquiries are generated a plurality of times depending on the response content of one of the inquiries, as in the method shown in FIG. It is desirable that name resolution can be performed for addresses of a plurality of record types with a single inquiry without such a complicated configuration.
- the present invention provides a name database server, a name resolution system, an entry search method, which can perform name resolution for both IPv4 and IPv6 by simply inquiring a host name even in a communication environment in which IPv4 and IPv6 are mixed.
- An object is to provide a name resolution method and an entry search program.
- the name database server transmits a node information storage means for storing an entry in which an address and a record type are associated with a host name, and transmits a record type and a host name to be resolved among the entries.
- An address conversion unit for converting an address of a record type different from the record type received from the terminal device inquiring about an address corresponding to the host name into an address of the record type to be received based on a predetermined rule; and a node information storage unit.
- An entry search means for specifying an entry corresponding to the host name received from the terminal device by searching, and a search result transmission means for transmitting an address included in the specified entry to the terminal device. To do.
- a name resolution system includes a terminal device that inquires about an address for a host name, and a name database server that receives an inquiry from the terminal device.
- a node information storage means for storing an entry in which the address and the record type are associated with the host name, and an address inquiry means for inquiring an address corresponding to the host name.
- the entry search method transmits a record type and a host name to be resolved among the entries stored in the node information storage means for storing an entry in which an address and a record type are associated with a host name. Then, the address of the record type different from the record type received from the terminal device inquiring about the address corresponding to the host name is converted to the address of the record type to be received based on a predetermined rule, and the node information storage means is searched. Thus, an entry corresponding to the host name received from the terminal device is specified, and an address included in the specified entry is transmitted to the terminal device.
- a terminal device that inquires an address for a host name sends a record type and a host name to be resolved to a name database server, and inquires about an address corresponding to the host name.
- the name database server stores a record type address different from the record type received from the terminal device among the entries stored in the node information storage means for storing the entry in which the address and the record type are associated with the host name.
- the name database server searches the node information storage means to identify an entry corresponding to the host name received from the terminal device, and the name database server , Included in the identified entry And transmits that address to the terminal device.
- An entry search program is an entry search program applied to a computer having node information storage means for storing an entry in which an address and a record type are associated with a host name.
- the address of the record type that receives the address of the record type that is different from the record type received from the terminal device that sends the host name to be resolved and inquires about the address corresponding to the host name, based on a predetermined rule Address conversion processing for conversion to the node information, entry search processing for specifying an entry corresponding to the host name received from the terminal device by searching the node information storage means, and sending the address contained in the specified entry to the terminal device Execute search result transmission process And wherein the door.
- name resolution can be performed for both IPv4 and IPv6 by inquiring the host name once.
- FIG. 1 is an explanatory diagram illustrating an example of an operation for performing name resolution.
- a DNS in which a client designates a host name (“hostX” in FIG. 1) and a record type (“AAAA + A” in FIG. 1) to be resolved.
- a query packet is transmitted to the DNS server.
- the record type “AAAA + A” specified here is a virtual record type that is different from the record type stored in the DNS server, such as “A” or “AAAA”.
- Arbitrary information can be set in the virtual record type.
- a record type that does not exist in the existing DNS may be newly defined, and information representing the record type may be used as a virtual record type.
- the virtual record type is described as “AAAA + A”.
- the virtual record type is not limited to one type of “AAAA + A”, and there may be a plurality of types.
- This virtual record type is predetermined by the user or the like.
- the virtual record type is a record type that is specified in a part that specifies a record in a query packet, and can also be referred to as a record type that is not defined in DNS.
- the DNS server that has received the DNS query packet determines a record type to be searched according to a rule determined in advance according to the designated virtual record type “AAAA + A”. Then, the DNS server searches for an entry corresponding to the determined record type and the received host name. In the example shown in FIG. 1, entries of record types “AAAA” and “A” are searched. Then, the DNS server transmits a reply packet including the IPv6 address and the IPv4 address (s, t, p, q in FIG. 1) included in the searched entry to the client.
- the name resolution system sends a packet specifying information (for example, host name or address; hereinafter referred to as entry specifying information) and record type “AAAAA + A” to the DNS server.
- a packet including corresponding node information for example, an IPv6 address, an IPv4 address, and a host name
- corresponding node information for example, an IPv6 address, an IPv4 address, and a host name
- the name resolution system according to the present embodiment is also applicable to the case where the corresponding host name is resolved from the IP address (in the case of reverse lookup). The contents of the name resolution system in the first embodiment will be described in detail below.
- FIG. 2 is a block diagram showing an example of the name resolution system in the first embodiment of the present invention.
- the name resolution system in the present embodiment includes a terminal device 10 and a name database server 20.
- the name database server 20 is realized by, for example, a DNS server.
- the name database server 20 is not limited to a DNS server.
- the terminal device 10 includes an address inquiry unit 11.
- the address inquiry means 11 transmits a virtual record type and entry specifying information (for example, a host name or address to be resolved) to the name database server 20 and inquires for corresponding node information.
- a virtual record type predetermined information that does not exist in the record type stored in the node information storage unit 21 to be described later (that is, “AAAA + A” described above) is designated.
- the address inquiry means 11 is realized by a CPU of a computer (terminal device 10) that operates according to a program, for example.
- the entry specifying information transmitted from the address inquiry means 11 to the name database server 20 is not limited to the host name, address, and virtual record type.
- the address inquiry unit 11 may transmit the address of the terminal device 10 itself to the name database server 20.
- the record type that the address inquiry unit 11 inquires of the name database server 20 is specified by, for example, another high-level API (not shown).
- the name database server 20 includes node information storage means 21, search target record determination means 22, entry search means 23, and search result transmission means 24.
- the node information storage means 21 stores an entry of node information in which at least an address and a record type are associated with a host name. Specifically, the node information storage unit 21 stores an entry in which at least an IPv6 address and an IPv4 address are associated with a host name.
- the node information storage unit 21 is realized by, for example, a magnetic disk. The information associated with each address and record type is not limited to the host name.
- the node information storage unit 21 may store an entry in which other information indicating domain host information is associated with each address and record type, such as a zone file.
- the entries stored in the node information storage unit 21 are sequentially updated using a mechanism such as DNS dynamic update.
- the search target record determining means 22 determines the record type of the entry to be searched from the virtual record type received from the terminal device 10. Specifically, a rule (hereinafter referred to as a search rule) that defines a record type to be searched according to a virtual record type is determined in advance. The search target record determining means 22 determines the record type of the entry to be searched from the received virtual record type according to the search rule. Specifically, as a search rule, “when the character string“ AAAAA + A ”is designated as the record type, the record types to be searched are set to“ AAAA ”and“ A ”” is set. By defining in this way, even when the entry search means 23 to be described later receives the virtual record type “AAAA + A”, it is possible to search for entries of the record types “AAAAA” and “A”.
- a search rule “when the character string“ AAAAA + A ”is designated as the record type, the record types to be searched are set to“ AAAA ”and“ A ”” is set.
- the entry search unit 23 searches the node information storage unit 21 to specify an entry corresponding to the received entry specifying information and having the record type determined by the search target record determining unit 22. For example, it is assumed that the search target record determining unit 22 determines the record types of the entries to be searched as “AAAA” and “A”. In this case, the entry search unit 23 searches the node information storage unit 21 and specifies an entry including the IPv4 address and the IPv6 address corresponding to the host name received from the terminal device 10.
- the virtual record type specified in this way can be said to be information for specifying the record type to be searched. Furthermore, this virtual record type can also be referred to as information for instructing the DNS server to search. That is, it can be said that this record type “AAAA + A” plays a role of a command for instructing the DNS server of a record type to be searched. Further, when a query is made, a record type different from the record type stored in the DNS server is used, so that the influence on the existing mechanism can be suppressed.
- the search result transmission unit 24 transmits the node information included in the entry specified by the entry search unit 23 to the terminal device 10. If the target entry does not exist, the search result transmission unit 24 may transmit a packet including information indicating that the node information corresponding to the host name does not exist to the terminal device 10.
- the search target record determination unit 22, the entry search unit 23, and the search result transmission unit 24 are realized by a CPU of a computer that operates according to a program (entry search program).
- the program is stored in a storage unit (not shown) of the name database server 20, and the CPU reads the program and, as the search target record determination unit 22, the entry search unit 23, and the search result transmission unit 24, according to the program. It may work. Further, the search target record determination unit 22, the entry search unit 23, and the search result transmission unit 24 may be realized by dedicated hardware, respectively.
- the DNS server returns both the IPv4 address and the IPv6 address to the client when an address inquiry is made from the client by designating the host name and the record type “AAAA + A”.
- the client corresponds to the terminal device 10 and the DNS server corresponds to the name database server 20.
- FIG. 3 is a sequence diagram showing an example of an operation for performing name resolution.
- the client address inquiry means 11 sends a DNS query packet designating the host name and the virtual record type “AAAA + A” to the DNS server to inquire about the address for the host name (step S1).
- the search target record determining unit 22 of the DNS server determines the record types to be searched as “AAAA” and “A” according to a predetermined search rule. (Step S2).
- the entry search means 23 searches the node information storage means 21 and identifies entries of record types “AAAA” and “A” corresponding to the received host name (step S3). Specifically, the entry search means 23 specifies an entry including an IPv4 address and an IPv6 address.
- the search result transmission unit 24 transmits a packet including the IPv4 address and the IPv6 address of the entry specified by the entry search unit 23 to the client (step S4).
- the address inquiry unit 11 of the terminal device 10 transmits the virtual record type and the entry specifying information to the name database server 20, and the node information corresponding to the entry specifying information.
- the search target record determining means 22 of the name database server 20 determines the record type of the entry to be searched based on the search rule that is a rule that defines the record type to be searched according to the virtual record type.
- the entry search unit 23 searches the node information storage unit 21 to specify an entry corresponding to the received entry specifying information and having the record type determined by the search target record determining unit 22. Then, the search result transmission unit 24 transmits the node information included in the entry specified by the entry search unit 23 to the terminal device 10.
- node information of multiple record types can be acquired with a single inquiry.
- name resolution can be performed for both IPv4 and IPv6 by inquiring the host name once.
- the addresses of a plurality of record types both IPv4 and IPv6 corresponding to the host name can be acquired by transmitting once a DNS query packet designating one record type.
- the processing on the client side is efficient because it is completed with a single inquiry. Moreover, it can suppress that various problems generate
- FIG. 4 is an explanatory diagram illustrating an example of an operation for performing name resolution.
- a client specifies a host name to be resolved (“hostX” in FIG. 4) and an IPv6 address record type (“AAAA” in FIG. 4).
- the designated DNS query packet is transmitted to the DNS server.
- the DNS server that has received the DNS query packet searches not only the entry of the specified record type “AAAA” but also the entry of the record type “A” among the received host name entries.
- the addresses p, q, s, and t included in the entry that matches the host name “hostX” are specified.
- the DNS server converts the IPv4 addresses p and q having the record type “A” into IPv6 addresses that are addresses of the received record type.
- the addresses p and q converted into IPv6 addresses are denoted as p 'and q'.
- the DNS server transmits a packet including these IPv6 addresses s, t, p ′, q ′ to the client.
- the client that has received the IPv6 address converts the converted addresses p ′ and q ′ back to the IPv4 addresses p and q before conversion.
- IPv4 mapped Address As a method of converting an IPv4 address into an IPv6 address, for example, a method of converting an IPv4 address into IPv4 mapped IPv6 Address (hereinafter referred to as IPv4 mapped Address) is used.
- IPv4 mapped Address a method of converting an IPv4 address into IPv4 mapped IPv6 Address (hereinafter referred to as IPv4 mapped Address) is used.
- IPv4 mapped Address IPv4 mapped Address
- the conversion process from IPv4 mapped Address to IPv4 address is normally performed by the kernel. Therefore, by converting the IPv4 address to IPv4 mapped Address, the return conversion process becomes unnecessary in the application in the user land on the client side.
- the name resolution system transmits a packet that specifies the host name and the record type of the IPv6 address to the DNS server only once. Can be acquired at once with the specified record type. Furthermore, by converting the converted address back to the address before conversion, the converted address can be used as the original address.
- the contents of the name resolution system in the second embodiment will be described in detail below.
- FIG. 5 is a block diagram showing an example of the name resolution system in the second embodiment of the present invention.
- symbol same as FIG. 2 is attached
- subjected and description is abbreviate
- the name resolution system in the present embodiment includes a terminal device 30 and a name database server 40.
- the name database server 40 is realized by, for example, a DNS server.
- the name database server 40 is not limited to a DNS server.
- the name database server 40 includes node information storage means 21, entry search means 41, address conversion means 42, and search result transmission means 43. Note that the node information storage unit 21 is the same as that in the first embodiment, and a description thereof will be omitted.
- the entry search means 41 specifies an entry corresponding to the host name received from the terminal device 30 by searching the node information storage means 21. Specifically, when a packet indicating the record type “AAAA” is received from the terminal device 30, the entry search unit 41 specifies an entry corresponding to the received host name and record type “AAAA”. Further, the entry search means 41 specifies an entry corresponding to the received host name and record type “A”.
- the address conversion unit 42 selects an address of a record type different from the record type received from the terminal device 30 among the addresses included in the entry specified by the entry search unit 41 based on a predetermined rule. Convert to Specifically, when the packet indicating the record type “AAAA” is received from the terminal device 30, the address conversion unit 42 has the record type “A” among the addresses included in the entry specified by the entry search unit 41.
- the address (IPv4 address) is converted into an address (IPv6 address) of record type “AAAA” based on a predetermined rule.
- a rule for converting an address of a record type different from the received record type into an address of the received record type may be determined in advance for each record type.
- an IPv4 address is converted into an IPv4 mapped Address.
- the address conversion unit 42 converts the IPv4 address specified by the entry search unit 41 into an IPv6 address based on the format defined as IPv4 mapped Address. To do.
- IPv4 mapped Address is described in Reference Document 1 “2.5.5.2.5.2IPv4-Mapped IPv6 Address” below.
- usage method (function) of IPv4 mapped Address is described in Reference Document 2 below. Therefore, detailed description is omitted.
- the method of converting an IPv4 address into an IPv6 address is not limited to the method of converting an IPv4 address into an IPv4 mapped Address.
- Other conversion algorithms may be used as long as the method can extract the original IPv4 address on the client side (terminal device 30).
- the specification for the conversion method is not limited to the above format as long as it is determined between devices that transmit and receive data.
- an IPv4 address may be converted into an IPv6 address by adding an arbitrary bit pattern before and after the IPv4 address. This is because the IPv6 address space is very large and it is easy to include an IPv4 address in the IPv6 address space.
- the search result transmission means 43 transmits the address corresponding to the received host name and record type to the terminal device 30. Specifically, the search result transmission unit 43 receives the address converted by the address conversion unit 42 and the address not converted by the address conversion unit 42 among the addresses included in the entry specified by the entry search unit 41. 30. If the entry search unit 41 cannot identify the entry, the search result transmission unit 43 may transmit a packet including information indicating that the address corresponding to the host name does not exist to the terminal device 30.
- the name database server 40 in the present embodiment converts the address in response to the inquiry from the terminal device 30. Therefore, the name resolution method according to the present embodiment can be called a dynamic conversion method. For example, when information that is known for the first time when a DNS query is generated is used in a rule for address conversion, this dynamic conversion method is effective.
- the entry search means 41, the address conversion means 42, and the search result transmission means 43 are realized by a CPU of a computer that operates according to a program (entry search program). Further, the entry search means 41, the address conversion means 42, and the search result transmission means 43 may each be realized by dedicated hardware.
- the terminal device 30 includes an address inquiry unit 31 and a translation address retranslation unit 32.
- the address inquiry means 31 transmits the record type and the host name to be resolved to the name database server 40 and inquires about the address for the host name. For example, a record type “AAAA” indicating an IPv6 address is designated as the record type.
- the translated address re-converting means 32 converts an address converted based on a predetermined rule among addresses included in the packet received from the name database server 40 into an address before conversion. Specifically, the translated address retranslating unit 32 converts the address converted from the IPv4 address to the IPv6 address into the IPv4 address before conversion.
- the converted address re-converting means 32 may specify an address in a predetermined format among the received addresses as an address to be converted into an address before conversion. For example, it is assumed that the address conversion unit 42 converts an IPv4 address into an IPv6 address according to the IPv4 mapped Address format. In this case, the translated address retranslating means 32 may specify an address in the IPv4 mapped Address format among the received IPv6 addresses as the address to be translated. At this time, the translated address retranslating means 32 may convert the IPv6 address in the IPv4 mapped Address format into the IPv4 address before conversion.
- the kernel determines whether the address is IPv4 mapped Address. When the address is determined to be IPv4 mapped Address, the kernel recognizes this address and converts this address into an IPv4 address.
- This function is usually implemented in general kernels. Therefore, when the existing structure (kernel) and IPv4 mapped Address are used, the client application does not need a new back conversion process (that is, a conversion process from an IPv6 address to an IPv4 address). Therefore, on the communication application side, it is not necessary to be aware of whether the IPv6 address is an IPv4 mapped Address or a normal IPv6 address, and it is not necessary to perform a conversion process or the like. That is, even if IPv4 mapped Address and normal IPv6 address are mixed in the IPv6 address, the communication application side can handle the IPv6 address in the same manner as the normal IPv6 address.
- IPv4 mapped Address when IPv4 mapped Address is used on the communication application side, it can be said that an IPv6 address is automatically converted to an IPv4 address. For these reasons, when converting an IPv4 address into an IPv6 address, it is preferable to convert the IPv4 address into an IPv4 mapped Address.
- address inquiry means 31 is the same as the address inquiry means 11 in the first embodiment, and a description thereof will be omitted.
- the address inquiry means 31 and the translation address re-translation means 32 are realized by a CPU of a computer that operates according to a program (name resolution program). Further, each of the address inquiry unit 31 and the translation address retranslation unit 32 may be realized by dedicated hardware.
- the DNS server returns the IPv6 address and the address obtained by converting the IPv4 address to the IPv6 address to the client.
- movement which performs is demonstrated.
- the client corresponds to the terminal device 30 and the DNS server corresponds to the name database server 40.
- FIG. 6 is a sequence diagram showing an example of an operation for performing name resolution.
- the client address inquiry means 31 sends a DNS query packet designating the host name and the record type “AAAA” to the DNS server to inquire about the address for the host name (step S11).
- the DNS server entry search means 41 searches the node information storage means 21 and identifies the entry corresponding to the received host name (step S12). Specifically, the entry search means 41 specifies an entry including an IPv6 address and an IPv4 address corresponding to the host name.
- the address conversion unit 42 converts the IPv4 address among the addresses included in the entry specified by the entry search unit 41 into an IPv6 address based on a predetermined rule (step S13).
- the search result transmission unit 43 transmits a packet including an address corresponding to the host name to the client (step S14).
- the translated address retranslating means 32 converts the IPv4 address converted to the IPv6 address among the addresses received from the DNS server into the IPv4 address before the conversion (step S15).
- the address inquiry unit 31 of the terminal device 30 transmits the record type and the host name to be resolved to the name database server 40 and corresponds to the host name. Queries the address.
- the entry search means 41 specifies an entry corresponding to the host name received from the terminal device 30 by searching the node information storage means 21.
- the address conversion unit 42 selects an address of a record type different from the record type received from the terminal device 30 among the addresses included in the entry specified by the entry search unit 41 based on a predetermined rule. Convert to Then, the search result transmission unit 43 transmits the received record type address included in the identified entry and the address converted by the address conversion unit 42 to the terminal device 30.
- the address inquiry means 31 sends the record type “AAAA” and the host name to be resolved to the name database server 40 and inquires about the address corresponding to the host name.
- the entry search unit 41 searches the node information storage unit 21 to identify an entry corresponding to the host name and record type “AAAA” received from the terminal device 30. Further, the entry search means 41 specifies an entry corresponding to the host name and record type “A” received from the terminal device 30.
- the address conversion unit 42 converts an IPv4 address into an IPv6 address based on a predetermined rule. Then, the search result transmission unit 43 transmits the IPv6 address included in the identified entry and the IPv6 address converted by the address conversion unit 42 to the terminal device 30.
- name resolution can be performed for both IPv4 and IPv6 by inquiring the host name once.
- the translated address re-converting means 32 converts the address converted based on a predetermined rule among the addresses received from the name database server 40 to the address before conversion. Therefore, the terminal device 30 can acquire the address of the requested record type and can use the address before conversion.
- the address conversion unit 42 may convert the IPv4 address extracted from the node information storage unit 21 into the IPv4 mapped Address when the record type indicating the IPv6 address is designated as the record type from the terminal device 30. .
- an IPv4 mapped Address and IPv4 address conversion function implemented by a normal kernel can be used. Therefore, it is not necessary to add a new back conversion process on the client application side. Therefore, it is possible to suppress the influence on a large number of existing client applications. Further, in this case, since it can be coped with only by implementing the function in the present embodiment on the name database server 40 (for example, DNS server) side, the influence range can be suppressed small.
- the address conversion means 42 when there is an inquiry about an address corresponding to the host name from the terminal device 30, the address conversion means 42 performs a process of converting the address.
- the address conversion means 42 performs a process (hereinafter referred to as a specific process) for making the inquiry result available only to a specific terminal device in addition to the process of converting the address.
- the translation address retranslation means 32 performs a process corresponding to the specific process.
- the process of making the inquiry result subjected to the specific process available is referred to as a return conversion process.
- the name database server 40 When the specification about the specific process is determined between the terminal device 30 and the name database server 40, the name database server 40 performs the specified process even if the terminal device 30 performs the specific process. Can recognize the return conversion processing for On the other hand, since the terminal device 30 that does not know the specific process by the name database server 40 does not know how to deal with the specific process, it cannot use the information on which the specific process has been performed. In this way, by making an arrangement for specific processing between the terminal device 30 and the name database server 40, the terminals that perform address conversion and specific processing are limited to the specific client (terminal device 30) that has made the arrangement. can do.
- the address conversion means 42 may perform a specific process that allows the return conversion process itself to be performed by any device. However, at that time, the address conversion unit 42 adds additional information that can be recognized only by the specific terminal device 30 to the information subjected to the return process. The address conversion unit 42 may add the additional information to the end of the information, for example, or may add it as a watermark. These methods can also be referred to as a check digit method or a flashing method. Only the terminal device 30 that recognizes the check digit method and the appearance method can use the additional information.
- the address conversion means 42 may perform a process of encrypting information as a specific process using a specific key possessed by the terminal device 30 that performs the return conversion process.
- ESP Encapsulating Security Payload
- AH Authentication Header Header
- the terminal device 30 may decrypt the information using a decryption key corresponding to a specific key possessed by the terminal device 30 as the back conversion process.
- the protocol used for the encryption process and the authentication process is not limited to the above contents.
- the name resolution system may use an authentication method based on challenge / response authentication for the specific processing.
- the terminal device 30 specifically, the address inquiry unit 31
- the name database server 40 for example, the address conversion unit 42
- the address inquiry unit 31 creates a response obtained by converting the received challenge and password according to a specific algorithm, and transmits the response to the name database server 40.
- the address conversion unit 42 creates a response in the same manner from the transmitted challenge and the password of the terminal device 30 registered in advance.
- the address conversion unit 42 performs address conversion when the response matches the response received from the terminal device 30.
- the name resolution system may use an authentication method using a check digit or an authentication method using a one-time password for the specific processing. Since an authentication method using challenge / response authentication, an authentication method using check digits, and an authentication method using a one-time password are widely known, detailed description thereof is omitted.
- the process of converting the IPv4 address described in the second embodiment into an IPv4 mapped Address is normally performed by the kernel. Therefore, userland applications need not be aware of this conversion process.
- the terminal device 30 performs processing other than the conversion processing to IPv4 mapped Address, the part that receives the DNS query return packet or the transmission destination of the return packet implements the return conversion processing.
- the reply packet will be received by the resolver library. For this reason, it is desirable that this back conversion process is implemented in the resolver library. It can be said that the resolver library that is not a kernel is a process in the userland. However, by implementing this return conversion process in the resolver library that is commonly used in communication applications, it is possible to reduce the effort of applying the return conversion process to individual communication applications.
- the name resolution system can be given new added value other than name resolution.
- FIG. 7 is an explanatory diagram illustrating an example of an operation for performing name resolution.
- the name resolution system according to the third embodiment creates in advance an entry in which an IPv4 address is converted to an IPv6 address when both an IPv6 address and an IPv4 address entry exist for the host name.
- FIG. 7 shows that the IPv4 addresses p and q are converted (statically converted) into IPv6 addresses p ′ and q ′ at a predetermined timing and held on a magnetic disk or the like.
- the shaded part in the table indicates the converted record.
- the client sends a DNS query packet in which a host name (“hostX” in FIG. 7) and an IPv6 address record type (“AAAA” in FIG. 7) for name resolution are specified.
- Send to server the DNS server that has received the DNS query packet searches the received host name and record type “AAAA”.
- the addresses s, t, p ′, q ′ of the entries of the host name “hostX” and the record type “AAAA” are specified.
- the DNS server transmits a packet including these IPv6 addresses s, t, p ′, q ′ to the client.
- the client that has received the IPv6 address converts the converted addresses p ′ and q ′ back to the IPv4 addresses p and q before conversion.
- IPv4 mapped Address As a method of converting an IPv4 address into an IPv6 address, for example, a method of converting an IPv4 address into IPv4 mapped IPv6 Address (hereinafter referred to as IPv4 mapped Address) is used. Since the conversion process from the IPv4 mapped Address to the IPv4 address is normally performed by the kernel, the conversion process from the IPv4 address to the IPv4 mapped Address eliminates the need for the back conversion process in the application in the user land on the client side.
- the name resolution system also transmits a packet that specifies the host name and the record type of the IPv6 address to the DNS server only once. Can be acquired at once with the specified record type. Furthermore, by converting the converted address back to the address before conversion, the converted address can be used as the original address.
- the contents of the name resolution system in the third embodiment will be described in detail below.
- FIG. 8 is a block diagram showing an example of the name resolution system in the third embodiment of the present invention.
- symbol same as FIG. 5 is attached
- subjected and description is abbreviate
- the name resolution system in the present embodiment includes a terminal device 30 and a name database server 50. Since the terminal device 30 is the same as that of the second embodiment, the description thereof is omitted.
- the name database server 50 includes node information storage means 21, translation address storage means 51, address translation means 52, entry search means 53, and search result transmission means 54. Note that the node information storage unit 21 is the same as in the first and second embodiments, and a description thereof will be omitted.
- the translated address storage unit 51 converts an IPv4 address stored in the node information storage unit 21 into an IPv6 address (hereinafter referred to as a translated address) and an IPv6 address stored in the node information storage unit 21. Stores an entry associated with a host name.
- the translation address storage unit 51 is realized by, for example, a magnetic disk. Note that the information associated with each address is not limited to the host name. Similar to the node information storage unit 21, the translation address storage unit 51 may store an entry in which other information indicating domain host information is associated with each address, like a zone file.
- the entries stored in the translated address storage unit 51 are stored by an address converting unit 52 described later.
- the address conversion means 52 converts the address of one record type among the addresses stored in the node information storage means 21 to an address of another record type based on a predetermined rule. Then, the address conversion unit 52 causes the conversion address storage unit 51 to store both the entry including the converted address and the entry including the unconverted address among the entries stored in the node information storage unit 21.
- the address conversion unit 52 converts the IPv4 address stored in the node information storage unit 21 into an IPv6 address based on a predetermined rule. Then, the address translation unit 52 stores both the entry including the translated IPv6 address (that is, the translation address) and the entry including the untranslated IPv6 address stored in the node information storage unit 21 in the translation address storage unit 51.
- the address conversion unit 52 converts the IPv4 address stored in the node information storage unit 21 into an IPv6 address based on a predetermined rule. Then, the address translation unit 52 stores both the entry including the translated IPv6 address (that is, the translation address) and the entry including the untranslated IPv6 address stored in the node information storage unit 21 in the translation address storage unit 51.
- the address conversion means 52 may convert the address every predetermined period or at a predetermined time. Alternatively, the address conversion unit 52 may convert the address at the timing when an entry is added to the node information storage unit 21.
- the entry that the address conversion unit 52 stores in the conversion address storage unit 51 may be a difference from the previous conversion process or the entire target entry.
- the entry search means 53 specifies the entry corresponding to the host name and record type received from the terminal device 30 by searching the translation address storage means 51. For example, when the record type “AAAA” is received from the terminal device 30, the entry search unit 53 selects an entry corresponding to the host name with the record type “AAAA” (that is, an entry including an IPv6 address). Identify.
- the search result transmission means 54 transmits an address corresponding to the host name to the terminal device 30. Specifically, the search result transmission unit 54 transmits the address included in the entry specified by the entry search unit 53 to the terminal device 30. If the entry search unit 53 cannot identify the entry, the search result transmission unit 54 may transmit information to the terminal device 30 that the address corresponding to the host name does not exist.
- This embodiment is different from the second embodiment in that the converted address is stored in the converted address storage unit 51 in advance. That is, the name database server 50 in the present embodiment converts and stores the address in advance regardless of whether there is an inquiry from the terminal device 30. Therefore, the name resolution method according to the present embodiment can be called a static conversion method.
- the case where the name database server 50 includes the node information storage unit 21 and the translation address storage unit 51 has been described.
- a mechanism for updating an entry in a zone file (corresponding to the node information storage means 21) when applied to a general DNS. No need to change.
- the name database server 50 may include only the node information storage means 21.
- the address conversion unit 52 when the DNS dynamic update is applied to update the entry of the zone file (corresponding to the node information storage unit 21), the address conversion unit 52 also converts the record type and converts the converted address.
- the included entry may be stored in the node information storage unit 21.
- the existing DNS can be used as it is.
- the address conversion means 52 may use a rule for converting an IPv4 address into an IPv4 mapped Address as a predetermined rule. This IPv4 mapped Address is obtained by converting an IPv4 address into an IPv6 address. Therefore, there is no problem in registering the converted address in the DNS database.
- the above-described method of converting an IPv4 address into an IPv6 address at any time and holding it at a predetermined timing can be referred to as a mixed conversion method.
- the substance of the mixed conversion method is a dynamic conversion method.
- the static conversion method can be regarded as a method of converting information in a file including address information (also referred to as a database information file) in advance (hereinafter referred to as a pre-conversion method).
- a pre-conversion method In the dynamic conversion method, there is no need to be aware of whether the information stored in the target database information is the information converted by the pre-conversion method or the method converted by the static conversion method. That is, it can be said that the static conversion method and the dynamic conversion method are independent conversion methods.
- the mixed conversion method can be said to be a method in which both the static conversion method and the dynamic conversion method are made effective.
- the name database server 50 includes an address conversion unit 52, which converts the address stored in the node information storage unit 21 at a predetermined timing and converts an entry including the converted address into a conversion address.
- an external device (not shown) may convert the address stored in the node information storage unit 21 at a predetermined timing and store the entry including the converted address in the conversion address storage unit 51.
- the name database server 50 itself may not include the address conversion unit 52.
- the address conversion unit 52, the entry search unit 53, and the search result transmission unit 54 are realized by a CPU of a computer that operates according to a program (entry search program). Further, the address conversion unit 52, the entry search unit 53, and the search result transmission unit 54 may each be realized by dedicated hardware.
- the DNS server returns the IPv6 address and the address obtained by converting the IPv4 address to the IPv6 address to the client.
- movement which performs is demonstrated.
- the client corresponds to the terminal device 30 and the DNS server corresponds to the name database server 50.
- FIG. 9 is a sequence diagram illustrating an example of an operation for performing name resolution.
- the address conversion unit 52 converts the IPv4 address stored in the node information storage unit 21 into an IPv6 address at a predetermined timing. Then, the address translation unit 52 stores the entry including the translated IPv6 address in the translation address storage unit 51 (step S21).
- the client address inquiry means 31 sends a DNS query packet designating the host name and the record type “AAAA” to the DNS server to inquire about the address for the host name (step S11).
- the entry search means 53 searches the translation address storage means 51 to identify the received host name and record type “AAAA” (step S22). Then, the search result transmission means 54 transmits a packet including the address of the identified entry to the client (Step S23).
- the translated address retranslating means 32 converts the IPv4 address converted to the IPv6 address among the addresses received from the DNS server into the IPv4 address before the conversion (step S15).
- the conversion address storage unit 51 converts the first record type address (IPv4 address) into the second record type address (IPv6 address) based on a predetermined rule.
- An entry in which the address (that is, the translation address) and its second record type are associated with the host name is stored.
- the entry search means 53 receives the second record type (IPv6 address) from the terminal device 30, the entry search means 53 searches the conversion address storage means 51 to search for the second record type (“ AAAA ")) entry.
- the search result transmission unit 54 transmits the address (IPv6 address) of the second record type included in the identified entry to the terminal device 30. Therefore, similarly to the effect of the first embodiment, even in a communication environment in which IPv4 and IPv6 are mixed, name resolution can be performed for both IPv4 and IPv6 by inquiring the host name once.
- the address converted by the name database server 50 in advance is stored. Therefore, in addition to the effects of the second embodiment, it is not necessary to perform conversion processing each time an inquiry is received from the terminal device 30. Therefore, the effect that the load of the name database server 50 (DNS server) is reduced can also be obtained.
- DNS server name database server
- the address conversion means 52 may convert the first record type address (IPv4 address) to the second record type address (IPv6 address) based on a predetermined rule. Then, the address conversion unit 52 may store the converted address in the node information storage unit 21.
- FIG. 10 is an explanatory diagram illustrating an example of an operation for performing name resolution.
- a client performs a name resolution target host name (“hostX” in FIG. 10) and a record type of IPv4 address and IPv6 address (“A” in FIG. 10).
- AAAA a record type of IPv4 address and IPv6 address
- the DNS server that has received the DNS query packet searches for entries of the designated record types “A” and “AAAA” from the received host name entries.
- FIG. 10 is an explanatory diagram illustrating an example of an operation for performing name resolution.
- the host name “hostX” and the addresses p, q, s, and t included in the entry that matches the specified record type are specified. Then, the DNS server transmits a packet including these addresses p, q, s, and t to the client.
- the name resolution system in the fourth embodiment acquires a packet including an address corresponding to the host name at a time by sending a packet specifying the host name and a plurality of record types to the DNS server once. can do.
- the name resolution system in the fourth embodiment since no conversion processing is performed on the address, it is not necessary for the client that receives the address to convert the received address.
- the contents of the name resolution system in the fourth embodiment will be described in detail.
- FIG. 11 is a block diagram showing an example of a name resolution system in the fourth embodiment of the present invention.
- symbol same as FIG. 2 is attached
- subjected and description is abbreviate
- the name resolution system in the present embodiment includes a terminal device 60 and a name database server 70.
- the name database server 70 is realized by a DNS server, for example.
- the name database server 70 is not limited to a DNS server.
- the terminal device 60 includes address inquiry means 61.
- the address inquiry means 61 transmits a plurality of record types together with the host name to the name database server 70, and inquires about the address for the host name.
- the record type to be transmitted the record type stored in the node information storage unit 21 is designated.
- the address inquiry unit 61 transmits “A” and “AAAA” (that is, a record type indicating an IPv4 address and a record type indicating an IPv6 address) to the name database server 70 together with the host name.
- the address inquiry means 61 is realized by a CPU of a computer (terminal device 60) that operates according to a program, for example.
- the name database server 70 includes node information storage means 21, entry search means 71, and search result transmission means 72. Note that the node information storage unit 21 is the same as that in the first embodiment, and a description thereof will be omitted.
- the entry search unit 71 searches the node information storage unit 21 to identify an entry of a record type that matches the host name received from the terminal device 60 and matches any of a plurality of record types. .
- the entry search means 71 receives from the terminal device 60 a packet including record types “A” and “AAAA” together with the host name.
- the entry search means 71 searches the node information storage means 21 to identify an entry corresponding to the host name and having the record type “A” or “AAAAA”.
- the search result transmission unit 72 transmits the address of the entry specified by the entry search unit 71 to the terminal device 60. If the target entry does not exist, the search result transmission unit 72 may transmit a packet including information indicating that the address corresponding to the host name does not exist to the terminal device 60.
- the entry search means 71 and the search result transmission means 72 are realized by a CPU of a computer that operates according to a program (entry search program). Further, each of the entry search means 71 and the search result transmission means 72 may be realized by dedicated hardware.
- the DNS server returns an IPv6 address and an IPv4 address to the client when an address inquiry is made from the client by designating the host name and record types “A” and “AAAA” will be described.
- the client corresponds to the terminal device 60
- the DNS server corresponds to the name database server 70.
- FIG. 12 is a sequence diagram illustrating an example of an operation for performing name resolution.
- the client address inquiry means 61 sends a DNS query packet designating the host name and record types “A” and “AAAA” to the DNS server to inquire about the address for the host name (step S31).
- the entry search means 71 searches the node information storage means 21 and is an entry corresponding to the host name, and the record type is “A” or “AAAA”. An entry is specified (step S32). Then, the search result transmission means 72 transmits a packet including the address of the identified entry to the client (Step S33).
- the address inquiry unit 61 transmits a plurality of record types to the name database server 70 together with the host name. Then, the entry search unit 71 searches the node information storage unit 21 to identify an entry that matches the received host name and matches any of a plurality of record types. Then, the search result transmission unit 72 transmits the address included in the identified entry to the terminal device 60.
- name resolution can be performed for both IPv4 and IPv6 by inquiring the host name once.
- the name database server 70 (server side) does not perform the conversion process, so the terminal device 60 (client side) performs the conversion process for returning the address. There is no need to do it.
- FIG. 13 is a block diagram showing an example of the minimum configuration of the name resolution system according to the present invention.
- FIG. 14 is a block diagram showing an example of the minimum configuration of the name database server according to the present invention.
- the name resolution system illustrated in FIG. 13 includes a terminal device 90 (for example, the terminal device 30) that makes an address inquiry for a host name, and a name database server 80 (for example, the name database server 40) that receives an inquiry from the terminal device 90. ).
- a terminal device 90 for example, the terminal device 30
- a name database server 80 for example, the name database server 40
- the terminal device 90 transmits a record type (for example, “AAAA”) and a host name to be subjected to name resolution to the name database server 80, and inquires for an address corresponding to the host name (for example, an address inquiry unit 81). Address inquiry means 31) is provided.
- a record type for example, “AAAA”
- a host name for example, “AAAA”
- Address inquiry means 31 is provided.
- the name database server 80 includes a node information storage unit 81 (for example, the node information storage unit 21) that stores an entry in which an address and a record type are associated with a host name, and among the entries, a record type (from the terminal device 90).
- a node information storage unit 81 for example, the node information storage unit 21
- an address conversion means 82 for example, an address of the record type received (for example, an IPv4 address) based on a predetermined rule, for example, an address of a record type different from “AAAA”) (for example, “A”)
- the address conversion means 42) and the entry information search means 83 for example, the entry search means 41 for specifying the entry corresponding to the host name received from the terminal device 90 by searching the node information storage means 81.
- node information storage unit 81 for example, the node information storage unit 21
- address conversion unit 82 for example, the address conversion unit 42
- entry search unit 83 for example, an entry
- Search means 41 and search result transmission means 84 (for example, search result transmission means 43) are provided.
- the contents of the node information storage means 81, the address conversion means 82, the entry search means 83, and the search result transmission means 84 are the same as those shown in FIG.
- the address conversion unit 82 selects an address of a record type different from the record type received from the terminal device from among the addresses included in the entry specified by the entry search unit 83 based on a predetermined rule.
- the search result transmitting unit 84 may convert the address into the address, and transmit the address of the received record type included in the identified entry and the address converted by the address converting unit 82 to the terminal device.
- the node information storage unit 81 stores at least an entry in which the IPv6 address and the IPv4 address are associated with the host name, and the entry search unit 83 receives the record type of the IPv6 address from the terminal device 90 and the target of name resolution.
- the node information storage unit 81 is searched, so that an entry corresponding to the host name received from the terminal device 90 and having a record type indicating an IPv6 address and / or an IPv4 address is obtained.
- the address conversion unit 82 converts the IPv4 address included in the entry specified by the entry search unit 83 into an IPv6 address based on a predetermined rule, and the search result transmission unit 84 specifies the entry search unit 83 An IPv6 address included in the entry; And IPv6 addresses converted by address conversion means 82 may be configured to be transmitted to the terminal device. Note that “IPv6 address and / or IPv4 address” represents “IPv6 address”, “IPv4 address”, or “both IPv6 address and IPv4 address”.
- the address converting unit 82 may convert the IPv4 address into an IPv4 mapped Address.
- the node information storage unit 81 (for example, the translation address storage unit 51) converts the first record type address (for example, IPv6 address) and the second record type address (IPv4 address) to the first one.
- the entry search means 83 (for example, the entry search means 53) receives the first record type from the terminal device 90, the conversion address that is the address of the record type is stored in association with the host name.
- the search result transmission unit 84 (for example, the search result transmission unit 54) is included in the specified entry.
- the first record type address may be transmitted to the terminal device 90.
- the address conversion unit 82 (for example, the address conversion unit 53) converts the address of the second record type into the address of the first record type based on a predetermined rule, and converts the address of the first record type. May be stored in the node information storage unit 81 (for example, the translated address storage unit 51 or the node information storage unit 21) in association with the host name.
- the node information storage unit 81 (for example, the translation address storage unit 51) stores at least the IPv6 address and the IPv6 address converted from the IPv4 address based on a predetermined rule in association with the host name, and the entry.
- the search means 83 (for example, the entry search means 53) receives the record type of the IPv6 address from the terminal device 90, the entry of the IPv6 address corresponding to the host name is specified by searching the node information storage means 81.
- the search result transmitting unit 84 may transmit the IPv6 address included in the specified entry to the terminal device.
- the node information storage unit 81 may store the IPv4 mapped Address converted from the IPv4 address in association with the host name as the IPv6 address.
- the present invention is preferably applied to a name database server used when performing name resolution in a communication environment in which IPv4 and IPv6 are mixed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Probability & Statistics with Applications (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Fuzzy Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
まず、図1を参照して、第1の実施形態における名前解決システムの概要を説明する。図1は、名前解決を行う動作の例を示す説明図である。第1の実施形態における名前解決システムでは、まず、クライアントが、名前解決を行う対象のホスト名(図1では、「hostX」)とレコードタイプ(図1では、「AAAA+A」)とを指定したDNSクエリパケットをDNSサーバに対して送信する。ここで指定されるレコードタイプ「AAAA+A」とは、「A」や「AAAA」といったDNSサーバに記憶されるレコードタイプとは異なる仮想のレコードタイプである。
次に、図4を参照して、第2の実施形態における名前解決システムの概要を説明する。図4は、名前解決を行う動作の例を示す説明図である。第2の実施形態における名前解決システムでは、まず、クライアントが、名前解決を行う対象のホスト名(図4では、「hostX」)とIPv6アドレスのレコードタイプ(図4では、「AAAA」)とを指定したDNSクエリパケットをDNSサーバに対して送信する。次に、DNSクエリパケットを受信したDNSサーバは、受信したホスト名のエントリのうち、指定されたレコードタイプ「AAAA」のエントリだけでなく、レコードタイプ「A」のエントリも検索する。図4に示す例では、この結果、ホスト名「hostX」に一致するエントリに含まれるアドレスp,q,s,tが特定される。
<参考文献2>M-K. Shin, et al., "Application Aspects of IPv6 Transition", March 2005, RFC4038 (http://www.ietf.org/rfc/rfc4038.txt)
次に、図7を参照して、第3の実施形態における名前解決システムの概要を説明する。図7は、名前解決を行う動作の例を示す説明図である。第3の実施形態における名前解決システムは、ホスト名に対してIPv6アドレスとIPv4アドレスの両方のエントリが存在する場合に、IPv4アドレスをIPv6アドレスに変換したエントリを予め作成しておくものである。具体的には、図7は、IPv4アドレスp,qが、所定のタイミングでIPv6アドレスp’,q’に変換(静的変換)され、磁気ディスク等に保持されていることを示す。なお、表中の網掛け部分が、変換されたレコードを示す。
次に、図10を参照して、第4の実施形態における名前解決システムの概要を説明する。図10は、名前解決を行う動作の例を示す説明図である。第4の実施形態における名前解決システムでは、まず、クライアントが、名前解決を行う対象のホスト名(図10では、「hostX」)と、IPv4アドレス及びIPv6アドレスのレコードタイプ(図10では、「A,AAAA」)とを指定したDNSクエリパケットをDNSサーバに対して送信する。次に、DNSクエリパケットを受信したDNSサーバは、受信したホスト名のエントリのうち、指定されたレコードタイプ「A」及び「AAAA」のエントリを検索する。図10に示す例では、この結果、ホスト名「hostX」と、指定されたレコードタイプに一致するエントリに含まれるアドレスp,q,s,tが特定される。そして、DNSサーバは、これらのアドレスp,q,s,tを含むパケットをクライアントに送信する。
11,31,61 アドレス問合せ手段
20,40,50,70 ネームデータベースサーバ
21 ノード情報記憶手段
22 検索対象レコード決定手段
24,43,54,72 検索結果送信手段
32 変換アドレス再変換手段
23,41,53,71 エントリ検索手段
42,52 アドレス変換手段
51 変換アドレス記憶手段
Claims (24)
- アドレス及びレコードタイプをホスト名と対応付けたエントリを記憶するノード情報記憶手段と、
前記エントリのうち、レコードタイプと名前解決を行う対象のホスト名とを送信して当該ホスト名に対応するアドレスを問い合わせる端末装置から受信する当該レコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信するレコードタイプのアドレスに変換するアドレス変換手段と、
前記ノード情報記憶手段を検索することにより、前記端末装置から受信したホスト名に対応するエントリを特定するエントリ検索手段と、
特定されたエントリに含まれるアドレスを前記端末装置に送信する検索結果送信手段とを備えた
ことを特徴とするネームデータベースサーバ。 - アドレス変換手段は、エントリ検索手段が特定したエントリに含まれるアドレスのうち、端末装置から受信したレコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信したレコードタイプのアドレスに変換し、
検索結果送信手段は、特定されたエントリに含まれる受信したレコードタイプのアドレスと、アドレス変換手段によって変換されたアドレスとを端末装置に送信する
請求項1記載のネームデータベースサーバ。 - ノード情報記憶手段は、少なくともIPv6アドレスおよびIPv4アドレスをホスト名と対応付けたエントリを記憶し、
エントリ検索手段は、端末装置からIPv6アドレスのレコードタイプと、名前解決を行う対象のホスト名とを受信したときに、前記ノード情報記憶手段を検索することにより、端末装置から受信したホスト名に対応するエントリであって、IPv6アドレスおよび/またはIPv4アドレスを示すレコードタイプのエントリを特定し、
アドレス変換手段は、所定の規則に基づいて、エントリ検索手段が特定したエントリに含まれるIPv4アドレスをIPv6アドレスに変換し、
検索結果送信手段は、エントリ検索手段が特定したエントリに含まれるIPv6アドレスと、アドレス変換手段によって変換されたIPv6アドレスとを端末装置に送信する
請求項2記載のネームデータベースサーバ。 - アドレス変換手段は、端末装置からIPv6アドレスのレコードタイプを受信した場合に、IPv4アドレスを、IPv4 mapped Addressに変換する
請求項1から請求項3記載のネームデータベースサーバ。 - ノード情報記憶手段は、第一のレコードタイプのアドレスと、第二のレコードタイプのアドレスから変換された第一のレコードタイプのアドレスである変換アドレスとを、ホスト名と対応付けて記憶し、
エントリ検索手段は、端末装置から第一のレコードタイプを受信したときに、前記ノード情報記憶手段を検索することにより、ホスト名に対応する当該第一のレコードタイプのエントリを特定し、
検索結果送信手段は、特定されたエントリに含まれる第一のレコードタイプのアドレスを端末装置に送信する
請求項1記載のネームデータベースサーバ。 - アドレス変換手段は、所定の規則に基づいて第二のレコードタイプのアドレスを第一のレコードタイプのアドレスに変換し、変換した第一のレコードタイプのアドレスを、ホスト名と対応付けてノード情報記憶手段に記憶させる
請求項5記載のネームデータベースサーバ。 - ノード情報記憶手段は、少なくともIPv6アドレスと、所定の規則に基づいてIPv4アドレスから変換されたIPv6アドレスとを、ホスト名と対応付けて記憶し、
エントリ検索手段は、端末装置からIPv6アドレスのレコードタイプを受信したときに、前記ノード情報記憶手段を検索することにより、ホスト名に対応するIPv6アドレスのエントリを特定し、
検索結果送信手段は、特定されたエントリに含まれるIPv6アドレスを端末装置に送信する
請求項5または請求項6記載のネームデータベースサーバ。 - ノード情報記憶手段は、IPv6アドレスとして、IPv4アドレスから変換されたIPv4 mapped Addressをホスト名と対応付けて記憶する
請求項5から請求項7のうちのいずれか1項に記載のネームデータベースサーバ。 - ホスト名に対するアドレスの問い合わせを行う端末装置と、
前記端末装置からの問い合わせを受信するネームデータベースサーバとを備え、
前記端末装置は、
レコードタイプと名前解決を行う対象のホスト名とを前記ネームデータベースサーバに送信して、当該ホスト名に対応するアドレスを問い合わせるアドレス問合せ手段を備え、
前記ネームデータベースサーバは、
アドレス及びレコードタイプをホスト名と対応付けたエントリを記憶するノード情報記憶手段と、
前記エントリのうち、前記端末装置から受信するレコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信するレコードタイプのアドレスに変換するアドレス変換手段と、
前記ノード情報記憶手段を検索することにより、前記端末装置から受信したホスト名に対応するエントリを特定するエントリ検索手段と、
特定されたエントリに含まれるアドレスを前記端末装置に送信する検索結果送信手段とを備えた
ことを特徴とする名前解決システム。 - 端末装置のアドレス問合せ手段は、IPv6アドレスのレコードタイプと、名前解決を行う対象のホスト名とをネームサーバに送信して、当該ホスト名に対応するアドレスを問い合わせ、
ノード情報記憶手段は、少なくともIPv6アドレスおよびIPv4アドレスをホスト名と対応付けたエントリを記憶し、
エントリ検索手段は、前記ノード情報記憶手段を検索することにより、端末装置から受信したホスト名に対応するエントリであって、IPv6アドレスおよび/またはIPv4アドレスを示すレコードタイプのエントリを特定し、
アドレス変換手段は、所定の規則に基づいて、エントリ検索手段が特定したエントリに含まれるIPv4アドレスをIPv6アドレスに変換し、
検索結果送信手段は、エントリ検索手段が特定したエントリに含まれるIPv6アドレスと、アドレス変換手段によって変換されたIPv6アドレスとを端末装置に送信する
請求項9記載の名前解決システム。 - アドレス変換手段は、端末装置からIPv6アドレスのレコードタイプを受信した場合に、IPv4アドレスを、IPv4 mapped Addressに変換する
請求項9または請求項10記載の名前解決システム。 - ネームデータベースサーバのアドレス変換手段は、端末装置による問い合わせの結果を特定の端末装置のみ利用可能にする処理である特定処理を行い、
端末装置は、
前記特定処理が行われた問い合わせの結果を利用可能にする戻し変換手段を備えた
請求項9から請求項11のうちのいずれか1項に記載の名前解決システム。 - ノード情報記憶手段は、少なくともIPv6アドレスと、所定の規則に基づいてIPv4アドレスから変換されたIPv6アドレスとを、ホスト名と対応付けて記憶し、
エントリ検索手段は、端末装置からIPv6アドレスのレコードタイプを受信したときに、前記ノード情報記憶手段を検索することにより、ホスト名に対応するIPv6アドレスのエントリを特定し、
検索結果送信手段は、特定されたエントリに含まれるIPv6アドレスを端末装置に送信する
請求項9記載の名前解決システム。 - ノード情報記憶手段は、IPv6アドレスとして、IPv4アドレスから変換されたIPv4 mapped Addressをホスト名と対応付けて記憶する
請求項9または請求項13記載の名前解決システム。 - 端末装置は、ネームデータベースサーバから受信したアドレスのうち、所定の規則に基づいて変換されたアドレスを、変換前のアドレスに変換する変換アドレス再変換手段を備えた
請求項9から請求項14のうちのいずれか1項に記載の名前解決システム - アドレス及びレコードタイプをホスト名と対応付けたエントリを記憶するノード情報記憶手段に記憶された当該エントリのうち、レコードタイプと名前解決を行う対象のホスト名とを送信して当該ホスト名に対応するアドレスを問い合わせる端末装置から受信する当該レコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信するレコードタイプのアドレスに変換し、
前記ノード情報記憶手段を検索することにより、前記端末装置から受信したホスト名に対応するエントリを特定し、
特定されたエントリに含まれるアドレスを前記端末装置に送信する
ことを特徴とするエントリ検索方法。 - 端末装置からIPv6アドレスのレコードタイプと、名前解決を行う対象のホスト名とを受信したときに、ノード情報記憶手段を検索することにより、端末装置から受信したホスト名に対応するエントリであって、IPv6アドレスおよび/またはIPv4アドレスを示すレコードタイプのエントリを特定し、
所定の規則に基づいて、特定されたエントリに含まれるIPv4アドレスをIPv6アドレスに変換し、
特定されたエントリに含まれるIPv6アドレスと、IPv4アドレスが変換されたIPv6アドレスとを端末装置に送信する
請求項16記載のエントリ検索方法。 - 端末装置からIPv6アドレスのレコードタイプを受信したときに、少なくともIPv6アドレスと、所定の規則に基づいてIPv4アドレスから変換されたIPv6アドレスとを、ホスト名と対応付けて記憶するノード情報記憶手段を検索することにより、ホスト名に対応するIPv6アドレスのエントリを特定し、
検索結果送信手段は、特定されたエントリに含まれるIPv6アドレスを端末装置に送信する
請求項16記載のエントリ検索方法。 - ホスト名に対するアドレスの問い合わせを行う端末装置が、レコードタイプと名前解決を行う対象のホスト名とを前記ネームデータベースサーバに送信して、当該ホスト名に対応するアドレスを問い合わせ、
前記ネームデータベースサーバが、アドレス及びレコードタイプをホスト名と対応付けたエントリを記憶するノード情報記憶手段に記憶された当該エントリのうち、前記端末装置から受信するレコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信するレコードタイプのアドレスに変換し、
前記ネームデータベースサーバが、前記ノード情報記憶手段を検索することにより、前記端末装置から受信したホスト名に対応するエントリを特定し、
前記ネームデータベースサーバが、特定されたエントリに含まれるアドレスを前記端末装置に送信する
ことを特徴とする名前解決方法。 - ネームデータベースサーバが、端末装置からIPv6アドレスのレコードタイプと、名前解決を行う対象のホスト名とを受信したときに、ノード情報記憶手段を検索することにより、端末装置から受信したホスト名に対応するエントリであって、IPv6アドレスおよび/またはIPv4アドレスを示すレコードタイプのエントリを特定し、
ネームデータベースサーバが、所定の規則に基づいて、特定されたエントリに含まれるIPv4アドレスをIPv6アドレスに変換し、
ネームデータベースサーバが、特定されたエントリに含まれるIPv6アドレスと、IPv4アドレスが変換されたIPv6アドレスとを端末装置に送信する
請求項19記載の名前解決方法。 - ネームデータベースサーバが、端末装置からIPv6アドレスのレコードタイプを受信したときに、少なくともIPv6アドレスと、所定の規則に基づいてIPv4アドレスから変換されたIPv6アドレスとを、ホスト名と対応付けて記憶するノード情報記憶手段を検索することにより、ホスト名に対応するIPv6アドレスのエントリを特定し、
ネームデータベースサーバが、特定されたエントリに含まれるIPv6アドレスを端末装置に送信する
請求項19記載の名前解決方法。 - アドレス及びレコードタイプをホスト名と対応付けたエントリを記憶するノード情報記憶手段を備えたコンピュータに適用されるエントリ検索プログラムであって、
前記コンピュータに、
前記エントリのうち、レコードタイプと名前解決を行う対象のホスト名とを送信して当該ホスト名に対応するアドレスを問い合わせる端末装置から受信する当該レコードタイプと異なるレコードタイプのアドレスを、所定の規則に基づいて、受信するレコードタイプのアドレスに変換するアドレス変換処理、
前記ノード情報記憶手段を検索することにより、前記端末装置から受信したホスト名に対応するエントリを特定するエントリ検索処理、および、
特定されたエントリに含まれるアドレスを前記端末装置に送信する検索結果送信処理
を実行させるためのエントリ検索プログラム。 - コンピュータに、
エントリ検索処理で、端末装置からIPv6アドレスのレコードタイプと、名前解決を行う対象のホスト名とを受信したときに、少なくともIPv6アドレスおよびIPv4アドレスをホスト名と対応付けたエントリを記憶するノード情報記憶手段を検索することにより、端末装置から受信したホスト名に対応するエントリであって、IPv6アドレスおよび/またはIPv4アドレスを示すレコードタイプのエントリを特定させ、
アドレス変換処理で、所定の規則に基づいて、エントリ検索処理で特定されたエントリに含まれるIPv4アドレスをIPv6アドレスに変換させ、
検索結果送信処理で、エントリ検索処理で特定されたエントリに含まれるIPv6アドレスと、アドレス変換処理で変換されたIPv6アドレスとを端末装置に送信させる
請求項22記載のエントリ検索プログラム。 - コンピュータに、
エントリ検索処理で、端末装置からIPv6アドレスのレコードタイプを受信したときに、少なくともIPv6アドレスと、所定の規則に基づいてIPv4アドレスから変換されたIPv6アドレスとを、ホスト名と対応付けて記憶するノード情報記憶手段を検索することにより、ホスト名に対応するIPv6アドレスのエントリを特定させ、
検索結果送信処理で、特定されたエントリに含まれるIPv6アドレスを端末装置に送信させる
請求項22記載のエントリ検索プログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/820,958 US9679022B2 (en) | 2010-10-18 | 2011-10-11 | Name database server, name resolution system, entry search method and entry search program |
CN201180047156.XA CN103141073B (zh) | 2010-10-18 | 2011-10-11 | 名称数据库服务器、名称解析系统、条目搜索方法以及条目搜索装置 |
JP2012539582A JP5812008B2 (ja) | 2010-10-18 | 2011-10-11 | ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム |
EP11834009.0A EP2632090A4 (en) | 2010-10-18 | 2011-10-11 | Name-database server, name-resolution system, entry-search method, and entry-search program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010233413 | 2010-10-18 | ||
JP2010-233413 | 2010-10-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012053163A1 true WO2012053163A1 (ja) | 2012-04-26 |
Family
ID=45974894
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/005688 WO2012053163A1 (ja) | 2010-10-18 | 2011-10-11 | ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US9679022B2 (ja) |
EP (1) | EP2632090A4 (ja) |
JP (1) | JP5812008B2 (ja) |
CN (1) | CN103141073B (ja) |
WO (1) | WO2012053163A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015220483A (ja) * | 2014-05-14 | 2015-12-07 | 西日本電信電話株式会社 | DNS−Proxy機能を有する中継装置 |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10552391B2 (en) * | 2008-04-04 | 2020-02-04 | Landmark Graphics Corporation | Systems and methods for real time data management in a collaborative environment |
US9419940B2 (en) * | 2012-03-02 | 2016-08-16 | Futurewei Technologies, Inc. | IPv4 data center support for IPv4 and IPv6 visitors |
US8800011B2 (en) * | 2012-05-31 | 2014-08-05 | Rackspace Us, Inc. | Validating pointer records in a domain name system (DNS) service |
KR101419436B1 (ko) * | 2012-12-14 | 2014-08-13 | (주)씨디네트웍스 | Dns 서비스 제공 방법 및 장치 |
JP5889955B2 (ja) * | 2014-05-13 | 2016-03-22 | 西日本電信電話株式会社 | 中継装置及びプログラム |
US10122630B1 (en) | 2014-08-15 | 2018-11-06 | F5 Networks, Inc. | Methods for network traffic presteering and devices thereof |
CA3015486A1 (en) * | 2016-02-23 | 2017-08-31 | Level 3 Communications, Llc | Systems and methods for content server rendezvous in a dual stack protocol network |
US10791088B1 (en) | 2016-06-17 | 2020-09-29 | F5 Networks, Inc. | Methods for disaggregating subscribers via DHCP address translation and devices thereof |
US10142230B2 (en) * | 2016-08-15 | 2018-11-27 | Vonage Business Inc. | Method and apparatus for transmitting messages associated with internet protocol version 4 (IPv4) addresses on an internet protocol version 6 (IPv6) network |
US11122083B1 (en) | 2017-09-08 | 2021-09-14 | F5 Networks, Inc. | Methods for managing network connections based on DNS data and network policies and devices thereof |
US11196705B2 (en) * | 2018-01-05 | 2021-12-07 | Nextroll, Inc. | Identification services for internet-enabled devices |
CN109167849A (zh) * | 2018-08-16 | 2019-01-08 | 深圳市天威视讯股份有限公司 | 用于混合通道的智能机顶盒的域名解析方法和系统 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009182631A (ja) * | 2008-01-30 | 2009-08-13 | Yokogawa Electric Corp | ネットワークシステム |
JP2010183242A (ja) | 2009-02-04 | 2010-08-19 | Kddi Corp | 通信装置およびdnsプロキシサーバ |
JP2010233413A (ja) | 2009-03-30 | 2010-10-14 | Aisin Seiki Co Ltd | 電動機 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100560737B1 (ko) * | 2003-02-18 | 2006-03-13 | 삼성전자주식회사 | 듀얼스택을 이용한 아이피브이4 - 아이피브이6 전환 장치및 그 방법 |
CN100474858C (zh) | 2004-09-27 | 2009-04-01 | 上海贝尔阿尔卡特股份有限公司 | 域名解析方法、域名服务器及域名系统 |
JP4812108B2 (ja) * | 2006-12-18 | 2011-11-09 | キヤノン株式会社 | 通信装置及びその制御方法 |
US8243740B1 (en) * | 2008-11-21 | 2012-08-14 | Sprint Communications Company L.P. | Using domain name server response and internet protocol version 6 to conserve internet protocol version 4 addresses |
US8825859B2 (en) * | 2009-12-23 | 2014-09-02 | Citrix Systems, Inc. | System and methods for mixed mode of IPv6 and IPv4 DNS of global server load balancing |
US9015327B2 (en) * | 2012-06-11 | 2015-04-21 | At&T Intellectual Property I, Lp | Apparatus and methods for flexible communicatons in a network |
-
2011
- 2011-10-11 CN CN201180047156.XA patent/CN103141073B/zh active Active
- 2011-10-11 WO PCT/JP2011/005688 patent/WO2012053163A1/ja active Application Filing
- 2011-10-11 EP EP11834009.0A patent/EP2632090A4/en not_active Withdrawn
- 2011-10-11 JP JP2012539582A patent/JP5812008B2/ja active Active
- 2011-10-11 US US13/820,958 patent/US9679022B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009182631A (ja) * | 2008-01-30 | 2009-08-13 | Yokogawa Electric Corp | ネットワークシステム |
JP2010183242A (ja) | 2009-02-04 | 2010-08-19 | Kddi Corp | 通信装置およびdnsプロキシサーバ |
JP2010233413A (ja) | 2009-03-30 | 2010-10-14 | Aisin Seiki Co Ltd | 電動機 |
Non-Patent Citations (5)
Title |
---|
HIROSHI KITAMURA ET AL.: "Simplified DNS Query Methods under IPv4/IPv6 Mixed Environment", IEICE TECHNICAL REPORT, IN2010-153, 24 February 2011 (2011-02-24), XP008167820 * |
KEISUKE TAKEUCHI ET AL.: "Development of DNS Proxy Server co-operating with IPv4/IPv6 Translators", IEICE TECHNICAL REPORT, NS2002- 246, 27 February 2003 (2003-02-27), XP008167897 * |
M-K. SHIN ET AL., APPLICATION ASPECTS OF IPV6 TRANSITION, March 2005 (2005-03-01), Retrieved from the Internet <URL:http://www.ietf.org/rfc/rfc4038.txt> |
R. HINDEN; S. DEERING, IP VERSION 6 ADDRESSING ARCHITECTURE, February 2006 (2006-02-01), Retrieved from the Internet <URL:http:llwww.ietf.org/rfc/rfc4291.txt> |
See also references of EP2632090A4 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015220483A (ja) * | 2014-05-14 | 2015-12-07 | 西日本電信電話株式会社 | DNS−Proxy機能を有する中継装置 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2012053163A1 (ja) | 2014-02-24 |
EP2632090A4 (en) | 2017-01-18 |
EP2632090A1 (en) | 2013-08-28 |
US9679022B2 (en) | 2017-06-13 |
CN103141073B (zh) | 2016-07-06 |
US20130212127A1 (en) | 2013-08-15 |
JP5812008B2 (ja) | 2015-11-11 |
CN103141073A (zh) | 2013-06-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5987690B2 (ja) | ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム | |
JP5812008B2 (ja) | ネームデータベースサーバ、名前解決システム、エントリ検索方法およびエントリ検索プログラム | |
JP6861219B2 (ja) | インテリジェントドメインネームシステム転送のための方法および装置 | |
CN102859960B (zh) | 用于关联名字服务器IPv6地址和IPv4地址的方法和装置 | |
JP5587732B2 (ja) | ドメイン・ネーム・サービス(dns)データベースへのアクセスを管理するコンピュータ実施方法、コンピュータ・プログラム、およびシステム | |
US7779158B2 (en) | Network device | |
US7558880B2 (en) | Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device | |
US7573903B2 (en) | IPv6/IPv4 translator | |
JP2007527068A (ja) | 少なくとも2つの計算装置間の接続を設定する際のアドレス及びポート番号アブストラクション | |
US9386097B2 (en) | Using values represented as internet protocol (IP) addresses to access resources in a non-internet protocol address space | |
US20230216825A1 (en) | Gateway based ip address translation in communication networks | |
US20070118884A1 (en) | Name resolution system using name registration intermediary and name resolution intermediary | |
JP2016503267A (ja) | ネットワークのプロトコルアドレスを扱う方法及び処理デバイス | |
KR101051792B1 (ko) | 네트워크 주소 변환 장치 및 방법 | |
US9306900B2 (en) | Communication device, communication system, and communication method | |
JP2009015645A (ja) | ファイルサーバ装置、ファイル管理システム、ファイル管理方法、ファイル管理制御プログラムおよびそのプログラムを記録した記録媒体 | |
JP2008206081A (ja) | マルチホーミング通信システムに用いられるデータ中継装置およびデータ中継方法 | |
KR20050104103A (ko) | 사설 네트워크를 기반으로 하는 단말간의 일대일 통신시스템 및 그 방법 | |
JP2001268132A (ja) | ネットワークシステムの相互接続のためのネットワークアドレス変換方法及び装置 | |
WO2019015363A1 (zh) | 数据包路由方法和数据包路由装置 | |
JP2007243675A (ja) | アドレス変換方法及び装置とプログラム | |
JP2002374322A (ja) | インタフェース管理方法 | |
JP2011166269A (ja) | 名前解決システム、名前解決サーバ、名前解決方法及び名前解決プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180047156.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11834009 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2012539582 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011834009 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13820958 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |