CN101436981B - Domain name server system of extended IPv4 network - Google Patents

Domain name server system of extended IPv4 network Download PDF

Info

Publication number
CN101436981B
CN101436981B CN2007101661957A CN200710166195A CN101436981B CN 101436981 B CN101436981 B CN 101436981B CN 2007101661957 A CN2007101661957 A CN 2007101661957A CN 200710166195 A CN200710166195 A CN 200710166195A CN 101436981 B CN101436981 B CN 101436981B
Authority
CN
China
Prior art keywords
address
node
name server
domain name
private
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN2007101661957A
Other languages
Chinese (zh)
Other versions
CN101436981A (en
Inventor
刁永平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN2007101661957A priority Critical patent/CN101436981B/en
Publication of CN101436981A publication Critical patent/CN101436981A/en
Application granted granted Critical
Publication of CN101436981B publication Critical patent/CN101436981B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention relates to a domain name server system in an expanded IPv4 network. On the basis of the domain name server system of the prior IPv4 public IP address domain, at the edge of the public IP address domain in the expanded IPv4 network, an independent domain name server subtree is derived for a private IP address domain, and the domain name server subtree at least comprises a first domain name server in charge of managing total domain names of IP nodes in the private IP address domain and mapping of positions of the IP nodes. The domain name server system solves the problem that the prior IPv4 domain name server system only aims at the public IP address domain. The domain name server system also solves the problem that the prior art determines an IP node address according to the domain names of the IP nodes, but can not determine IP node positions of (the public IP address) or [the private IP address] according to the domain names of the IP nodes, so as to solve the problem of knowledge of the IP node positions in the expanded IP network.

Description

Domain name server system in the IPv4 network of expansion
Technical field
The present invention relates to the IP network technical field, relate in particular to the realization of name server (DNS) system extension in expansion IPv4.
Background technology
Anyone can't imagine that at the initial stage of internet development network of today can develop into so big scale.Before 20th century the nineties, agenda has just been put in the address crisis that solves the Internet, predicts at that time that the resource of the Internet will soon assign.Afterwards, the appearance of privately owned private network scheme, dynamic address allocation technology, VLSM (VLSM) technology, CIDR (CIDR) technology and NAT/NAPT technology had greatly slowed down the speed of IP address resource exhaustion.In order thoroughly to solve the problem that IP address scarcity causes, the IETF decision adopts IPv6 as follow-on the Internet, but its progress is very slow, can't in time satisfy the demand of the Internet fast development.
Millions upon millions of main frames are arranged on the internet, and in order to distinguish these main frames, people distribute a special address for every main frame, are called the IP address, just can have access to each main frame by the IP address.The IP address is made up of four parts numeral, and every part numeral is corresponding to 8 bit binary number, and decimally separately, the IP address can reach 2 in theory between the each several part 32Individual.IP address as a certain main frame is: 211.152.65.112.Internet-ip address is specifically responsible for the U.S. and other regional IP address assignment by Inter NIC, APNIC, RIPE three macroreticular information centres simultaneously by unified planning and the management of being responsible for global address of NIC (inter NIC).
Because the scarcity of existing IP network address, the Internet industry has been made and has much been made great efforts to attempt to address this problem, and as NAT/NAPT, IPv6 etc., but owing to has open defect or an implementation cost is excessive and make slow progress.
Therefore, it is 200610143248.9 patent application that the applicant has proposed application number on November 1st, 2006, this application has proposed a kind of implementation method that existing IP network is expanded, and has wherein adopted the two-stage expandable IP network framework in public ip address and private IP address territory.Position according to source IP node and destination IP node is represented, controls the IP packet based on the mode of source routing and navigates within whole expansion IP network without barrier.
In this application, proposed a kind of like this expansion IP network: this expansion IP network comprises public ip address territory and private IP address territory, comprise the IP node that has legal public ip address in the described public ip address territory, and described private IP address territory comprises the IP node that adopts private IP address, wherein between publicly-owned address field and privately owned address field, be connected with public and private address field boundary point gateway, described public and private address field boundary point gateway had both had the address that belongs to publicly-owned address field, has simultaneously the address that belongs to privately owned address field again, IP node in publicly-owned address field and the privately owned address field can be visited mutually by this public and private address field boundary point gateway, and each IP node in this network and public and private address field point of interface gateway are all supported source routing option.
It is legal to have only publicly-owned address to be only in traditional the Internet, so each internet node can be determined and the location uniquely by public ip address.And in the expansion IP network framework that this application adopted, though it is unique that legal public ip address remains the whole network, but the private IP address territory can be reused, so this application has proposed the position that a kind of IP node positioning method is determined any IP network node in a scalable network.
In the IP node positioning method according to this application, the position of IP node can be expressed as: (public ip address) [: private IP address].Wherein, the IP node location in the publicly-owned address field is expressed as
The public ip address of this node;
IP node location in the privately owned address field is expressed as
The public ip address of the public and private network domains boundary point gateway that this node is associated: the private IP address of this IP node;
The IP node location of public and private address field boundary point gateway is expressed as
The public ip address of this gateway IP node, perhaps
This gateway IP node: the privately owned address of this gateway IP node.
Like this, adopt the public ip address of node or just can determine to expand the position of any one IP node in the IP network in conjunction with the private IP address that adopts node and the public ip address that is associated uniquely.
In IP packet header predefine option type be 131 loose source routing (LSRR) option.It is because any route that allows gateway or host ip use to contain other middle gateways of any amount arrives the next address in the source routing that this option is called loose source routing.Loose source and record route option provide a kind of source address by the IP packet to come to write down the method for this routing iinformation simultaneously for gateway provides the routing iinformation that how this packet is forwarded to destination-address.
First byte in loose source and the record route option is the type codes of LSRR option; Second length (length) that byte is the LSRR option comprises the byte number that this option is all; The 3rd byte is pointer (pointer), points to next source routing to be processed address, and this pointer is for this option, and minimum legal value is 4.Route data (route data) is made up of a series of IP address, and each IP address definition is four bytes.This application promptly realizes expansion to IP network by the IP node to the support of LSRR route option.
In the expansion IP network, finish in the method for packet transmission, the source IP node and the destination IP node of at first definite packet that will transmit, and according to the position of the source IP node and the destination IP node of above-mentioned IP node positioning method specified data bag, the address sequence of representing by the inverted sequence of source IP node location then, the address sequence that the order of destination IP node location of connecting is again represented, thus constitute the path address sequence that this packet will transmit.
Source IP node is inserted first address in the top resulting entire path address sequence source address field in IP packet header, second address inserted the destination address field in IP packet header, then will insert the loose source in IP packet header and the route data field in the record route option in turn as the source routing address sequence except that the remaining address described first address, and length value and pointer position be set, make the beginning of pointed source routing address sequence, IP node in source is transmitted the IP packet according to current pointer address pointed or according to the address in the current destination address field then.Because pointer address pointed is consistent with address in the destination address field, therefore no matter still can make packet arrive desired node according to the purpose routing mode of routine according to the source routing mode this moment.
After packet arrives the represented IP node in address in the current destination address field, if pointer does not surpass length value, the next address in the pointed route data field then, and replace address in the current destination address field with the next address in the source routing address sequence, make just used source routing address be replaced by the record routing address simultaneously, this IP node continues to transmit packet.
If pointer has exceeded length value, then this IP node is exactly the final purpose way address that packet will arrive, the order of recording address sequence is reverse, thereby the reverse path sequence when obtaining the response data bag according to the recording address sequence after oppositely and source IP address makes packet send back source IP node from destination IP node in the manner described above.
Specifically, Fig. 1 shows the expandable IP network framework based on source routing that this application proposes.As shown in Figure 1, comprise public ip address territory, two private IP address territory A and B and public and private address field boundary point as the whole expandable IP network of example.
The IP node that the public ip address territory comprises all has legal public ip address, and all legal public ip address nodes all should belong to the public ip address territory.The public ip address territory is exactly existing Global Internet, and IP node wherein and employed routing mechanism all remain unchanged.As in Fig. 1, IP node S2, D2 just are positioned at the public ip address territory, and its address is respectively public ip address Addr S2And Addr D2
The IP node that the private IP address territory comprises all adopts private IP address, and all adopt the node of private IP address all should belong to the private IP address territory.The private IP address territory is similar to more existing area or the enterprise's IP network that adopts privately owned address, and wherein employed routing mechanism etc. is identical with the public ip address territory, and difference only is to have adopted private IP address.As in Fig. 1, IP node S1, D1, D3 are located in private IP address territory A, the B, and its address is respectively private IP address Addr S1, Addr D1And Addr D3
Public and private address field boundary point is the joint in public ip address territory and private IP address territory, gateway normally, and this gateway had both had the address that belongs to the public ip address territory, had the address that belongs to the private IP address territory simultaneously again.IP node in the private IP address territory can be visited the public ip address territory by this gateway, and vice versa.As in Fig. 1, IP node GA, GB are exactly public and private address field boundary point gateway, and their public ip address is respectively PublichAddr GAAnd PublicAddr GB, and private IP address is respectively PrivateAddr GAAnd PrivateAddr GB
According to the IP node positioning method that this application adopted, the IP node location in the publicly-owned address field is expressed as the public ip address of this node.In Fig. 1, be positioned at the IP node S2 in public ip address territory, the position Position of D2 S2And Position D2Be expressed as public ip address Addr respectively S2And Addr D2Promptly
Position S2＝Addr S2
Position D1＝Addr D1
IP node location in the privately owned address field is expressed as the public ip address of the associated public and private network domains boundary point gateway of this node: the private IP address of this IP node.In Fig. 1, be positioned at the IP node S1 in private IP address territory, the position Position of D1, D3 S1, Position D1And Position D3Just be expressed as respectively:
Position S1＝PublicAddr GA：Addr S1
Position D1＝PublicAddr GA：Addr D1
Position D3＝PublicAddr GB：Addr D3
The IP node location of public and private address field boundary point gateway is expressed as the public ip address of this gateway IP node, perhaps is expressed as this gateway IP node: the privately owned address of this gateway IP node.In Fig. 1, IP node GA, GB represent two public and private address field boundary point gateways, and their public ip address is respectively PublichAddr GAAnd PublicAddr GB, and their private IP address is respectively PrivateAddr GAAnd PrivateAddr GB, its position Position GAAnd Position GBBe expressed as follows respectively:
Position GA=PublichAddr GA, perhaps PublichAddr GA: PrivateAddr GA
Position GB=PublichAddr GB, perhaps PublichAddr GA: PrivateAddr GB
Fig. 2 shows each byte implication in the loose source and record route option field in the IP packet header.Wherein first byte is the type codes of LSRR option; Second byte is length value, comprises the byte number that this option is all; The 3rd byte is pointer, promptly points to next source routing to be processed address, and this pointer is for this option, and minimum legal value is 4.Route data (route data) is made up of a series of IP address, and each IP address definition is four bytes.The pointer size does not also surpass length value if packet has arrived the address in the destination address field, then the next address in route data field this moment will be replaced the address in the current destination address field, replace just used source routing address with the record routing address, the next address (being that pointer adds 4) in the pointed source routing sequence simultaneously, and make the source routing address be recorded routing address to replace.When if the pointer size has surpassed length value, then the source routing address sequence is full for sky writes down the routing address sequence, and ensuing route will be carried out according to destination-address.
Give one example below to describe and finish the process that packet transmits with the source routing mode.At first the source IP node of specified data bag and destination IP node obtain source IP node location and destination IP node location according to the above-mentioned IP node positioning method then, thus the path that can should pass through according to the particular location setting data bag of node.As shown in Figure 1, suppose that source IP node is S1, its IP address is Addr S1, the region is private IP address territory A, the public ip address of the gateway related with it is PublicAddr GA, i.e. the position Position of source IP node S1=PublicAddr GA: Addr S1If destination IP node is D3, its IP address is Addr D3, the region is private IP address territory B, the public ip address of the gateway related with it is PublicAddr GB, i.e. the position Position of destination IP node D3=PublicAddr GB: Addr D3This moment from source IP node S1 to destination IP node D3 must pathway through being Addr S1-＞PublicAddr GA-＞PublicAddr GB-＞Addr D3, i.e. the inverted sequence address sequence that can represent by source IP node location, the sequence address sequence that the destination IP node location of connecting is again represented, thereby whole " the path address sequence " of composition data bag.
For the source routing of realizing being scheduled to, according to the source routing principle, source IP node must be according to source address field, destination address field, loose source and record route option (LSRR) field in the path address sequence filling IP packet header.As shown in Figure 3, at the first stop of path address sequence, source IP node S1 first address in the entire path address sequence that obtains in a manner described, be the source address field that source IP node address is inserted IP packet header; Publicly-owned address PublicAddr with second address, the public and private address field boundary point gateway that promptly is associated with source IP node GAInsert the destination address field in IP packet header; With the remaining address except first address (source IP node address) in the path address sequence (i.e. so-called " source routing address sequence ") PublicAddr GA-＞PublicAddr GB-＞Addr DInsert the loose source in IP packet header and " route data (route the data) " field in the record route option in turn, and relevant length (length), pointer parameters such as (pointer) are set.Like this, IP node in source just will guarantee that the route that this packet can arrive destination IP node determined to get off.
In transmission course, source IP node is at first according to first address (being second address in the path address sequence) PublicAddr of source routing address sequence GATransmit the IP packet.Because the IP address that pointer is indicated in the source routing option is consistent with the IP address in the destination address field, therefore other private IP address territory router in the approach before arriving this IP node both can use the source routing function also can still use conventional purpose routing function to transmit this packet, all can arrive first address PublicAddr of source routing at last GA(also being the destination-address of packet in this network segment simultaneously) is the private IP address territory A at IP node place, source and the point of interface gateway GA between the public ip address territory in this example.
In second station of path address sequence shown in Figure 3, gateway GA must handle according to the source routing principle, if promptly packet has reached the address of current destination address field and the pointer size also surpasses the preseting length value, then replace address in the current destination address field with the next address in the source routing address sequence, and with writing down the just used source routing of routing address replacement address, pointer adds 4 simultaneously.Like this, the IP address in the IP address of pointer indication and destination-address territory has just as one man been made the next address in the path sequence address, i.e. PublicAddr in the source routing option GBEqually, other public ip address territory router in the approach before arriving this IP node can use the source routing function or still use conventional purpose routing function to transmit packet, all can arrive second address PublicAddr of source routing at last GB(also being the destination-address of packet in this network segment simultaneously) is the point of interface gateway GB of the private IP address territory B at public ip address territory and IP node place, destination in this example.
Similar with the processing of gateway GA, gateway GB also must handle (the 3rd station of path address sequence shown in Figure 3) according to the source routing principle.The IP address of the pointer indication in the source routing option and the IP address in destination-address territory are as one man made the next address in the path sequence address, i.e. Addr again into D3, same, other private IP address territory router in the approach before arriving this IP node uses the source routing function or uses conventional purpose routing function to transmit this packet, all can arrive the 3rd address Addr of source routing at last D3(also being the destination-address of packet in this network segment simultaneously) is destination IP node D3 in this example.
At the 4th station of path address sequence shown in Figure 3, according to the source routing principle, it oneself is exactly the final destination that this packet will arrive that destination IP node D3 finds, obtains reverse " recording address sequence " as the source routing address sequence.Reverse " path address sequence ", i.e. Addr when like this, destination IP node just can obtain the response data bag according to this recording address sequence and source IP address D3-＞PublicAddr GB-＞PublicAddr GA-＞Addr S1That is to say the inverted sequence address sequence that to represent by the position of reverse source IP node D3, the sequence address sequence represented of the position of series opposing destination IP node S1 again.Like this, according to the source routing principle, IP address, destination node also can use same process successfully packet to be sent back source IP node.
Equally, for other internodal communications among Fig. 1, also can realize expanding route in the IP network according to above-described method.
Realization based on the expansion IP network of source routing has solved the major issue that perplexs the Internet industry for a long time, and the extensibility that it has realized IP network has solved the problem of IPv4 address scarcity, makes the expansion transition problem of IP network become very simple.
The expansion IPv4 in order to adopt source routing method to finish the transmission of datagram, at first the source IP node and the destination IP node of specified data newspaper, draw source IP node location and destination IP node location according to the above-mentioned IP node positioning method then, like this we just can according to their particular location setting data retribution should process " path (Path) ", and then according to the method among the IPv4 of expansion, source IP node use path address sequence is filled the source address field in the IP header, destination address field, loose source and record route option field, like this, source IP node just guaranteeing that the route that this packet can arrive destination IP node determined to get off, has been realized the expansion IP network based on source routing that this application proposes.Yet the domain name server system of existing IPv4 can only be determined the IP node address according to the domain name of IP node, can not determine IP node location as above-mentioned (public ip address) [: private IP address] according to the domain name of IP node.Therefore, determine the path according to source IP node location and destination IP node location, just become one of the problem to be solved in the present invention thereby how to obtain destination IP node location in the situation of knowing destination IP node domain name.
Just its institutional framework layering is the same in the name server of prior art (DNS) system, extends downwards from top DNS root server, and domain name and IP address are propagated on each server that spreads all over the world.On each server, deposit some IP resource records, contained the domain name of node and the IP addresses of nodes that is associated with this domain name in the IP resource record.Name server is not stored the whole domain names and the mapping of IP address in this locality, in case name server does not find the IP address in self database, whether it can ask the upper level name server to be seen can find that name server of depositing this IP address, if the upper level name server does not still find, then inquire about more top top-level domain server, up to finding root name server, root name server generally can know to have deposited the IP address that will look on which following name server.These name servers all on public network, the IP address that they have only been stored the node domain name and have been associated with this domain name, and the IP node location that does not have the memory node domain name and be associated, i.e. (public ip address) [: private IP address] with this domain name.Domain name when present known source IP node and destination IP node, source IP node is wanted to know destination IP IP addresses of nodes according to domain name, thereby obtain source IP node and destination IP IP addresses of nodes, and then when between source IP address and IP address, destination, setting up route, CLIENT PROGRAM on the IP node of source starts, (this CLIENT PROGRAM and domain name mapping device function operation are on the client computer of this node to call its domain name mapping device function, when landing when starting, the user can move automatically, be prior art), the domain name that this domain name mapping device function can be keyed in the user wants the IP node that communicates with converts the request of an IP address lookup to and sends into nearby name server, inform by this name server which name server the user IP address relevant with this domain name is left on, but because this IP address storage on each name server is a distributed storage, so when this name server does not have storage to leave information on which name server in about the IP address relevant with this domain name, it must get in touch (this is the distribution character of DNS just) with other name server, yet, be not that each name server all knows how to get in touch with other name servers, on the contrary, each name server must know how to get in touch with the name server of root.All name servers must know that all (these IP addresses are in the configuration file of name server for the IP address of root server, name server must be known the IP address of root server, rather than their domain name), root server is then known domain name and position (being the IP address) of each authoritative domain name server in all second-level domains.This means such process repeatedly: the name server (by successively being forwarded to the name server of upper level, thereby get in touch with root server, root server tells it and another name server to get in touch) of handling request.For example, when this name server does not have storage to leave information on which name server in about the IP address relevant with this domain name, it is forwarded to the previous field name server with it, if still not this information up forwarding again of the previous field name server, until arriving root name server.Root name server generally can know to have deposited the IP address that will look on which following name server, and by return the response inform which name server the IP address that the user will look for is recorded on, user's source node sends request to the name server that this has deposited the IP address that will look for again then, this name server of having deposited the IP address that will look for is informed this IP address of user by response, like this, the source node at user place has just been known the destination IP addresses of nodes, just can be connected with the destination node.Yet, two inapplicable places have appearred in the IPv4 network of the name server architecture system of existing IPv4 after at above-described expansion: a place is to determine the IP node address according to the domain name of IP node, and the IPv4 network requirement after the above-mentioned expansion is determined IP node location as above-mentioned (public ip address) [: private IP address] according to the domain name of IP node, and is not only the IP node address; Another place is that the name server architecture system of existing IPv4 is only at the public ip address territory, if the node in the private IP address territory will be inquired about (promptly inquire about by the private IP address territory and enter the public ip address territory) to the node in public ip address territory, perhaps the node in the public ip address territory will be inquired about (promptly inquire about by the public ip address territory and enter the private IP address territory) to the node in private IP address territory, lacks corresponding name server architecture.
That is to say, expansion IPv4 is to the demand of DNS, to no longer only be that requirement DNS provides the conversion between host domain name and the IP address, but require to provide the domain name of IP node and the conversion of IP node location, thereby, any source IP node among the expansion IPv4 just can be according to another domain name as the IP node of destination (certainly, should be than being easier to understand and memory), DNS interpreter function by this source IP node itself, from position based on this destination of acquisition IP node the name server of expansion IPv4, and then, source IP node according to the positional information of itself positional information and destination IP node just can according to expand the method stipulated among the IPv4 successfully with this destination IP node communication.
Summary of the invention
An object of the present invention is to solve name server architecture system the problem of existing IPv4 at the public ip address territory, thereby the node in the private IP address territory will carry out the inquiry of domain name or IP node location to the node in public ip address territory, perhaps when the node in the public ip address territory will carry out the inquiry of domain name or IP node location to the node in private IP address territory, corresponding name server architecture is arranged.
Another object of the present invention is to solve in the prior art to determine the IP node address according to the domain name of IP node, and can not determine problem as the IP node location of above-mentioned (public ip address) [: private IP address] according to the domain name of IP node, thereby the IP node location that solves in the expansion IP network is known problem.
The invention provides a kind of domain name server system in the IPv4 network of expansion, wherein on the basis of the domain name server system in the public ip address territory of existing IPv4, the publicly-owned address field of IP edge in the IPv4 network of expansion, for the private IP address territory derives independently name server (DNS) subtree, this name server (DNS) subtree contains first name server of the mapping of a whole domain name of being in charge of IP node in this private IP address territory and IP node location at least.
The invention solves name server architecture system the problem of existing IPv4 at the public ip address territory, thereby the node in the private IP address territory will carry out the inquiry of domain name or IP node location to the node in public ip address territory, perhaps when the node in the public ip address territory will carry out the inquiry of domain name or IP node location to the node in private IP address territory, corresponding name server architecture is arranged.
The present invention has also solved in the prior art can only determine the IP node address according to the domain name of IP node, and can not determine problem as the IP node location of above-mentioned (public ip address) [: private IP address] according to the domain name of IP node, thereby the IP node location that has solved in the expansion IP network is known problem.
Description of drawings
Fig. 1 shows the expansion IP network framework of mentioning in the prior art based on source routing.
Fig. 2 shows prior art based on loose source that comprises in the IP packet header in the expansion IP network framework of source routing and record route (LSRR) option.
Fig. 3 shows according to the expansion IP network framework of prior art based on source routing, the state of IP header field different phase in routing procedure.
Fig. 4 is the system assumption diagram of the domain name server system embodiment 1 in the IPv4 network of expansion of the present invention.
Fig. 5 is the system assumption diagram of the domain name server system embodiment 2 in the IPv4 network of expansion of the present invention.
Fig. 6 is the system assumption diagram of the domain name server system embodiment 3 in the IPv4 network of expansion of the present invention.
Fig. 7 is the system assumption diagram of the domain name server system embodiment 4 in the IPv4 network of expansion of the present invention.
Fig. 8 is the system assumption diagram of the domain name server system embodiment 5 in the IPv4 network of expansion of the present invention.
Fig. 9 is the figure of IP node location of the present invention (IPD) resource record form.
Figure 10 is the figure of pointer resource record form of the present invention.
Figure 11 is according to an example of the present invention, and source IP node finds this destination IP node location according to destination IP node domain name, and IP node in destination carries out the method schematic diagram of authenticate reverse then.
Embodiment
Can solve the deficient problem of existing IP network address effectively based on the implementation method of the expansion IPv4 network (EIPv4) of source routing, being necessary on using provides domain names to explain service at EIPv4.The present invention proposes and a kind of existing DNS system is expanded the method that provides the DNS inquiry service of domain name between representing to the IP node location in expansion IP network two level frameworks to be supported in, and defined a kind of new DNS resource record and using method thereof.
In expansion IPv4 network, constant for the DNS System Operation mechanism that guarantees existing the Internet, do not plan to change the outfit and the setting of server in the Internet DNS institutional framework, so it is constant to keep the DNS system of existing the Internet in the public ip address territory.
In the IPv4 network of expansion, publicly-owned by the public ip address territory by certain, when private IP address territory boundary point derives some private IP address territory, need promptly be called a zone (zone) this private IP address territory as a DNS subtree of managing independently.In other words, the publicly-owned address field of the IP edge in the IPv4 network of expansion for the private IP address territory derives independently name server (DNS) subtree, and is independently managed in a zone as DNS.In case after the authorized organization in a zone is appointed, be responsible for providing some name servers to this zone by it.Wherein, this name server (DNS) subtree contains first name server of the mapping of a whole domain name of being in charge of IP node in this private IP address territory and IP node location at least.When a new node joined in the zone, this regional DNS manager was domain name of this new node application and an IP node location, i.e. (public ip address) [: private IP address], and they are added in the database of name server.This zone can also further be divided into littler zonule as required.
Embodiment 1
As shown in Figure 4, in embodiment 1, first name server be in the public ip address territory, the border name server of the position in contiguous this private IP address territory.The whole domain name of IP node and the mapping of IP node location in this this private IP address territory of border domain name service management.At embodiment 1 owing to have only one first name server, therefore, node S1 in the A of private IP address territory (plan is according to the source node of the IP node location of the inquiry of the domain name destination node of destination node) needs the IP node location of search purposes ground node, it is at first sent out and asks this border name server, if this border name server relevant for the information of the IP node location of its destination node that will search, is just directly informed node S1 with the domain-name information response of destination node; In case border domain name (DNS) server does not find destination IP node location information in self database, whether it can ask the upper level dns server to be seen can find this IP node location information, the upper level dns server is not if also have, then ask upper level dns server again, this process can continue up to overtime or find answer.The rest may be inferred, up to inquiring the root name server that the uppermost circle of Fig. 4 is represented, root name server generally contains the information of name server at the IP node location place of the destination node that will search relevant for it, this name server just can return this information by first name server that response is successively asked to node S1, is returned the domain-name information of request then to node S1 by first name server.As seen, in embodiment 1, when the inquiry of domain name or IP node location need enter this private IP address territory, directly enter the border name server in this private IP address territory; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, inquiry also directly entered the border name server in this private IP address territory.
Embodiment 2
As shown in Figure 5, in embodiment 2, described first name server also be in the public ip address territory, the border name server of the position in contiguous this private IP address territory.As different from Example 1, this private IP address territory is marked off some zonules (being 4 among Fig. 5), one second name server is distributed in each zonule, and described second name server is all communicated by letter with first name server.
In embodiment 2, when the inquiry of domain name or IP node location need enter this private IP address territory, the inquiry of this domain name or IP node location at first enters the border name server in this private IP address territory, is transmitted to second name server in the respective cell territory by this border name server; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, at first this inquiry is issued the border name server in this private IP address territory, this inquiry is forwarded to name server in other the interference networks by it.
For example, node S1 in the A of private IP address territory (plan is according to the source node of the IP node location of the inquiry of the domain name destination node of destination node) needs the IP node location of search purposes ground node, it asks that second name server in the zonule at its place in the private IP address territory at first nearby, if store the information of the IP node location of the destination node that will search about it in this second name server, just directly node S1 is informed in destination node domain name information response, in case this second name server does not find destination IP node location information in self database, it can ask upper level dns server (being the border name server) to see whether to find this IP node location information, the upper level dns server is not if also find, then ask upper level dns server again, this process can continue up to overtime or find answer.And the like, up to inquiring the root name server that the uppermost circle of Fig. 5 is represented, root name server generally contains the information of name server at the IP node location place of the destination node that will search relevant for it, this name server just can return this information by second name server that response is successively asked to node S1, is returned the domain-name information of request then to node S1 by second name server.
Using the border name server is in order to consider in the expansion IPv4 network requirement to the host software source routing option as the service of transfer, in order to make DNS expansion can not produce possible influence, perhaps seamlessly transit simultaneously in order to make network can adapt to these situations to existing the Internet DNS system based on expansion IPv4.
Embodiment 3
As shown in Figure 6, in embodiment 3, described first name server is in this inside, private IP address territory.
In embodiment 3, when the inquiry of domain name or IP node location need enter this private IP address territory, this domain name or the inquiry of IP node location were forwarded to first name server of this inside, private IP address territory by the boundary point gateway (GA among Fig. 6) in public ip address territory and this private IP address territory; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, first name server of this inside, private IP address territory is transmitted to described boundary point gateway to this inquiry, this inquiry is forwarded to the name server in other the interference networks by the boundary point gateway.
For example, node S1 in the A of private IP address territory (plan is according to the source node of the IP node location of the inquiry of the domain name destination node of destination node) needs the IP node location of search purposes ground node, it is at first sent out and asks this first name server, if this first name server relevant for the information of the IP node location of its destination node that will search, is just directly informed node S1 with destination node domain name information response; In case this first domain name (DNS) server does not find destination IP node location information in self database, then this inquiry is forwarded to the boundary point gateway (GA among Fig. 6) in public ip address territory and this private IP address territory, be forwarded to its upper level dns server again, thereby request upper level dns server sees whether to find this IP node location information, the upper level dns server is not if also find, then ask upper level dns server again, this process can continue up to overtime or find answer.The rest may be inferred, up to inquiring the root name server that the uppermost circle of Fig. 6 is represented, root name server generally contains the information of name server at the IP node location place of the destination node that will search relevant for it, this name server just can return this information by first name server that response is successively asked to node S1, is returned the domain-name information of request then to node S1 by first name server.
Embodiment 4
As shown in Figure 7, embodiment 4 is with the different of embodiment 3: this private IP address territory is marked off some zonules, and one second name server is distributed in each zonule, and described second name server is all communicated by letter with first name server.
For example, node S1 in the A of private IP address territory (plan is according to the source node of the IP node location of the inquiry of the domain name destination node of destination node) needs the IP node location of search purposes ground node, it asks that second name server in the zonule at its place in the private IP address territory at first nearby, if store the information of the IP node location of the destination node that will search about it in this second name server, just directly node S1 is informed in destination node domain name information response; In case this second name server does not find destination IP node location information in self database, it can ask upper level dns server (i.e. first name server) to see whether to find this IP node location information, first name server is not if also find, then this inquiry is forwarded to the boundary point gateway (GA among Fig. 7) in public ip address territory and this private IP address territory, be forwarded to its upper level name server again, this upper level dns server is not if also find, then ask upper level dns server again, this process can continue up to overtime or find answer.The rest may be inferred, up to inquiring the root name server that the uppermost circle of Fig. 7 is represented, root name server generally contains the information of name server at the IP node location place of the destination node that will search relevant for it, this name server just can return this information by second name server that response is successively asked to node S1, is returned the domain-name information of request then to node S1 by second name server.
Embodiment 5
As shown in Figure 8, in embodiment 5, described first name server is in the overseas portion of this private IP address.
In embodiment 5, when the inquiry of domain name or IP node location need enter this private IP address territory, because described first name server is in the overseas portion of this private IP address, and this first domain name service management whole domain name of IP node and the mapping of IP node location in this private IP address territory, therefore need not enter inner relevant domain name or the IP node location information of just having access in this private IP address territory; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, the borde gateway (GA among Fig. 8) in public ip address territory and this private IP address territory at first is forwarded to this inquiry first name server of this overseas portion of private IP address, if there is not relevant information, again inquiry is forwarded to the name server in other the interference networks.
For example, node S1 in the A of private IP address territory (plan is according to the source node of the IP node location of the inquiry of the domain name destination node of destination node) needs the IP node location of search purposes ground node, it is at first sent out and asks this first name server, because first name server is in the overseas portion of private IP address, therefore, this inquiry is forwarded to first name server of this overseas portion of private IP address by means of the borde gateway (GA among Fig. 8) in public ip address territory and this private IP address territory, if this first name server relevant for the information of the IP node location of its destination node that will search, is just directly informed node S1 with the domain-name information response of destination node; In case first name server does not find destination IP node location information in self database, it can ask upper level domain name (DNS) server to see whether to find this IP node location information, the upper level dns server is not if also find, then ask upper level dns server again, this process can continue up to overtime or find answer.The rest may be inferred, up to inquiring the root name server that the uppermost circle of Fig. 8 is represented, root name server generally contains the information of name server at the IP node location place of the destination node that will search relevant for it, this name server just can return this information by first name server that response is successively asked to node S1, is returned the domain-name information of request then to node S1 by means of the borde gateway (GA among Fig. 8) in public ip address territory and this private IP address territory by first name server.
IP node location (IPD) the resource record definition of name server:
The distributed IP node location of depositing domain name, being associated with this domain name in above-mentioned each name server, this IP node location is defined as: public ip address [: private IP address], the wherein content selectable in [].This depositing stored some IP node locations (IPD) resource record by described each name server and carried out.The form of IP node location (IPD) resource record will be described below.
In expansion IPv4, the IP node just can find another any IP node by IP node location representation in the IPv4 of expansion network, and carries out the accessible communication of point-to-point.If, just be necessary in the DNS system, to carry out the conversion between representing of IP node domain name and IP node location so wish just can find any other IP node by DNS according to the domain name of IP node.Therefore, be necessary to define a kind of new resource record types IPD, IP node location of an IPD record storage is represented.The DNS inquiry of an IPD type will can not trigger other additional processing demands.
The form of IPD resource record and the definition of implication meet the definition about the DNS resource record, and concrete form as shown in Figure 9.Wherein:
● NAME: the DNS domain name of the IP node that this IPD resource record is relevant.
● TYPE:IPD resource record types sign indicating number is designated IPD, two bytes.The types value that the IPD resource record types is concrete will need to distribute by IANA.
● CLASS:IPD resource record class identification code is IN=1, two bytes.
● TTL: indicate the maximum number of seconds that this resource record can be buffered use, 32 bit strip symbol integers.
● RDLENGTH: indicate the byte number among the RDATA, 16 signless integers.
● RDATA: comprise the address sequence of IP node location, promptly deposit successively by sequence of addresses in (public ip address) [: private IP address].The IPD resource record need be stored one or two IP address, i.e. 4 bytes or 8 byte lengths.For example, for IP node S1, its IPD is expressed as 202.99.0.9:172.18.10.8, and then its RDLENGTH is 8, the decimal representation in RDATA following (all ". " wherein and ": " can not appear at the former capital is omitted in the DNS packet):
202?99?0?9?172?18?10?8
In addition, described each name server is also stored the pointer resource record (PTR RR) of the reverse inquiry that is used for from the IP node location to domain name, and the IP address sequence of the IP node location that this pointer resource record contains domain name, be associated with this domain name carries out adding the sequence that IPD.INT forms behind the byte reversal.Specifically, as shown in figure 10, the form of described pointer resource record (PTR RR) is as follows:
● NAME: the domain name of the IP node relevant with this pointer resource record;
● TYPE: pointer resource record types sign indicating number;
● CLASS: pointer resource record class identification code;
● TTL: indicate the maximum number of seconds that this pointer resource record can be buffered use;
● RDLENGTH: indicate the byte number among the RDATA;
● RDATA: the IP address sequence of the IP node location that this domain name is associated carries out adding the sequence that IPD.INT forms behind the byte reversal.
When the reverse inquiry carried out from the IP node location to domain name, the IP address sequence of this IP node location is carried out byte reversal, and add IPD.INT, then with name server in RDATA territory in the described pointer resource record (PTR RR) stored compare, if coupling then contains the domain name that inquires in the NAME territory in the pointer resource record of this coupling (PTR RR).
That is to say that the present invention uses pointer resource record (PTR RR) to carry out the mapping of IP node location (IPD) to domain name.In the DNS of IPv4 domain name system, defined PTR RR so that realize that in the IN-ADDR.ARPA territory IPv4 address is to the map locating between the domain name.Similarly, domain name inverse query can define a new territory " IPD.INT " among the EIPv4, utilizes IPDPTR RR to realize representing domain name by domain name system inquiry IP node according to known IP node location.
A sequence that is used for inquiry of the domain name can produce by following rule according to IPD: the IP address sequence of IP node location is pressed byte reversal, and every byte is all as a subdomain independently, and in the end is connected in series top subdomain name " IPD.INT ".For example for the following IPD of reverse find
202.99.0.9：172.18.10.8
The domain name of structure will be expressed as when at this moment, oppositely inquiring about according to this IPD
8.10.18.172.9.0.99.202.IPD.INT
Figure 11 is according to an example of the present invention, and source IP node finds this destination IP node location according to destination IP node domain name, and IP node in destination carries out the method schematic diagram of authenticate reverse then.We do a comprehensive review by the DNS extended attribute of this example expansion IPv4 of by the agency of.Suppose that a source IP node need find this destination IP node location according to destination IP node domain name, this source IP node at first starts the Rlogin CLIENT PROGRAM (so that being connected to a Rlogin server that is positioned at other territories such as public ip address territory) of this this machine of node.The Rlogin CLIENT PROGRAM is the content of prior art, all can move automatically when wanting with other node communication at every turn.
Figure below has shown the packet switching process that takes place.
11 steps that take place are below all supposed in the high-speed cache of client and server without any information.Content is to select for the available transfer that the DNS expansion is seamlessly transitted in its bracket.
(1) after the Rlogin CLIENT PROGRAM started, the domain name of the destination IP node that the domain name mapping device function that source IP node calls it communicates with wanting of keying in of user was converted to a request and is sent to a root name server according to the query requests of the IPD type of inquiry of the domain name destination, destination IP node location (the border name server that is associated by private IP address territory, IP node place, source).
(2) comprise the name of the name server that has destination node-Rlogin server location information in the response that (the border name server that is associated by private IP address territory, IP node place, source) returned by root name server.
(3) (the border name server that is associated by private IP address territory, IP node place, source,) the domain name mapping device function of source IP node will retransmit the inquiry of above-mentioned IP D type to the above-mentioned name server that has destination node-Rlogin server location information, this inquiry expects that normally the recurrence sign is set to 1.
(4) (the border name server that is associated by private IP address territory, IP node place, source) this name server that has destination node-Rlogin server location information returns comprises the IP node location of destination node-Rlogin server in replying.
(5) source node-Rlogin client and destination node-Rlogin server are set up a TCP according to expansion IPv4 principle and are connected.To exchange handshake packet between the tcp module of client and server.
(6) after the Rlogin server is received connection request from the source node client, the IP node location (IPD) that calls the source node client that its domain name mapping device function will analyze from the TCP connection request is converted to the query requests of request according to the IPD PTR type of the domain name of IP node location (IPD) the query source IP node of source IP node, is forwarded to a root name server and handles.This root name server can be different from the root name server that the source node client is used in the step (1).
(7) contain the name of the name server that has source node-Rlogin client computer domain name and positional information in the response of this root name server.
(8) the domain name mapping device function on (the border name server that is associated by private IP address territory, IP node place, source) Rlogin server will retransmit above-mentioned IP D PTR inquiry to the name server that has source node-Rlogin client computer domain name and positional information.
(9) domain name that contains source node-Rlogin Client Host during the IPD PTR that returns of (the border name server that is associated by private IP address territory, IP node place, source) this name server that has source node-Rlogin client computer domain name and positional information replys.
(10) (the border name server that is associated by private IP address territory, IP node place, source,) the domain name mapping device function of server sends an IPD type query requests to the name server that has source node-Rlogin client computer domain name and positional information, searches the pairing IP node location of domain name (IPD) that back returns.This may be finished automatically by certain function such as the gethostbyIPD in the server, otherwise the Rlogin server will be finished this step.In addition, the name server that this step is inquired about is exactly the name server of being inquired about in the step (8) usually, but this is optional.
(11) (the border name server that is associated by private IP address territory, IP node place, source) response of returning from the name server that has source node-Rlogin client computer domain name and positional information contains IP node location (IPD) record of source node-Rlogin client computer.The Rlogin server with the IP node location (IPD) in client's the TCP connection request therewith IPD record make comparisons.
High-speed cache will reduce the grouping number that exchanges among this figure.
By utilizing the present invention, make expansion IPv4 can access smooth popularization.People can use according to the custom of existing the Internet when using, the present invention is based on expansion IPv4 existing DNS system is expanded, comprise the resource record and the using method of DNS system extension when in expansion IPv4, carrying out changing between IP node domain name and the IP node location of expansion framework, the redetermination of DNS.

Claims (12)

1. domain name server system in extendible IPv4 network based on the source routing mode, wherein on the basis of the domain name server system in the public ip address territory of existing IPv4, the publicly-owned address field of IP edge in extendible IPv4 network based on the source routing mode, for the private IP address territory derives independently name server (DNS) subtree, this name server (DNS) subtree contains first name server of the mapping of a whole domain name of being in charge of IP node in this private IP address territory and IP node location at least, wherein, describedly comprise public ip address territory and private IP address territory, between described publicly-owned address field and described privately owned address field, be connected with public and private address field boundary point gateway based on the extendible IPv4 network of source routing mode.
2. according to the domain name server system of claim 1, wherein this private IP address territory is marked off some zonules, one second name server is distributed in each zonule, and described second name server is all communicated by letter with first name server.
3. according to the domain name server system of claim 2, wherein said first name server be in the public ip address territory, the border name server of the position in contiguous this private IP address territory.
4. according to the domain name server system of claim 3, wherein when the inquiry of domain name or IP node location need enter this private IP address territory, the inquiry of this domain name or IP node location at first enters first name server in this private IP address territory, is transmitted to second name server in the respective cell territory by this border name server; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, at first this inquiry is issued the border name server in this private IP address territory, this inquiry is forwarded to name server in other the interference networks by it.
5. according to the domain name server system of claim 1, wherein said first name server is in this inside, private IP address territory.
6. according to the domain name server system of claim 5, wherein when the inquiry of domain name or IP node location need enter this private IP address territory, this domain name or the inquiry of IP node location are by the boundary point gateway forwards in public ip address territory and this private IP address territory first name server to this inside, private IP address territory; When the inquiry of domain name or IP node location need enter the public ip address territory from the private IP address territory, first name server of this inside, private IP address territory is transmitted to described boundary point gateway to this inquiry, this inquiry is forwarded to the name server in other the interference networks by the boundary point gateway.
7. according to the domain name server system of claim 1, wherein said first name server is in the overseas portion of this private IP address.
8. according to the domain name server system of claim 1, the distributed IP node location of depositing domain name, being associated in wherein said each name server with this domain name, this IP node location is defined as: public ip address [: private IP address], the wherein content selectable in [].
9. domain name server system according to Claim 8, wherein said each name server is stored some IP node location IPD resource records, and every IP node location IPD resource record form is as follows:
● NAME: the domain name of the IP node relevant with this IP node location IPD resource record;
● TYPE:IPD resource record types sign indicating number is designated IPD;
● CLASS:IPD resource record class identification code is IN=1;
● TTL: indicate the maximum number of seconds that this resource record can be buffered use;
● RDLENGTH: indicate the byte number among the RDATA;
● RDATA: comprise the address sequence of IP node location, promptly press: the sequence of addresses of public ip address [: private IP address] is deposited successively.
10. according to the domain name server system of claim 1, wherein said each name server is also stored the pointer resource record (PTR RR) of the reverse inquiry that is used for from the IP node location to domain name, and the IP address sequence of the IP node location that this pointer resource record contains domain name, be associated with this domain name carries out adding the sequence that top subdomain name IPD.INT forms behind the byte reversal.
11. according to the domain name server system of claim 10, the form of wherein said pointer resource record (PTR RR) is as follows:
● NAME: the domain name of the IP node relevant with this pointer resource record;
● TYPE: pointer resource record types sign indicating number;
● CLASS: pointer resource record class identification code;
● TTL: indicate the maximum number of seconds that this pointer resource record can be buffered use;
● RDLENGTH: indicate the byte number among the RDATA;
● RDATA: the IP address sequence of the IP node location that this domain name is associated carries out adding the sequence that IPD.INT forms behind the byte reversal.
12. domain name server system according to claim 11, wherein when the reverse inquiry carried out from the IP node location to domain name, the IP address sequence of this IP node location is carried out byte reversal, and add IPD.INT, then with name server in RDATA territory in the described pointer resource record (PTR RR) stored compare, if coupling then contains the domain name that inquires in the NAME territory in the pointer resource record of this coupling (PTR RR).
CN2007101661957A 2007-11-13 2007-11-13 Domain name server system of extended IPv4 network Active CN101436981B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2007101661957A CN101436981B (en) 2007-11-13 2007-11-13 Domain name server system of extended IPv4 network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2007101661957A CN101436981B (en) 2007-11-13 2007-11-13 Domain name server system of extended IPv4 network

Publications (2)

Publication Number Publication Date
CN101436981A CN101436981A (en) 2009-05-20
CN101436981B true CN101436981B (en) 2011-12-07

Family

ID=40711213

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007101661957A Active CN101436981B (en) 2007-11-13 2007-11-13 Domain name server system of extended IPv4 network

Country Status (1)

Country Link
CN (1) CN101436981B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101917494B (en) * 2010-09-09 2013-05-15 刁永平 Realization of autonomous Internet
US9204290B2 (en) * 2010-11-03 2015-12-01 Telefonaktiebolaget L M Ericsson (Publ) Method and system for constructing a domain name for a radio network node in a cellular communication system
WO2012072135A1 (en) * 2010-12-01 2012-06-07 Nokia Siemens Networks Oy Apparatus and method for establishing connections
CN104303489A (en) * 2012-04-30 2015-01-21 Nec欧洲有限公司 Method for performing dns resolution in a network, content distribution system and client terminal for deployment in a content distribution system
CN102932496B (en) * 2012-10-10 2017-03-29 瑞斯康达科技发展股份有限公司 A kind of method and system of management domain name system information
CN103957285B (en) * 2014-04-18 2015-09-09 北京奇虎科技有限公司 The method and system of root domain name resolution service is provided
CN106161269A (en) * 2015-04-17 2016-11-23 华为技术有限公司 A kind of data pack transmission method, controller and switch
CN109145092B (en) * 2017-06-15 2022-05-17 阿里巴巴集团控股有限公司 Database updating and intelligent question and answer management method, device and equipment
CN107835175B (en) * 2017-11-09 2020-09-22 深圳市云盾科技有限公司 Network connection tracking method adopting balanced binary tree algorithm

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1406026A (en) * 2001-09-16 2003-03-26 华为技术有限公司 Combined address resolving scheme and combined address route device thereof
CN1505322A (en) * 2002-12-04 2004-06-16 ��Ϊ�������޹�˾ A management method of network device
US7603410B1 (en) * 2001-05-14 2009-10-13 At&T Intellectual Property Ii, L.P. System having generalized client-server computing

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7603410B1 (en) * 2001-05-14 2009-10-13 At&T Intellectual Property Ii, L.P. System having generalized client-server computing
CN1406026A (en) * 2001-09-16 2003-03-26 华为技术有限公司 Combined address resolving scheme and combined address route device thereof
CN1505322A (en) * 2002-12-04 2004-06-16 ��Ϊ�������޹�˾ A management method of network device

Also Published As

Publication number Publication date
CN101436981A (en) 2009-05-20

Similar Documents

Publication Publication Date Title
CN101436981B (en) Domain name server system of extended IPv4 network
US9866523B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
CN100536444C (en) Data packet commmunication device
US8351430B2 (en) Routing using global address pairs
US8090843B2 (en) Creating a public identity for an entity on a network
CN101043447B (en) Method for mapping dynamically inside and outside network of server based on DDNS and NAT
CN102938735B (en) Advertising of route is used to carry the method that option issues NAT64 address prefix
CN112840601B (en) Method, apparatus and computer readable medium for configuring an apparatus to be named
US20090222581A1 (en) Internet location coordinate enhanced domain name system
CN104734963A (en) IPv4 and IPv6 network interconnection method based on SDN
CN104427010A (en) NAT (network address translation) method and device applied to DVPN (dynamic virtual private network)
CN103856580B (en) A kind of method that IPv6 client computer accesses IPv4 servers
KR20050086925A (en) System and method for establishing communication between a client and a server in a heterogenous ip network
JP2001103092A (en) Dns inquiry device, dns inquiry method and recording medium
CN102394947B (en) Translation method, device and system and ALG device for IPv4 and IPv6 addresses
CN102739809A (en) DNS64 database, server, system and IPv4/IPv6 communication method
CN103118145B (en) Based on the IPv4-over-IPv6 Multiple tunnel auto-creating method of DNS
CN110691150A (en) SDN-based IPv4 and IPv6 interconnection method and system
JP2003258838A (en) Communication equipment and network system
CN102204191A (en) A message transmission method and a network-network routing device
CN100459572C (en) Message transformation realizing method based on port from IPv4 to IPv6 network
CN100518147C (en) Method for spanning heterogeneous network mobile telecommunication based on two-way tunnel
CN103581258A (en) Network data caching method and system
CN104717639A (en) Access method for mobile client to internet and access gateway server
CN101175096A (en) Implementation of expandable IP network based on source routing

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant