CN100454891C

CN100454891C - IPv6/IPv4 converter

Info

Publication number: CN100454891C
Application number: CNB200510006248XA
Authority: CN
Inventors: 宫田宏; 远藤正仁
Original assignee: Yokogawa Electric Corp
Current assignee: Yokogawa Electric Corp
Priority date: 2005-02-02
Filing date: 2005-02-02
Publication date: 2009-01-21
Anticipated expiration: 2025-02-02
Also published as: CN1816001A

Abstract

The present invention relates to a converter structure which can be used when a target of service is supplied to general clients with no need of changing specifications of a DNS server, particularly to an IPv6/IPv4 converter which can be converted between an IPv6 agreement and an IPv4 agreement, and uses a configuration to make DNS inquiry from a client terminal to a converter DNS proxy server which uses an exclusive network domain with equal effectiveness with a specific DNS network domain. The proxy server can designate operation through predefined character strings which are input in FQDN, the clients can designate address based on the IPv6 or the IPv4 as a wish address at least in the FQDN, and the clients can at least designate a converting address or a non-converting address as an address used for returning replies. If necessary, communication through the converter can be used with no need of changing specifications of a DNS server on a client terminal, and if necessary, users can communicate through the converter by using a definite designation address. Besides, general non-designated clients can also communicate through the converter.

Description

The IPv6/IPv4 transducer

Technical field

The present invention especially produces relevant for automatic address about the IPv6/IPv4 transducer.

Background technology

About the description of title division conversion between IPv6 and IPv4 agreement, can find the 0049th section of patent documentation 1.

Yet patent documentation 1 is described packet handler, packet processing method and packet switcher, and purpose is the saving of realization memory, and realizes level and smooth pipeline, and in this was handled, the access of shared storage there is no warfare between the processing of different stratum.

With above-mentioned opposite, the present invention allows automatic address to produce, and need not change the address setting of Domain Name System (below be abbreviated as DNS), so its purpose and patent documentation 1 are different.

[patent documentation 1]

Japanese Laid-Open Patent Application case 2000-115234.

It is a skill that the IPv6/IPv4 transducer uses the method to offer the environment that the user is easy to, and utilizes this skill, dns server with address transition as a method that produces dynamic address.Specifically, utilize and to send from the client that a inquiry packet to the project equipment with DNS Proxy function among the DNS realizes.This means provides automatic address to produce service to a given client.

Generally speaking, send DNS inquiry, the DNS proxy server that the client need be correlated with the address setting of dns server to a specific DNS proxy server.

Yet, owing to, can't expect this setting changing, be to have one to need not this visitor and hold the setting that changes dns server can utilize the structure of IPv6/IPv4 transducer to one without the visitor of appointment end.

The invention provides a structure, need not this visitor therein and hold the setting that changes dns server can utilize the IPv6/IPv4 transducer.

Fig. 1 is the client with the DNS Proxy function of the transducer calcspar as dns server.In Fig. 1, client 1 produces for the automatic address that utilizes DNS, the DNS proxy server of transducer 2 must be specified as dns server.DNS proxy server in the transducer 2 will be by the type of this address acquisition, and the address style of being inquired about and the proper address that content determined of setting are transmitted back to client 1.

Fig. 2 is the operating instruction figure when the client inquires about an IPv6 address, shows the example that the IPv6 address produces automatically.

(1) client 1 for DNS proxy server 2 require " Www.The ox Δ .com" IPv6 address (" AAAA " record).

(2) DNS proxy server 2 will transfer to dns server 3 from client 1 requirement.

(3) dns server 3 is not presented at name server in this figure to other, proposes and " the www.ox Δ .com " inquiry of corresponding IPv6 address.Yet dns server 3 obtains to respond and is: do not have corresponding IPv6 address.(if corresponding IPv6 address was arranged at that time, then DNS proxy server 2 is transmitted back to client 1 with the IPv6 address that is received)

(4) DNS proxy server 2 requires and " www.ox Δ .com " corresponding IPv4 address (" A " record) to dns server 3.

(5) dns server 3 is not presented at name server in this figure to other, proposes and " the www.ox Δ .com " inquiry of corresponding IPv4 address, and obtains the IPv4 address of correspondence, and DNS proxy server 2 is circulated a notice of these addresses.

(6) DNS proxy server 2 utilizes for this IPv4 map addresses is produced an address to the virtual preamble of preparing to the IPv6 address, and this address is transmitted back to client 1 as the IPv6 address.

Fig. 3 is the operating instruction figure when the client inquires about an IPv4 address, and shows the example that produces an IPv4 address automatically.

(1) client 1 for DNS proxy server 2 require " Www.The ox Δ .com" IPv4 address (" A " record).

(2) DNS proxy server 2 will transfer to dns server 3 from client 1 requirement.

(3) dns server 3 is not presented at name server in this figure to other, proposes and " the www.ox Δ .com " inquiry of corresponding IPv4 address.Yet dns server 3 obtains to respond and is: do not have corresponding IPv4 address.(if corresponding IPv4 address was arranged at that time, then DNS proxy server 2 is passed the IPv4 address of this reception back to client 1.)

(4) 2 pairs of dns servers of DNS proxy server 3 require and " www.ox Δ .com " corresponding IPv6 address (" AAAA " record).

(5) dns server 3 is not presented at name server in this figure to other, proposes and " the www.ox Δ .com " inquiry of corresponding IPv6 address, and obtains the IPv6 address of correspondence, and DNS proxy server 2 is circulated a notice of these addresses.

(6) DNS proxy server 2 will give this IPv6 address for the IPv4 address assignment that this IPv6 map addresses is prepared to the IPv4 address, and this address is transmitted back to client 1 as the IPv4 address.

As long as environment allows that the client can be appointed as dns server with the DNS proxy server of transducer, these traditional usages are no problem definitely.Yet when service provides when giving unspecific common customer, so setting changing promptly can't be expected.

Summary of the invention

The present invention desires to address the above problem, its purpose with common customer when the service object is provided, realize that a kind of dns server specification that need not to change visitor's end can use the structure of transducer.

Therefore, the present invention is about a kind of IPv6/IPv4 transducer, can be between IPv6 and IPv4 agreement convert packets reciprocally; And utilize the exclusive net territory that can be used as an effective specific DNS net territory so that allow the DNS proxy server that can reach this transducer from client's DNS inquiry; This transducer DNS proxy server utilization input is specified an operation in the interior defined character string of complete qualified domain name (FQDN) (Fully qualified Domain Name).

In addition, of the present invention being characterized as: being specified by this client among the FQDN is an address of wishing based on the address of IPv6 or based on the address of IPv4, and also can by the client specify one reference address or not the reference address be one to respond the address.

According to the present invention, need not to change the dns server specification of client, can be according to need utilizing communication via a transducer, and the user utilizes the mode of specifying a hard objectives address, and can be according to setting up communication through a transducer.

In addition, because of need not to specify a transducer, even general unspecified client can utilize the communication via a transducer.

Even, but the address transition policy of the DNS proxy server of user's designated conversion device.

Description of drawings

Fig. 1 is the calcspar when the DNS of transducer Proxy function is used as dns server by the client.

The key diagram of the example operation when Fig. 2 inquires about an IPv6 address for the demonstration client.

The key diagram of the example operation when Fig. 3 inquires about an IPv4 address for the demonstration client.

Fig. 4 is the key diagram that is presented at the example operation in one embodiment of the invention.

Fig. 5 is the key diagram that is presented at the example operation in another embodiment of the present invention.

Fig. 6 is the key diagram that is presented at the example operation in further embodiment of this invention.

Fig. 7 is the key diagram that is presented at the example operation in further embodiment of this invention.

Fig. 8 is a functional block diagram of the operation of key diagram 4.

Fig. 9 is a functional block diagram of the operation of key diagram 5.

Figure 10 is a functional block diagram of the operation of key diagram 6.

Figure 11 is a functional block diagram of the operation of key diagram 7.

Embodiment

Below with reference to accompanying drawing the present invention is illustrated in detail.In the present invention, preparation one net territory is so that allow the DNS inquiry arrive at the DNS proxy server of a transducer.Although " 6x4.org " is assumed that a domain name in the following description, in the reality in the elsewhere not as an effective domain name or a Hostname.Arbitrary net territory all can be accepted, but as long as it is the DNS proxy server of designated conversion device, gets final product as the net territory of the name server with this domain name.The DNS proxy server of transducer is registered as " 6x4.org " used name server.

Fig. 4 is the key diagram that shows the example of operation in one embodiment of the invention, and shows as if accepting for " A " the operation the when FQDN of the inquiry of record has one " A " record.

(1) client 4 is for the dns server 5 of designated requirement inquiry as name server, require " www.ox Δ .com.6x4.org " and IPv4 address (" A " record).

(2) require the name server of the server 5 of inquiry for " 6x4.org " net territory, the IPv4 address of inquiry " www.ox Δ .com.6x4.org ".Because the name server in " 6x4.org " net territory is the DNS proxy server of transducer, this inquiry arrives the DNS proxy server 6 of transducer.

(3) the DNS proxy server 6 of transducer is for passing on target dns server 7, and inquiry is from " " (that is FQDN of previous existing inquiry) removes " www.ox Δ .com " and the address of the IPv4 of the FQDN " www.ox Δ .com " that obtains to www.ox Δ .com.6x4.org.Pass on target dns server 7 for other name server inquiries and " www.ox Δ .com " corresponding IPv4 address of not being shown among the figure, and accept corresponding IPv4 address.

(4) passing on target dns server 7 will be returned to the IPv4 address of the DNS proxy server 6 of transducer as " www.ox Δ .com " as the IPv4 address that receives for the response of aforementioned inquiry.

(5) the DNS proxy server 6 of the transducer IPv4 address that will receive is transmitted back to the dns server 5 that requires inquiry, as the IPv4 address of " www.ox Δ .com.6x4.org ".

(6) dns server 5 that requires inquiry is passed this receiver address back to client 4 with similar methods.

Fig. 5 is the key diagram that is presented at the example operation in another embodiment of the present invention, and show inquired about " A " do not have " A " record among the FQDN of record but operation when having " AAAA " record.

(1) client 4 requires the IPv4 address (" A " record) of " www.ox Δ .com.6x4.org " for the dns server 5 of the requirement inquiry that is designated as name server.

(2) server 5 that requires inquiry for " 6x4.org " name server in net territory, the IPv4 address of inquiry " www.ox Δ .com.6x4.org ".Because the name server in " 6x4.org " net territory is the DNS proxy server of transducer, this inquiry arrives the DNS proxy server 6 of transducer.

(3) the DNS proxy server 6 of transducer is for passing on target dns server 7, and inquiry removes " www.ox Δ .com " and the address of the IPv4 of the FQDN " www.ox Δ .com " that obtains from " www.ox Δ .com.6x4.org " (that is FQDN of previous existing inquiry).

(4) passing on target dns server 7 does not show in the drawings name server inquiry and " www.ox Δ .com " corresponding IPv4 address for other, but receives the non-existent response in corresponding IPv4 address, and with the DNS proxy server 6 of this response notification transducer.

(5) the DNS proxy server 6 of transducer is for passing on target dns server 7, inquiry with " www.ox Δ .com " corresponding IPv6 address (" AAAA " writes down).

(6) passing on target dns server 7 does not show in the drawings name server inquiry and " www.ox Δ .com " corresponding IPv6 address for other, and obtains the IPv6 address of correspondence, afterwards this address is notified the DNS proxy server 6 of transducer.

(7) the DNS proxy server 6 of transducer with preparation map to the IPv6 address the IPv4 address one of them, map to the IPv6 address of this reception, and pass this address back to the dns server 5 that requires to inquire about, as IPv4 address corresponding to " www.ox Δ .com.6x4.org ".

(8) dns server 5 of requirement inquiry is returned to client 4 with the address that derives from the DNS proxy server 6 of transducer, as the IPv4 address corresponding to " www.ox Δ .com.6x4.org ".

Fig. 6 is also for being presented at the present invention's key diagram of the example operation in another embodiment again, and shows the operation when having " AAAA " record among the FQDN that is subjected to inquiry " AAAA " record.

(1) client 4 requires the IPv6 address (" AAAA " record) of " www.ox Δ .com.6x4.org " for the dns server 5 of the requirement inquiry that is designated as name server.

(2) require the name server of the server 5 of inquiry, the IPv6 address of inquiry " www.ox Δ .com.6x4.org " for " 6x4.org " net territory.Because the name server in " 6x4.org " net territory is the DNS proxy server 6 of transducer, this inquiry arrives the DNS proxy server 6 of transducer.

(3) the DNS proxy server 6 of transducer is for passing on target dns server 7, and inquiry removes " www.ox Δ .com " and the address of the IPv6 of the FQDN " www.ox Δ .com " that obtains from " www.ox Δ .com.6x4.org " (that is FQDN of previous existing inquiry).The target dns server 7 that passes on does not show in the drawings name server inquiry and " www.ox Δ .com " corresponding IPv6 address and the IPv6 address of reception correspondence for other.

(4) passing on target dns server 7 will receive the DNS proxy server 6 that the IPv6 address is transmitted back to this transducer, as the IPv6 address of " www.ox Δ .com ".

(5) the DNS proxy server 6 of transducer is transmitted back to the dns server 5 that requires inquiry with the IPv6 address that receives, as the IPv6 address of " www.ox Δ .com.6x4.org ".

Fig. 7 is also for being presented at the present invention's key diagram of the example operation in another embodiment again, and shows and do not have this " AAAA " record among the FQDN that is subjected to inquiry " AAAA " record but have " A " operation when writing down.

(2) require the name server of the server 5 of inquiry, the IPv6 address of inquiry " www.ox Δ .com.6x4.org " for " 6x4.org " net territory.Because the name server in " 6x4.org " net territory is the DNS proxy server of transducer, this inquiry arrives the DNS proxy server 6 of transducer.

(3) the DNS proxy server 6 of transducer is for passing on target dns server 7, and inquiry removes " www.ox Δ .com " and the address of the IPv6 of the FQDN " www.ox Δ .com " that obtains from " www.ox Δ .com.6x4.org " (that is FQDN of previous existing inquiry).

(4) passing on target dns server 7 does not show in the drawings name server inquiry and " www.ox Δ .com " corresponding IPv6 address for other, but receives the non-existent response in corresponding IPv6 address, and with the DNS proxy server 6 of this response notification transducer.

(5) the DNS proxy server 6 of transducer is inquired about the IPv4 address corresponding with " www.ox Δ .com " (" A " record) for passing on target dns server 7.

(6) passing on target dns server 7 does not show in the drawings name server inquiry and " www.ox Δ .com " corresponding IPv4 address for other, and obtains the IPv4 address of correspondence, afterwards this address is notified the DNS proxy server 6 of transducer.

(7) the DNS proxy server 6 of transducer produces an IPv6 address of preparing in order to map to the IPv6 address, this address has the virtual prefix of an IPv6 in higher 64, and in hanging down 32, has the IPv4 address, and this address is transmitted back to the dns server 5 that requires inquiry, as with " www.ox Δ .com.6x4.org " corresponding IPv6 address.

(8) address that requires the dns server 5 of inquiry to accept is transmitted back to client 4, as with " www.ox Δ .com.6x4.org " corresponding IPv6 address.

The functional block diagram of the typical operation when having " A " record among the FQDN of Fig. 8 for explanation acceptance shown in Figure 4 inquiry " A " record, and each inquiry with respond the contents are as follows shown in.

Inquiry A [inquiry of " A " record of " www.ox Δ .com.6x4.org "]

Inquiry B [inquiry of " A " record of " www.ox Δ .com "]

Respond A [inquiry of " A " record of " www.ox Δ .com.6x4.org "]

Respond A ' [the NS record (name server) of " org "]

Response A " [the NS record (name server) of " 6x4.org "]

Respond B [" A " record of " www.ox Δ .com "]

In Fig. 8 each time inquiry is carried out as follows with the exchange of responding:

(1) client 4 inquires about A with inquiry " www.ox Δ .com.6x4.org " for the dns server 5 that requires to inquire about " A " record.

(2) require the dns server 5 of inquiry to send inquiry A and claim server 8 to root name.

(3) root name claims server 8, sends with the NS of " org " and writes down corresponding response A ', to the dns server 5 that requires to inquire about.

(4) require the dns server 5 of inquiry to send the name server of inquiry A to " org " 9.

(5) name server of " org " 9, will with the corresponding response A of the NS of " 6x4.org " record " be sent to and require the dns server 5 inquired about.

(6) require the dns server 5 of inquiry to send the DNS proxy server 6 of inquiry A to this transducer.

(7) the inquiry B of " A " record of DNS proxy server 6 transmissions " www.ox Δ .com " of transducer is to passing on target dns server 7.

(8) pass on target dns server 7 to other do not show in the figure name server inquiry " Www.oxΔ .com" A " record.

(9) pass on target dns server 7 receive corresponding to " Www.oxΔ .com" A " record response B, as response to above-mentioned inquiry.

(10) pass on target dns server 7 will with the corresponding response B of " A " of " www.ox Δ .com " record, be sent to the DNS proxy server 6 of this transducer.

(11) the DNS proxy server 6 of transducer will be sent to the dns server 5 that requires inquiry corresponding to the response A of the inquiry of " A " of " www.ox Δ .com.6x4.org " record.

(12) dns server 5 of requirement inquiry sends it back and answers A to client 4.

Fig. 9 is explanation acceptance inquiry shown in Figure 5 " A " do not have among the FQDN of record " A " record but have " AAAA " the functional block diagram of typical operation during record, and each inquiry with respond the contents are as follows shown in.

Inquiry A [inquiry of " A " record of " www.ox Δ .com.6x4.org "]

Inquiry B [inquiry of " A " record of " www.ox Δ .com "]

Inquiry C [inquiry of " AAAA " record of " www.ox Δ .com "]

Respond A [inquiry of " A " record of " www.ox Δ .com.6x4.org "]

Respond A ' [the NS record (name server) of " org "]

Response A " [the NS record (name server) of " 6x4.org "]

Respond B [" A " record (not existing) of " www.ox Δ .com "]

Respond C [" AAAA " record of " www.ox Δ .org "]

Among Fig. 9 each time inquiry is carried out as follows with the exchange of responding:

(1) client 4 inquires about A " A " record with inquiry " www.ox Δ .com.6x4.org " for the dns server 5 that requires to inquire about.

(3) root name claims server 8 that the response A ' corresponding with the NS record of " org " is sent to the dns server 5 that requires inquiry.

(5) " org " 9 name server, will " be sent to and require the dns server 5 inquired about with the corresponding response A of NS record of " 6x4.org ".

(7) the DNS proxy server 6 of this transducer is sent to the inquiry B of the A of " www.ox Δ .com " record and passes on target dns server 7.

(8) passing on target dns server 7 does not show in the figure name server inquiry " www.ox Δ .com's " A to other " record.

(9) passing on target dns server 7 receives Www.oxΔ .com" A " the non-existent response B of record.

(10) passing on target dns server 7 is sent to the non-existent response of " A " of " www.ox Δ .com " record B the DNS proxy server 6 of transducer.

(11) the DNS proxy server 6 of transducer with the inquiry C of " AAAA " of " www.ox Δ .com " record, is sent to and passes on target dns server 7.

(12) pass on " AAAA " record of the name server inquiry " www.ox Δ .com " of target dns server 7 in other are not presented at this figure.

(13) pass on target dns server 7 receive " www.ox Δ .com " " AAAA " record response C.

(14) passing on target dns server 7 will be sent to the DNS proxy server 6 of this transducer corresponding to the response C of the inquiry of " AAAA " of " www.ox Δ .com " record.

(15) the DNS proxy server 6 of transducer will be sent to the dns server 5 that requires inquiry corresponding to the response A of the inquiry of " A " of " www.ox Δ .com.6x4.org " record.

(16) dns server 5 of requirement inquiry sends it back and answers A to client 4.

Figure 10 is explanation acceptance inquiry shown in Figure 6 " AAAA " the functional block diagram of typical operation when having " AAAA " record among the FQDN of record, and each inquiry with respond the contents are as follows shown in.

Inquiry A [" Www.oxΔ .com.6x4.org" " AAAA " record inquiry]

Inquiry B [" Www.oxΔ .com" " AAAA " record inquiry]

Response A [" Www.oxΔ .com.6x4.org" " AAAA " record]

Respond A ' [the NS record (name server) of " org "]

Response A " [the NS record (name server) of " 6x4.org "]

Respond B [" Www.oxΔ .com" " AAAA " record]

Among Figure 10 each time inquiry is carried out as follows with the exchange of responding:

(1) client 4 for the dns server 5 that requires to inquire about inquire about A with the inquiry " www.ox Δ .com.6x4.org " and " AAAA " record.

(3) root name claim server 8 will " org " and the corresponding response A ' of NS record be sent to the dns server 5 that requires inquiry.

(4) require the dns server 5 of inquiry send inquiry A to " org " 9 name server.

(5) " org " 9 name server will " 6x4.org " and the corresponding response A of NS record " be sent to the dns server 5 that requires inquiry.

(7) the DNS proxy server 6 of transducer will " www.ox Δ .com " and the inquiry B of " AAAA " record be sent to and pass on target dns server 7.

(8) passing on target dns server 7 does not show in the figure name server inquiry to other " www.ox Δ .com " " AAAA " record.

(9) pass on target dns server 7 receive corresponding to " Www.oxΔ .com" " AAAA " record response B.

(10) passing on target dns server 7 will be sent to the DNS proxy server 6 of this transducer corresponding to the response B of " AAAA " of " www.ox Δ .com " record.

(11) the DNS proxy server 6 of this transducer will be corresponding to the response A of the inquiry of " AAAA " of " www.ox Δ .com.6x4.org " record, is sent to pass on target dns server 5.

Do not have " AAAA " record among the FQDN of Figure 11 for explanation acceptance shown in Figure 7 inquiry " AAAA " record but have " A " the diagram of operation during record, and each inquiry with respond the contents are as follows shown in.

Inquiry A [inquiry of " AAAA " record of " www.ox Δ .com.6x4.org "]

Inquiry B [inquiry of " AAAA " record of " www.ox Δ .com "]

Inquiry C [inquiry of " A " record of " www.ox Δ .com "]

Respond A [" AAAA " record of " www.ox Δ .com.6x4.org "]

Respond A ' [the NS record (name server) of " org "]

Response A " [the NS record (name server) of " 6x4.org "]

Respond B [" AAAA " record (not existing) of " www.ox Δ .com "]

Respond C [" A " record of " www.ox Δ .org "]

Among Figure 11 each time inquiry is carried out as follows with the exchange of responding:

(1) client 4 inquires about the inquiry A of " AAAA " record of " www.ox Δ .com.6x4.org " for the dns server 5 that requires to inquire about.

(3) root name claim server 8 will with " org " and the corresponding response A ' of NS record be sent to and require the dns server 5 inquired about.

(5) the response A of the NS record of the name server of " org " 9 transmission corresponding " 6x4.org " is " to the dns server 5 that requires to inquire about.

(7) the DNS proxy server 6 of transducer is sent to the inquiry B of " AAAA " of " www.ox Δ .com " record and passes on target dns server 7.

(8) passing on target dns server 7 does not show in the figure name server inquiry " www.ox Δ .com " to other " AAAA " record.

(9) pass on target dns server 7 receive " Www.oxΔ .com" " AAAA " the non-existent response B of record.

(10) passing on target dns server 7 is sent to the non-existent response of " AAAA " of " www.ox Δ .com " record B the DNS proxy server 6 of this transducer.

(11) the DNS proxy server 6 of transducer will " Www.oxΔ .com" the inquiry C of " A " record be sent to and pass on target dns server 7.

(12) pass on target dns server 7 to other do not show in the figure name server inquiry " Www.oxΔ .com" " AAAA " record.

(13) pass on target dns server 7 receive " Www.oxΔ .com" " A " record response C.

(14) passing on target dns server 7 will the response C corresponding with the inquiry of " A " of " www.ox Δ .com " record be sent to the DNS proxy server 6 of transducer.

(15) the DNS proxy server 6 of transducer is sent to the dns server 5 that requires inquiry with the response A corresponding with the inquiry that " AAAA " of " www.ox Δ .com.6x4.org " writes down.

Simultaneously, at Fig. 4 to each embodiment shown in Figure 11, the DNS proxy server of transducer is at first carried out the inquiry of one " A " record for the target dns server, so that when the inquiry for " A " record had corresponding " A " record, " A " record can preferentially be passed back.Yet, when the DNS of transducer proxy server receives the inquiry of one " A " record, also may cause the DNS proxy server of transducer at first to carry out the inquiry that " AAAA " writes down, and if " AAAA " of this correspondence record exists, to this IPv6 address that is included in this " AAAA " record, and preferentially pass this IPv4 map addresses back this mapping address.

Even, can consider only to pass the address of being shone upon back, or only pass the address of being shone upon back, or pass the operation of the address that is subjected to shining upon and is shone upon back.As above-mentioned, be subjected to this DNS proxy server of the transducer of inquiry " A " record, may have following operation:

(a) " A " record that is only shone upon is passed back.

(b) " A " record that is only mapped to " AAAA " record is passed back.

(c) if correspondence is inquired about FQDN's " A " when record exists, pass this " A " record back.When corresponding " AAAA " record exists if corresponding " A " record does not exist, to " AAAA " intrarecord IPv6 address, and this IPv4 address passed the IPv4 map addresses back as " A " record.

(d), to " AAAA " intrarecord IPv6 address, and this IPv4 address passed the IPv4 map addresses back as " A " record if when corresponding " AAAA " record of being inquired about FQDN exists.If this correspondence " AAAA " record does not exist, but should exist by correspondence " A " record, then pass " A " address back.

(e) if corresponding " A " that is inquired about FQDN writes down when existing, pass this " A " record back.When corresponding if " AAAA " record exists, the IPv4 address that will map to " AAAA " intrarecord IPv6 address is passed back as " A " record.If this " A " that passes back all exists with " AAAA " record of this mapping, this two record is all passed back.

Similarly, be subjected to this DNS proxy server of the transducer of inquiry " AAAA " record, may have following operation:

(a) " AAAA " record that is only shone upon is passed back.

(b) " AAAA " record that is only mapped to " A " record is passed back.

(c) if corresponding " AAAA " that is inquired about FQDN writes down when existing, pass this " AAAA " record back.When should correspondence " A " record if this correspondence " AAAA " record does not exist existing, to " A " intrarecord IPv4 address, and this IPv6 address passed the IPv6 map addresses back as " AAAA " record.

(d), to " A " intrarecord IPv4 address, and this IPv6 address passed the IPv6 map addresses back as " AAAA " record if when corresponding " A " record of being inquired about FQDN exists.If this correspondence " A " record does not exist, but should exist by correspondence " AAAA " record, then pass " AAAA " address back.

(e) if corresponding " AAAA " that is inquired about FQDN writes down when existing, pass this " AAAA " record back.When corresponding if " A " record exists, the IPv6 address that will map to " A " intrarecord IPv4 address is passed back as " AAAA " record.If this " A " that passes back all exists with " AAAA " record of this mapping, this two record is all passed back.

In addition, the DNS proxy server of transducer can select to take any operation for this " A " record and the inquiry of being somebody's turn to do " AAAA " record.In addition, the operation that the user wishes, can import one the definition character string specify to this FQDN.

(1) if during the switched address of preferential expectation, for example can add " x.6x4.org ".

" www.ox Δ .com.x.6x4.org kenel=A "

" A " record that is subjected to mapping to the IPv4 address of an IPv6 address is preferentially passed back.

" www.ox Δ .com.x.6x4.org kenel "=AAAA "

" AAAA " record that is subjected to mapping to the IPv6 address of an IPv4 address is preferentially passed back.

When (2) not being converted the address, for example can add " n.6x4.org " as if preferential expectation.

" www.ox Δ .com.n.6x4.org kenel=A "

Shone upon " A " write down and preferentially passed back.

" www.ox Δ .com.n.6x4.org kenel=AAAA "

Shone upon " AAAA " write down and preferentially passed back.

(3) if when only expecting switched address, for example can add " xo.6x4.org ".

" www.ox Δ .com.xo.6x4.org kenel=A "

Only there is " A " record of an IPv4 address that is mapped to the IPv6 address to pass back.

" www.ox Δ .com.xo.6x4.org kenel=AAAA "

The IPv6 address that is subjected to mapping to the IPv4 address is only arranged " AAAA " record passes back.

(4) if only the expectation be not converted the address time, for example can add " no.6x4.org ".

" www.ox Δ .com.no.6x4.org kenel=A "

Only have and to be shone upon " A " record passed back.

" www.ox Δ .com.no.6x4.org kenel=AAAA "

Only have and to be shone upon " AAAA " record passed back.

(5) if when being converted address and this and not being converted the address and all expecting, for example can add " b.6x4.org ".

" www.ox Δ .com.b.6x4.org kenel=A "

Shone upon " A " write down and be subjected to mapping to an IPv6 address the IPv4 address " A " record all passed back.

" www.ox Δ .com.b.6x4.org kenel=AAAA "

Shone upon " AAAA " write down and be subjected to mapping to the IPv6 address of IPv4 address " AAAA " record all passed back.

Even, if the client can specify an address based on IPv6 of wanting in the FQDN, or based on the address of IPv4.So make the client to specify to use which kind of transmission control protocol among IPv6 or the IPv4, with to side communication.

(6) if preferential expectation during based on the record of an IPv6 address, for example can add " 6.6x4.org ".

" www.ox Δ .com.6.6x4.org kenel=A "

Be subjected to mapping to an IPv4 address of IPv6 address " A " record preferentially passed back.

" www.ox Δ .com.6.6x4.org kenel=AAAA "

" AAAA " record that is shone upon is preferentially passed back.

(7) if preferential expectation during based on the record of an IPv4 address, can for example add " 4.6x4.org ".

" www.ox Δ .com.4.6x4.org kenel=A "

" A " record that is shone upon is preferentially passed back.

" www.ox Δ .com.4.6x4.org kenel=AAAA "

" AAAA " record that is subjected to mapping to an IPv6 address of IPv4 address is preferentially passed back.

(8) if when only expecting record based on an IPv6 address, for example can add " 6o.6x4.org ".

" www.ox Δ .com.6o.6x4.org kenel=A "

Only there is " A " record of an IPv4 address that is subjected to mapping to the IPv6 address to be passed back.

" www.ox Δ .com.6o.6x4.org kenel=AAAA "

Only there is one " AAAA " record that is shone upon to be passed back.

(9) if when only expecting record based on an IPv4 address, for example can add " 4o.6x4.org ".

" www.ox Δ .com.4o.6x4.org kenel=A "

Only have and one not shone upon " A " record passed back.

" www.ox Δ .com.4o.6x4.org kenel=AAAA "

Only there is " AAAA " record of an IPv6 address that is subjected to mapping to the IPv4 address to be passed back.

Claims

1. IPv6/IPv4 transducer, can be between IPv6 and IPv4 agreement convert packets reciprocally; And utilize the exclusive net territory that can be used as an effective specific DNS net territory so that allow the DNS proxy server that can reach this transducer from client's DNS inquiry; The utilization of this transducer DNS proxy server is imported defined character string in complete qualified domain name and is specified an operation.

2. IPv6/IPv4 transducer as claimed in claim 1, therein this client specify in the FQDN based on the address of IPv6 or based in the address of IPv4 at least one, as the address of hope.

3. IPv6/IPv4 transducer as claimed in claim 1, this client specifies at least one in an address of changing or the address of not changing therein, as the address of expectation.