WO2021078281A1 - 报文转发及域名地址查询 - Google Patents

报文转发及域名地址查询 Download PDF

Info

Publication number
WO2021078281A1
WO2021078281A1 PCT/CN2020/123378 CN2020123378W WO2021078281A1 WO 2021078281 A1 WO2021078281 A1 WO 2021078281A1 CN 2020123378 W CN2020123378 W CN 2020123378W WO 2021078281 A1 WO2021078281 A1 WO 2021078281A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
network address
domain name
network
response message
Prior art date
Application number
PCT/CN2020/123378
Other languages
English (en)
French (fr)
Inventor
李明玉
夏添
Original Assignee
新华三信息安全技术有限公司
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 新华三信息安全技术有限公司 filed Critical 新华三信息安全技术有限公司
Priority to JP2022521052A priority Critical patent/JP7478820B2/ja
Priority to EP20879262.2A priority patent/EP4033729B1/en
Publication of WO2021078281A1 publication Critical patent/WO2021078281A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/659—Internet protocol version 6 [IPv6] addresses

Definitions

  • IPv4 Internet Protocol Version 4
  • IPv6 Internet Protocol Version 6
  • NAT64 Network Address Translation for IPv6-IPv4, network address translation from Internet Protocol Version 6 to Internet Protocol Version 4
  • DNS64 Domain Name System for IPv6-IPv4, a domain name system solution for Internet Protocol version 6 clients to query the network address of Internet Protocol version 4 servers.
  • Fig. 1 shows a message forwarding flow chart based on NAT64+DNS64 provided by the prior art.
  • a typical message forwarding process may include the following steps:
  • IPv6 client When the IPv6 client is ready to access the server whose domain name is example.com, it first initiates an AAAA query to the DNS64 server to request the address corresponding to the domain name example.com;
  • the DNS64 server If the DNS64 server does not have a record of the domain name locally, it will initiate an AAAA query to the DNS66 (Domain Name System for IPv6-IPv6, the domain name system for the Internet Protocol version 6 client to query the Internet Protocol version 6 server network address) server, Request the address corresponding to the domain name example.com;
  • DNS66 Domain Name System for IPv6-IPv6, the domain name system for the Internet Protocol version 6 client to query the Internet Protocol version 6 server network address
  • the DNS64 server After the DNS64 server receives the null value, it initiates a query A to the DNS44 (Domain Name System for IPv4-IPv4, the domain name system for Internet Protocol version 4 clients to query the network address of the Internet Protocol version 4 server) server, requesting a domain name The address corresponding to example.com;
  • the DNS44 server If the DNS44 server has the IPv4 address record of the domain name, it sends a DNS response message to the DNS64 server to inform that the address corresponding to the domain name example.com is 192.0.2.1;
  • the DNS64 server After the DNS64 server obtains the IPv4 address corresponding to the domain name, it uses the preset prefix (for example, 2001:db8:cdef::) to synthesize the IPv4 address into an IPv6 address (for example, 2001:db8:cdef:192.0.2.1), And return it to the IPv6 client through a DNS response message;
  • the preset prefix for example, 2001:db8:cdef:::
  • IPv6 client initiates IPv6 access through the NAT64 device and sends an IPv6 message to the NAT64 device.
  • the destination address of the IPv6 message is the synthesized IPv6 address 2001:db8:cdef:192.0.2.1, and the source address is the IPv6 client itself the address of;
  • the NAT64 device After the NAT64 device receives the IPv6 message sent by the IPv6 client, it converts the source/destination IPv6 address of the message to an IPv4 address through the pre-configured NAT64 conversion rules, and sends it to the domain name example.com and the IPv4 address 192.0 .2.1 IPv4 server, where the NAT64 conversion rule of the NAT64 device needs to correspond to the DNS64 prefix configuration, otherwise it cannot be converted;
  • the NAT64 device receives the IPv4 packet responded by the IPv4 server, and then uses the reverse conversion relationship in step 8) to convert the IPv4 packet into an IPv6 packet (usually matching the session on the NAT64 device for reverse conversion);
  • the NAT64 device sends the converted IPv6 message to the IPv6 client.
  • FIG. 1 shows a schematic flowchart of a message forwarding method provided in the prior art
  • Figure 2 shows a schematic diagram of an application scenario provided by an embodiment of the present application
  • FIG. 3 shows a flowchart of a method for forwarding a message according to an embodiment of the present application
  • Figure 4a shows a schematic diagram of an additional record of a second response message provided by an embodiment of the present application
  • FIG. 4b shows a schematic diagram of an additional record of a second response message provided by an embodiment of the present application
  • FIG. 5 shows a schematic diagram of header information of a second response message provided by an embodiment of the present application
  • FIG. 6 shows a flowchart of a method for processing a second response message provided by an embodiment of the present application
  • FIG. 7 shows a schematic diagram of a message forwarding apparatus provided by an embodiment of the present application.
  • FIG. 8 shows a flowchart of a method for querying a domain name address provided by an embodiment of the present application
  • FIG. 9 shows a flowchart of a method for querying a domain name address provided by an embodiment of the present application.
  • FIG. 10 shows a schematic structural diagram of a domain name address query device provided by an embodiment of the present application.
  • FIG. 11 shows a sequence diagram of a message forwarding method provided by an embodiment of the present application.
  • FIG. 12 shows a schematic structural diagram of a network address translation device provided by an embodiment of the present application.
  • FIG. 13 shows a schematic structural diagram of a domain name system provided by an embodiment of the present application.
  • Fig. 14 shows a schematic diagram of a computer-readable medium provided by an embodiment of the present application.
  • DNS Domain Name System
  • NAT Network Address Translation
  • first and second are used to distinguish different objects, rather than to describe a specific order.
  • the terms “including” and “having” and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes unlisted steps or units, or optionally also includes Other steps or units inherent in these processes, methods, products or equipment.
  • the translation strategy is manually configured on the network address translation device 10 (such as NAT64).
  • the IPv6 prefix referenced in the strategy and the prefix used to synthesize the IPv6 address on DNS64 must be consistent, otherwise the conversion cannot be performed. .
  • the workload of manually configuring the above conversion strategy on the NAT64 device is huge, and automatic operation and maintenance cannot be realized, and the efficiency is low and error-prone.
  • the conversion strategy is not synchronized in time or the synchronization is wrong, the network will be interrupted, and the timely and accurate forwarding of cross-protocol network messages cannot be ensured. Therefore, the prior art has the problems of low efficiency, error-proneness, and inability to ensure timely and accurate forwarding of cross-protocol network messages.
  • the embodiment of the application has opened up the communication channel between the network address translation device 10 and the domain name system 20.
  • the first network address of an Internet protocol also sends address translation information between the second network address and the first network address to the network address translation device 10.
  • This allows the network address translation device 10 to perform destination address translation on the service message whose destination address is the first network address sent by the client 50 according to the address translation information, and send the service message after the destination address conversion to the server 60.
  • the network address translation device 10 can be automatically synchronized with the domain name system according to the address translation information, and the network address translation device 10 can be promoted to realize automatic operation and maintenance, thereby avoiding manual configuration of address translation information for the network address translation device 10 and low efficiency.
  • the efficiency, stability, and reliability of operation and maintenance are improved, and network interruption is avoided, which helps ensure that the network address translation device 10 forwards messages across the protocol network in a timely and accurate manner.
  • the embodiments of the present application provide a method and device for forwarding a message, a method and device for querying a domain name address, a network address translation device, and a computer-readable medium, which are described below with reference to the accompanying drawings. Description.
  • FIG. 3 shows a flowchart of a message forwarding method provided by an embodiment of the present application.
  • the message forwarding method is applied to a network address translation device. As shown in FIG. 3, the method may include the following steps S101 to S105.
  • Step S101 Receive a first address query request for a target domain name sent by a client, where the client uses the first Internet protocol, and the target server corresponding to the target domain name uses the second Internet protocol.
  • the network address translation device 10 can be used as a proxy DNS, or the network address translation device 10 has at least a proxy DNS function.
  • the client 50 needs to query the address corresponding to the target domain name, it no longer sends an address query request to the DNS 20, but instead sends a first address query request to the network address translation device 10, and the destination address in the first address query request is no longer It is the address of the DNS 20, but the address of the aforementioned network address conversion device 10, so that the client 50 sends the aforementioned first address query request to the network address conversion device 10.
  • Step S102 If the network address corresponding to the target domain name is not found locally, a second address query request for the target domain name is sent to the domain name system.
  • the network address translation device 10 receives the first address query request, and queries the network address corresponding to the target domain name locally. If the network address corresponding to the target domain name is not found locally, a second address query request is sent to the DNS 20.
  • the source address of the second address query request is the address of the network address translation device 10
  • the destination address is the address of the DNS 20, so that the network address translation device 10 sends the second address query request to the DNS 20 and can receive it Response message returned by DNS20.
  • the conversion device 10 After receiving the second address query request, if the second network address queried only supports the second Internet protocol, it needs to be converted to the first network address supporting the first Internet protocol, and then the network address The conversion device 10 sends a second response message for the second address query request.
  • the second response message includes the first network address and the address conversion information between the first network address and the second network address, so that the network address conversion device 10 can send the destination address to the client 50 according to the address conversion information as The service message of the first network address undergoes destination address translation.
  • Step S103 Receive a second response message returned by the domain name system for the second address query request.
  • the second response message records the first network address and the address conversion information between the first network address and the second network address.
  • the second network address includes a network address supporting the second Internet protocol corresponding to the target domain name
  • the first network address includes a network address supporting the first Internet protocol obtained by the domain name system according to the second network address conversion.
  • Step S104 Send a first response message for the first address query request to the client, where the first response message includes the first network address.
  • the network address translation device 10 may send the first network address to the client 50 to realize the role of proxy DNS.
  • Step S105 Receive the service message with the destination address of the first network address sent by the client, convert the destination address of the service message to the second network address according to the address conversion information, and send the service after the destination address conversion to the target server Message.
  • the client terminal 50 can send a service message to the target server (for example, the server 60) corresponding to the target domain name according to the first network address.
  • the target server for example, the server 60
  • the network address translation device 10 After the network address translation device 10 receives the service message whose destination address is the first network address sent by the client 50, it can convert the destination address of the service message to the second network address according to the address translation information, and send it to the target
  • the server for example, the server 60 sends the service message after the destination address conversion.
  • the network address translation device after receiving the first address query request for the target domain name sent by the client, the network address translation device first queries the network address corresponding to the target domain name locally. If it is not found, Then send a second address query request for the target domain name to the domain name system, and receive a second response message that includes the first network address and the address translation information returned by the domain name system. Then send the first response message for the first address query request to the client. After that, after receiving the service message with the destination address of the first network address sent by the client, the service can be converted according to the above address translation information. The destination address of the message is converted to the second network address, and the service message after the destination address conversion is sent to the target server.
  • the above method changes the existing domain name address query mechanism and the response mechanism of the domain name system.
  • the client no longer directly sends an address query request to the domain name system, but instead sends an address query request to the network address translation device.
  • the network address translation device can use the combination of local query and query to the domain name system to query the domain name address, and return the first network address found to the client, thereby realizing the function of proxying the domain name system; and because in the query process In the domain name system, the address translation information is sent to the network address translation device. Therefore, the network address translation device can use the address translation information to convert the destination address of the service message sent by the client, thereby realizing the conversion of the service message.
  • Cross-protocol network forwarding can be used to convert the destination address of the service message sent by the client, thereby realizing the conversion of the service message.
  • this method can not only enable the smooth implementation of domain name address query, but also enable the network address translation equipment to automatically and real-time obtain the above address translation information without manual intervention, thereby realizing the automatic operation and maintenance of the network address translation equipment and avoiding Manually configure the address translation information for the network address translation equipment to produce low efficiency and error-prone problems, improve the efficiency, stability and reliability of operation and maintenance, avoid network interruption, and ensure the timely and accurate forwarding of cross-protocol network messages.
  • the first Internet protocol includes Internet Protocol Version 6 IPv6, and the second Internet protocol includes Internet Protocol Version 4 IPv4; or, the first Internet protocol includes Internet Protocol Version 4 IPv4, and the second Internet protocol includes Internet Protocol version 6 IPv6. That is, service packets can be forwarded from the IPv6 network to the IPv4 network, or from the IPv4 network to the IPv6 network.
  • the embodiment of this application does not limit it. To make it easier to understand and describe, in the part of the description of the embodiment of this application, the above Business messages are called cross-protocol network messages.
  • the network address translation device may refer to a packet forwarding device between two different Internet protocol networks (for example, an IPv6 network and an IPv4 network), and is used to forward packets across a protocol network.
  • the message may be forwarded from the IPv6 network to the IPv4 network, or the message may be forwarded from the IPv4 network to the IPv6 network, which is not limited in the embodiment of the present application.
  • the network address translation device may have different names, such as NAT64, NAT46, AFT (Address Family Translation, address cluster translation), etc., which are not limited in the embodiment of the present application.
  • NAT64 NAT64
  • NAT46 NAT46
  • AFT Address Family Translation, address cluster translation
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • the second response message is a DNS response message.
  • the above address translation information can be delivered to the network address translation device along with the second response message.
  • Additional Resource Records also known as additional resource records, collectively referred to herein as additional records
  • additional records also known as additional resource records, collectively referred to herein as additional records
  • the embodiment of this application does not need to modify the hardware in the network architecture.
  • only a simple software upgrade can realize the function upgrade to realize the method provided in the embodiment of the present application. Therefore, the embodiment of the present application also has the advantages of simple and easy modification, low modification cost, and the like.
  • the method may further include:
  • the network address conversion device reads the address conversion information between the first network address and the second network address from the additional record of the second response message.
  • the method also Can include:
  • the network address translation device searches for an additional record of a predetermined type from the text area of the second response message, and reads the address translation information between the first network address and the second network address from the additional record of the predetermined type.
  • the DNS may add the above-mentioned additional records to the response message according to a preset format.
  • Figure 4a shows a schematic diagram of an additional record of a second response message provided by some implementations of the embodiments of the present application.
  • the first Internet protocol is IPv6
  • the second Internet protocol is IPv4.
  • the address conversion information is the prefix information used to convert the first network address and the second network address
  • Fig. 4b is an example of additional records (Additional records) after filling in.
  • Name:example.com indicates that the domain name contained in the resource record is "example.com”.
  • Type: PREFIX(64) indicates that the type of the resource record is the prefix type, and the type value is 64.
  • Class: IN (0x001) represents the class of the recorded data (RDATA), and its value is 0x0001.
  • TTL: 24hours means that the additional record can be cached for 24 hours.
  • RDlength: 32 means that the length of RDATA is 32.
  • Rdata:2001::/96 indicates that the detailed content of the additional record is 2001::/96, where "2001::” is the prefix of the IPv6 address and "96" is the length of the IPv6 address.
  • the domain name system can add additional records to the second response message according to the preset format, and specify the type of the additional records, so that the network address translation device can automatically and correctly parse the foregoing format and type according to the foregoing format and type. Attach records to get address translation information.
  • the method may further include:
  • the step of searching for a predetermined type of additional record from the body area of the second response message is triggered.
  • the additional record identifier in the header information of the second response message may be modified to the first identifier.
  • the additional record identifier is used to identify the number of additional records carried in the second response message. For example, an additional record identifier of 0 means no additional record, an additional record identifier of 1 means there is 1 additional record, and an additional record identifier of 2 Indicates that there are 2 additional records.
  • the first identifier can be any positive integer, that is, if the network address translation device determines that there are additional records (unlimited number) in the second response message according to the additional record identifier, the network address translation device can be triggered from the second The step of searching for additional records of a predetermined type in the body area of the response message.
  • the "Additional RRs" field in the second response message is an additional record identifier, and the value of the "Additional RRs" field is used to indicate the number of additional records.
  • Additional RRs in Figure 5 are additional record identifiers, and the domain name system modifies its value to 1, indicating that there is an additional record in the second response message. In another example, if Additional RRs is 2, it means that there are 2 additional records in the second response message.
  • the network address translation device can first determine whether the second response message carries additional records according to the additional record identifier. If the second response message does not carry additional records, there is no need to further query the additional records to avoid useless work; If the second response message carries additional records, the network address device is then triggered to perform the step of searching for a predetermined type of additional records from the text area of the second response message, thereby improving the implementation efficiency as a whole.
  • the method may further include:
  • the network address translation device determines the second network address corresponding to the first network address according to the first network address and the address translation information recorded in the second response message, and generates the second network address according to the first network address, the address translation information, and the second network address
  • the domain name system caches entries and stores them locally.
  • domain name system cache entry is not limited to include the first network address, the address translation information, and the second network address, and may also include other fields according to actual needs, which are not limited in the embodiment of the present application.
  • DNS cache entry may be as shown in Table 3 below, where one of the IPv6 address and the IPv4 address is the first network address, the other is the second network address, and the address translation information may be It is the prefix information (for example, 2001::), or the correspondence information between the first network address and the second network address recorded in the DNS cache entry.
  • the aging time TTL may be the same as the aging time of the domain name record entry on the DNS by default, or it may be manually configured to be less than the aging time of the domain name record entry on the DNS, which is not limited in this embodiment of the application.
  • the network address translation device can generate a DNS cache entry and store it locally, so that after receiving an address query request for the target domain name, it can directly query the local DNS cache entry to obtain the target domain name corresponding The first network address is fed back to the client, thereby improving the efficiency of domain name address query.
  • step S101 the method further includes:
  • the network address translation device locally queries the network address corresponding to the target domain name.
  • the network address translation device locally querying the network address corresponding to the target domain name may include:
  • the network address translation device queries the network address corresponding to the target domain name in the locally stored domain name system cache entry.
  • the network address corresponding to the target domain name can be queried in the local DNS cache entry first, and if the network address corresponding to the target domain name is not found in the local DNS cache entry, the network address can be retrieved from the local DNS cache entry.
  • DNS server query which can effectively improve the efficiency of domain name address query.
  • the method may further include:
  • the network address translation device finds the first network address corresponding to the target domain name locally, it triggers the step of sending a first response message for the first address query request to the client.
  • step S104 can be triggered without performing steps S102 and S103, so that the domain name address query efficiency can be effectively improved.
  • the method may further include:
  • the network address translation device queries the address translation information between the first network address and the second network address in the locally stored domain name system cache entry, thereby ensuring the smooth implementation of step S105 and improving the forwarding efficiency of the cross-protocol network message.
  • the address translation information may include prefix information used to convert the first network address and the second network address.
  • the network address translation device translates the destination address of the service message into the second network address, including:
  • the network address conversion device converts the destination address of the service message from the first network address to the second network address by adding or deleting prefix information to the first network address.
  • the network address conversion device can convert the first network address to the second network address by simply adding or deleting the prefix information to the first network address, which has the advantages of simplicity and high efficiency.
  • the method may further include:
  • an address translation rule is generated and stored locally, and the matching items of the address translation rule include the foregoing prefix information
  • the network address translation device translates the destination address of the service message into the second network address, which may include:
  • the network address translation device locally matches the corresponding address translation rule according to the prefix information of the first network address
  • the destination address of the service packet is converted from the first network address to the second network address according to the matched address conversion rule.
  • the address translation rule may include a type item and a matching item.
  • the type item may be "prefix" (prefix). This type means that the network address translation device can convert the network address by deleting the prefix information, and the matching item Specific prefix information may be included. In this way, based on the address conversion rule, the network address conversion device can implement network address conversion by deleting the prefix information.
  • the address translation rule generated by the network address translation device according to the prefix information is "nat64prefix-nat64 2001::96".
  • the prefix is deleted through the address conversion rule, and the IPv6 destination address (for example, 2001::1.2.3.4) is converted to an IPv4 address (for example, 1.2.3.4).
  • the network address conversion device can accurately and conveniently convert the first network address to the second network address.
  • the prefix information used by DNS for network address translation may be specific prefix information, such as "2001::”, “64:FF9B::”, and so on.
  • DNS64 generally uses the above-mentioned designated dedicated prefix to synthesize the IPv4 address to the IPv6 address by default. Therefore, the prefixes of multiple different first network addresses synthesized by the DNS have a greater probability of being the same.
  • the same address translation rule can be used to perform address translation on multiple different first network addresses with the same prefix, so that the network address translation device stores With fewer address conversion rules, a large number of network addresses can be converted across protocols. On the one hand, it can save the local storage space of the network address translation device; on the other hand, because there are fewer address translation rules, it helps the network address translation device to match the address translation rules faster based on the prefix information, thereby improving the efficiency of network address translation .
  • the network address translation device generates an address translation rule based on the prefix information and stores it locally, which may include:
  • the network address translation device locally matches the corresponding address translation rule according to the prefix information recorded in the second response message;
  • the network address translation device If the address translation rule is not matched, the network address translation device generates an address translation rule according to the prefix information recorded in the second response message and stores it locally;
  • step S104 is triggered.
  • the network address translation device since multiple first network addresses may have the same prefix, through this embodiment, the network address translation device only needs to generate the address translation rule when the prefix information first appears, and it does not need to generate the address translation rule again when the prefix information appears again. Therefore, the redundant work and system load caused by the generation of address translation rules to the network address translation device can be effectively reduced, and the work efficiency of the network address translation device can be improved.
  • FIG. 6 shows a flowchart of a method for processing a second response message provided by an embodiment of the present application.
  • the foregoing embodiment can be understood with reference to FIG. 6, and FIG. 6 may also refer to the foregoing implementation.
  • the description of the example is to be understood and will not be repeated here.
  • the AAAA response message can be understood as a DNS response message.
  • the network address translation device receives the AAAA response message (ie, the second response message), it can first determine whether the second response message has additional records. , And then determine whether the type (type) of the additional record is a predetermined type (such as "prefix"), if not, it will be processed according to other types of additional records, if it is, the additional record will be parsed to obtain the prefix information (ie address translation Information), the second network address (that is, the IPv4 address in the figure) and other related information, and then generate the address translation rule (that is, the NAT64 translation configuration in the figure) based on the above information, and then add the IPv6 address (that is, the first network address) Return to the client after the first response message.
  • prefix information ie address translation Information
  • the second network address that is, the IPv4 address in the figure
  • the address translation rule that is, the NAT64 translation configuration in the figure
  • the first internet protocol is IPV6
  • the first network address is IPV6 address
  • the second internet protocol is IPV4 address
  • the aforementioned domain name system includes a DNS64 server
  • the network address translation device may be a NAT64 device.
  • the DNS AAAA response message ie, the second response message
  • the NAT64 device can determine whether there is an additional record in the DNS AAAA response message. If there is no additional record, , It is processed as a normal DNS response message; if there is an additional record, it is judged whether the type (type) of the additional record is a predetermined type (for example, "prefix").
  • the network address translation device will process other types of additional records; if the type of the additional record is a predetermined type, it will parse the prefix and length in the additional record, cache the query domain name and synthesize IPv6 Correspondence between address, prefix and length, and real IPv4 address. Among them, by parsing the additional record, relevant information such as prefix information (ie address translation information), IPV6 address (ie first network address) and so on can be obtained. For the information obtained by parsing the additional record, please refer to the relevant description in Table 2 above, which will not be repeated here.
  • the network address conversion device converts the IPv6 address (that is, the first network address) into an IPV4 address (that is, the second network address) according to the prefix information, and caches the prefix information, the correspondence relationship between the IPv6 address and the IPv4 address.
  • the NAT64 device automatically generates the corresponding NAT64 translation configuration for converting the IPv6 address in the packet with the IPv6 address in the DNS AAAA response packet as the destination address into the corresponding IPv4 address. That is, the NAT64 device generates a NAT64 translation configuration (namely, address translation rule) according to the cached correspondence between the above-mentioned IPv6 address and IPv4 address.
  • the NAT64 translation configuration is used to subsequently receive a business message, if the purpose of the business message is The address is the IPv6 address in the DNS AAAA response message, and the IPv6 address is converted to the corresponding IPv4 address.
  • the NAT64 device fills the synthesized IPv6 address into the DNS AAAA response message, and returns it to the IPv6 client. That is, after the NAT64 device adds the IPv6 address (that is, the first network address) to the DNS AAAA response message (first response message), it returns the DNS AAAA response message to the IPv6 client.
  • the foregoing implementation manners can not only ensure the smooth implementation of the domain name address query, but also enable the network address translation device to automatically and real-time obtain the address translation information without manual participation, thereby realizing the automatic operation of the network address translation device.
  • Maintenance to avoid the low efficiency and error-prone problems caused by manually configuring the address translation information for the network address translation equipment, improve the efficiency, stability and reliability of operation and maintenance, avoid network interruption, and ensure the timely and accurate cross-protocol network messages To forward.
  • the address translation information includes corresponding information between the first network address and the second network address.
  • the aforementioned corresponding information may record the first network address and the second network address having a corresponding relationship.
  • the network address translation device translates the destination address of the service message into the second network address, which may include:
  • the network address translation device replaces the destination address of the service message from the first network address with the second network address according to the corresponding information.
  • the network address conversion device can convert the first network address to the second network address through a simple replacement operation, which has the advantages of simplicity and efficiency, and high efficiency.
  • the network address translation device may query the address translation information corresponding to the destination address of the service message from the domain name system cache entry, and then according to the found address The conversion information performs the conversion of the destination address.
  • Step S105 can be specifically implemented as follows:
  • the network address translation device receives the service message whose destination address is the first network address sent by the client, queries the address translation information corresponding to the first network address in the locally stored domain name system cache entry, and according to the queried address translation information, The destination address of the service message is converted into the second network address, and the service message after the destination address conversion is sent to the target server.
  • the domain name system cache entry may include a first network address, address translation information, and a second network address, and the address translation information may be prefix information (for example, 2001::), It may also be the corresponding information between the first network address and the second network address recorded in the domain name system cache entry.
  • the network address translation device can find the corresponding information between the first network address and the second network address according to the above-mentioned domain name system cache entry, and according to the corresponding information, transfer the destination address of the service message from the first network The address is replaced with the second network address.
  • the network address translation device can find the prefix information corresponding to the first network address according to the above-mentioned domain name system cache entry, and according to the prefix information, the service message can be changed by adding or deleting the prefix information to the first network address. The destination address is converted from the first network address to the second network address.
  • the network address conversion device finds the prefix information, it can convert the first network address into an IPv4 address (that is, the second network address) by deleting the prefix information in the first network address. address).
  • the first network address is an IPv4 address
  • the network address translation device finds the prefix information, it can convert the first network address to an IPv6 address (ie, the second network address) by adding the prefix information to the first network address. website address).
  • the network address translation device uses the domain name system to cache entries, which can realize the conversion from an IPv6 address to an IPv4 address, and can also realize a conversion from an IPv4 address to an IPv6 address, and has the advantages of high conversion accuracy and high efficiency.
  • the conversion between the IPv6 address and the IPv4 address can be realized by combining the domain name system cache entry and the address conversion rule.
  • the function of the address translation rule is to pass the address when the network address translation device receives an IPv6 packet with the prefix "2001::”
  • the conversion rule deletes the prefix and converts the IPv6 destination address (for example, 2001::1.2.3.4) to an IPv4 address (for example, 1.2.3.4).
  • the network address translation device receives an IPv4 packet with a destination address of 1.2.3.4, it does not match the address translation rule, and at this time it queries the IP address 1.2 in the domain name system cache entry (as shown in Table 3). 3.4. After querying and finding the corresponding entry, the prefix "2001::” is added to the destination address 1.2.3.4 of the IPv4 packet to obtain the corresponding IPv6 destination address 2001::1.2.3.4.
  • an embodiment of the present application also provides a device for forwarding a message.
  • the message forwarding device provided in the embodiment of the present application can implement the above message forwarding method, and the message forwarding device can be implemented by software, hardware, or a combination of software and hardware.
  • the message forwarding apparatus may include integrated or separate functional modules or units to perform corresponding steps in the foregoing methods.
  • FIG. 7, shows a schematic diagram of a message forwarding apparatus provided by an embodiment of the present application. Since the device embodiment is basically similar to the method embodiment, the description is relatively simple, and the relevant part can refer to the part of the description of the method embodiment.
  • the device embodiments described below are merely illustrative.
  • an embodiment of the present application provides a message forwarding device, which is applied to a network address translation device, and the device may include:
  • the first query request receiving module 101 is configured to receive a first address query request for a target domain name sent by a client, where the client uses the first Internet protocol, and the target server corresponding to the target domain name uses the second Internet protocol;
  • the second query request sending module 102 is configured to send a second address query request for the target domain name to the domain name system if the network address corresponding to the target domain name is not found locally;
  • the second response message receiving module 103 is configured to receive a second response message returned by the domain name system in response to the second address query request, wherein the second response message records the first network address, the first network address and the second network Address translation information between addresses, the second network address includes a network address supporting the second Internet protocol corresponding to the target domain name, and the first network address includes a network address supporting the first Internet protocol obtained by the domain name system according to the second network address conversion;
  • the first response message sending module 104 is configured to send a first response message for the first address query request to the client, where the first response message includes the first network address;
  • the service message forwarding module 105 is configured to receive the service message whose destination address is the first network address sent by the client, convert the destination address of the service message to the second network address according to the address conversion information, and send it to the target server Service packet after destination address translation.
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • the device may further include:
  • the additional record query module is used to search for additional records of a predetermined type from the text area of the second response message
  • the additional record reading module is used to read the address conversion information between the first network address and the second network address from a predetermined type of additional record.
  • the device may further include:
  • the information reading trigger module is configured to trigger the operation of the additional record reading module if the additional record identifier in the header information of the second response message is the first identifier.
  • the device may further include:
  • the second network address determining module is configured to determine the second network address corresponding to the first network address according to the first network address and the address conversion information recorded in the second response message;
  • the cache entry generation module is used to generate and store the domain name system cache entry according to the first network address, the address conversion information and the second network address.
  • the device may further include:
  • the local query success processing module is configured to trigger the operation of the first response message sending module 104 if the first network address corresponding to the target domain name is queried locally.
  • the address conversion information includes prefix information used to convert the first network address and the second network address
  • the address conversion information includes correspondence information between the first network address and the second network address.
  • the service message forwarding module 105 may include:
  • the corresponding information conversion unit is configured to replace the destination address of the service message from the first network address to the second network address according to the above corresponding information.
  • the address conversion information includes prefix information used to convert the first network address and the second network address
  • the device may also include:
  • the address conversion rule generation module is used to generate an address conversion rule based on the prefix information and store it locally, and the matching items of the address conversion rule include prefix information;
  • the service message forwarding module 105 may include:
  • the address translation rule matching unit is configured to locally match the corresponding address translation rule according to the prefix information of the first network address
  • the rule conversion unit is configured to, if the matching is successful, convert the destination address of the service packet from the first network address to the second network address according to the matched address conversion rule.
  • the first Internet protocol may include Internet Protocol version 6 IPv6, and the second Internet protocol may include Internet Protocol version 4 IPv4; or,
  • the first internet protocol may include the fourth version of the internet protocol IPv4, and the second internet protocol may include the sixth version of the internet protocol IPv6.
  • the message forwarding device provided in the embodiment of the present application is based on the same inventive concept as the message forwarding method provided in the foregoing embodiment of the present application, and has the same beneficial effects.
  • a message forwarding method is provided.
  • this application also provides a domain name address query method.
  • the domain name address query method is implemented in cooperation with the foregoing message forwarding method, and belongs to The same inventive concept. Therefore, the following embodiments of the domain name address query method can be understood with reference to the foregoing embodiments of the message forwarding method, and part of the content will not be repeated.
  • the foregoing embodiments of the message forwarding method can also be understood with reference to the following embodiments of the domain name address query method.
  • FIG. 8 shows a flowchart of a domain name address query method provided by an embodiment of the present application.
  • the domain name address query method is applied to a domain name system.
  • the method can be understood with reference to the sequence diagram shown in FIG. 11.
  • the method can include the following steps:
  • Step S201 Receive a second address query request for the target domain name sent by the network address translation device, where the source address of the second address query request supports the first Internet protocol.
  • Step S202 In response to the second address query request, query the second network address corresponding to the target domain name, where the second network address supports the second Internet protocol.
  • Step S203 Convert the second network address into a first network address supporting the first Internet protocol.
  • Step S204 Send a second response message for the second address query request to the network address translation device, where the second response message includes the first network address and address translation information between the first network address and the second network address , So that the network address translation device sends the first network address to the client, and performs destination address translation on the service message sent by the client with the destination address of the first network address according to the address translation information.
  • the network address translation device After the network address translation device receives the business message sent by the client, if the destination address of the business message is the first network address, the network address translation device can determine the destination address of the business message according to the address translation information Convert to the second network address.
  • the domain name address query method provided in the embodiment of this application is based on the same inventive concept as the message forwarding method provided in the previous embodiment of this application, and has at least the following corresponding beneficial effects: After the domain name system receives a cross-protocol address query request , First query the second network address that supports the second Internet protocol corresponding to the target domain name, and then convert the second network address to the first network address that supports the first Internet protocol.
  • the domain name system sends the address translation information between the first network address and the second network address to the network address translation device, so that the network address translation device can automatically synchronize with the domain name system according to the address translation information, and prompt the network address translation device to achieve Automatic operation and maintenance, thereby avoiding low efficiency and error-prone problems caused by manually configuring address translation information for network address translation equipment, improving operation and maintenance efficiency, stability and reliability, avoiding network interruptions, and helping to ensure network address translation
  • the device forwards messages across the protocol network in a timely and accurate manner.
  • the domain name system can ensure that the network address translation device returns the found first network address to the client to realize the function of proxy DNS, thereby ensuring the smooth implementation of the domain name address query.
  • the domain name system sends the first network address and address translation information to the network address translation device, which can effectively simplify the data transfer process between the domain name system, the network address translation device and the client, improve the efficiency of data transfer, and save the network. Transmission resources.
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • the address conversion information includes prefix information used to convert the first network address and the second network address.
  • FIG. 9 shows a flowchart of a method for querying a domain name address provided by an embodiment of the present application.
  • the description of the foregoing embodiment can be understood with reference to FIG. 9, and FIG. 9 may also refer to that of the foregoing embodiment.
  • the description is for understanding, so I won’t repeat it here.
  • the AAAA response message can be understood as a DNS response message.
  • DNS can first query whether there is an AAAA record corresponding to the target domain name (IPv6 domain name) Address), if there is, it will directly return the AAAA record, if not, it will further query whether there is an A record (IPv4 domain name address), if not, it will return a null value, if it has, it will use the preset IPv6 prefix to synthesize the IPv6 address
  • return an AAAA response message ie, the second response message
  • add an additional record to the second response message and record the above-mentioned IPv6 prefix and length information in the additional record.
  • the process shown in FIG. 9 is executed by a DNS64 server, and accordingly, the network address translation device may be a NAT64 device.
  • the first internet protocol is IPV6, the first network address is an IPV6 address, the second internet protocol is an IPV4, and the second network address is an IPV4 address.
  • the DNS64 server after the DNS64 server receives the AAAA query message (ie, the second address query request), it can first query whether there is an AAAA record (IPv6 domain name address) corresponding to the target domain name, if there is a target domain name The corresponding AAAA record will directly return the AAAA record to the NAT64 device; if there is no AAAA record corresponding to the target domain name, the DNS64 server will further query whether there is an A record (IPv4 domain name address).
  • IPv6 domain name address IPv6 domain name address
  • the IPv6 address is synthesized using the preset IPv6 prefix, and an AAAA response message (ie, the second response message) is returned to the NAT64 device, the second response message
  • AAAA response message ie, the second response message
  • the additional record is included in the additional record, and the above-mentioned IPv6 prefix is recorded in the additional record.
  • the additional record please refer to the relevant description in Table 2 above, which will not be repeated here.
  • the address translation information includes correspondence information between the first network address and the second network address.
  • additional records can be added according to a preset format, and the type of the additional records can be specified, thereby ensuring that the network address translation device can automatically and correctly parse the additional records according to the foregoing format and type to obtain address translation information.
  • converting the second network address to the first network address supporting the first Internet protocol includes:
  • a network address supporting the first Internet protocol is selected from the preset address pool as the first network address to be converted with the second network address.
  • the domain name system will select a network address from the preset address pool as the first network address.
  • an IPv6 address pool can be configured on the DNS in advance. After DNS receives the second address query request, if it finds that the second network address corresponding to the target domain name is an IPv4 address, it can select an IPv6 address from the IPv6 address pool as the first network to be converted with the second network address The address is assigned to the target domain name. That is, the IPv6 address is assigned to the target domain name.
  • the domain name system can use the address pool to conveniently convert the second network address to the first network address, which has the advantages of convenient implementation and high efficiency.
  • a method for querying a domain name address is provided.
  • an embodiment of the present application also provides a device for querying a domain name address.
  • the domain name address query device provided in the embodiment of the present application can implement the above domain name address query method, and the domain name address query device can be implemented by software, hardware or a combination of software and hardware.
  • the domain name address query device may include integrated or separate functional modules or units to execute the corresponding steps in the foregoing methods.
  • FIG. 10 shows a schematic diagram of a domain name address query device provided by an embodiment of the present application. Since the device embodiment is basically similar to the method embodiment, the description is relatively simple, and the relevant part can refer to the part of the description of the method embodiment.
  • the device embodiments described below are merely illustrative.
  • the domain name address query device of the embodiment of the present application is applied to a domain name system. As shown in FIG. 10, the device may include:
  • the second address query request receiving module 201 is configured to receive a second address query request for the target domain name sent by the network address translation device, wherein the source address of the second address query request supports the first Internet protocol;
  • the second address query request processing module 202 is configured to query the second network address corresponding to the target domain name in response to the second address query request, where the second network address supports the second Internet protocol;
  • the network address conversion module 203 is configured to convert the second network address into a first network address supporting the first Internet protocol
  • the second response message sending module 204 is configured to send a second response message for the second address query request to the network address translation device, where the second response message includes the first network address and the first network address and the second network address. Address translation information between network addresses, so that the network address translation device sends the first network address to the client, and performs destination address translation on the service packet sent by the client with the destination address of the first network address according to the address translation information.
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • the address conversion information includes prefix information used to convert the first network address and the second network address.
  • the address translation information includes correspondence information between the first network address and the second network address.
  • the network address translation module 203 includes:
  • the network address selection unit is configured to select a network address supporting the first Internet protocol from a preset address pool as the first network address to be converted with the second network address.
  • the domain name address query device provided in the embodiment of the present application is based on the same inventive concept as the domain name address query method provided in the foregoing embodiment of the present application, and has the same beneficial effects.
  • this specific embodiment may at least include the following steps S301-S310.
  • Step S301 When the client supporting the first Internet protocol needs to query the address corresponding to the target domain name, it sends a first address query request for the target domain name to the network address translation device.
  • Step S302 After receiving the first address query request, the network address translation device queries the network address corresponding to the target domain name locally, and if not found, sends a second address query request for the target domain name to the domain name system.
  • Step S303 After the domain name system receives the second address query request, if the queried second network address only supports the second internet protocol, it will convert the found second network address to the first network supporting the first internet protocol address.
  • Step S304 The domain name system sends a second response message for the second address query request to the network address translation device, the second response message records the first network address and the address translation between the first network address and the second network address information.
  • Step S305 After receiving the second response message, the network address translation device sends a first response message for the first address query request to the client, where the first response message includes the first network address.
  • Step S306 The network address translation device also stores at least the address translation information between the first network address and the second network address locally.
  • Step S307 After receiving the first network address, the client sends a service message to the target server corresponding to the target domain name according to the first network address, and the destination address of the service message is the first network address.
  • Step S308 After receiving the service message, the network address conversion device converts the destination address of the service message from the first network address to the second network address according to the above address conversion information, and sends the service message after the destination address conversion to the target server. At the same time, a session table entry between the client and the target server is generated.
  • Step S309 After receiving the service message, the target server may return a response message for the service message, where the source address of the response message is the second network address.
  • Step S310 After receiving the response message, the network address translation device converts the source address of the response message from the second network address to the first network address according to the session table entry, and sends the converted response message to the client Text.
  • an embodiment of the present application also provides a network address translation device, as shown in FIG. 12, including a processor 1201, a machine-readable storage medium 1202, and a transceiver 1204.
  • the machine-readable storage medium 1202 stores machine-executable instructions that can be executed by the processor 1201; the machine-executable instructions cause the processor 1201 to perform the following steps:
  • the second network address includes a network address supporting the second Internet protocol corresponding to the target domain name
  • the first network address includes a network address supporting the first Internet protocol obtained by the domain name system according to the second network address conversion;
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • machine executable instructions also cause the processor 1201 to perform the following steps:
  • machine executable instructions also cause the processor 1201 to perform the following steps:
  • the step of searching for a predetermined type of additional record from the body area of the second response message is triggered.
  • machine executable instructions also cause the processor 1201 to perform the following steps:
  • a domain name system cache entry is generated and stored locally.
  • machine executable instructions also cause the processor 1201 to perform the following steps:
  • the step of sending a first response message for the first address query request to the client is triggered.
  • the address conversion information includes prefix information used to convert the first network address and the second network address;
  • the address conversion information includes correspondence information between the first network address and the second network address.
  • machine executable instructions also cause the processor 1201 to perform the following steps:
  • the destination address of the service message is converted from the first network address to the second network address; or,
  • the destination address of the service message is replaced from the first network address to the second network address.
  • the address conversion information includes prefix information used to convert the first network address and the second network address;
  • the machine executable instructions also cause the processor 1201 to perform the following steps:
  • the machine executable instructions also cause the processor 1201 to perform the following steps:
  • the destination address of the service packet is converted from the first network address to the second network address according to the matched address conversion rule.
  • the network address translation device may further include a communication bus 1203.
  • the processor 1201, the machine-readable storage medium 1202, and the transceiver 1204 communicate with each other through a communication bus 1203.
  • the communication bus 1203 can be a Peripheral Component Interconnect (PCI) bus or an extended industrial standard structure. (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the communication bus 1203 can be divided into an address bus, a data bus, a control bus, and the like.
  • the transceiver 1204 may be a wireless communication module, and under the control of the processor 1201, the transceiver 1204 performs data interaction with other devices (AC and terminal).
  • the machine-readable storage medium 1202 may include random access memory (Random Access Memory, RAM), and may also include non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk storage. In addition, the machine-readable storage medium 1202 may also be at least one storage device located far away from the aforementioned processor.
  • RAM Random Access Memory
  • NVM non-Volatile Memory
  • the processor 1201 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (Digital Signal Processing, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU central processing unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the network address translation device provided in the embodiment of the present application and the message forwarding method provided in the embodiment of the present application are based on the same technical concept, and have the same beneficial effects as the method adopted, operated, or implemented.
  • an embodiment of the present application also provides a domain name system, as shown in FIG. 13, including a processor 1301, a machine-readable storage medium 1302, and a transceiver 1304.
  • the machine-readable storage medium 1302 stores machine-executable instructions that can be executed by the processor 1301; the machine-executable instructions cause the processor 1301 to perform the following steps:
  • the information is converted, so that the network address conversion device sends the first network address to the client, and performs destination address conversion on the service packet whose destination address is the first network address sent by the client according to the address conversion information.
  • the second response message includes an additional record, and the additional record is used to record the address translation information between the first network address and the second network address.
  • the address translation information includes prefix information used to translate the first network address and the second network address; or,
  • the address conversion information includes correspondence information between the first network address and the second network address.
  • the address translation information includes correspondence information between the first network address and the second network address
  • the machine executable instructions also cause the processor 1301 to perform the following steps:
  • a network address supporting the first Internet protocol is selected from the preset address pool as the first network address to be converted with the second network address.
  • the network address translation device may further include a communication bus 1303.
  • the processor 1301, the machine-readable storage medium 1302, and the transceiver 1304 communicate with each other through a communication bus 1303.
  • the communication bus 1303 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the communication bus 1303 can be divided into an address bus, a data bus, a control bus, and the like.
  • the transceiver 1304 may be a wireless communication module. Under the control of the processor 1301, the transceiver 1304 performs data interaction with other devices (AC and terminal).
  • the machine-readable storage medium 1302 may include random access memory (Random Access Memory, RAM), and may also include non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk storage.
  • RAM Random Access Memory
  • NVM non-Volatile Memory
  • the machine-readable storage medium 1302 may also be at least one storage device located far away from the aforementioned processor.
  • the processor 1301 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (Digital Signal Processing, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU central processing unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • the domain name system provided in the embodiment of the application and the domain name address query method provided in the embodiment of the application are based on the same technical idea, and have the same beneficial effects as the method adopted, operated, or implemented.
  • the embodiment of the present application also provides a computer readable medium corresponding to the message forwarding method and domain name address query method provided in the foregoing embodiment.
  • FIG. 14 shows the computer readable storage medium as the optical disc 40.
  • a computer program ie, a program product
  • a processor such as the above-mentioned processor
  • examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random Access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media will not be repeated here.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random Access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other optical and magnetic storage media will not be repeated here.
  • the computer-readable storage medium provided by the above-mentioned embodiments of this application and the message forwarding method and domain name address query method provided by the embodiments of this application are based on the same inventive concept, and have methods adopted, run, or implemented by the stored application program. The same beneficial effect.
  • a computer program product containing instructions is also provided, which when running on a computer, causes the computer to execute any of the message forwarding methods or domain name address query methods in the foregoing embodiments.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more functions for realizing the specified logic function.
  • Executable instructions may also occur in a different order from the order marked in the drawings. For example, two consecutive blocks can actually be executed in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or actions Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the disclosed device and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some physical ports, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请提供一种报文转发方法及装置、一种域名地址查询方法及装置、一种网络地址转换设备以及一种计算机可读介质。其中，报文转发方法包括：接收客户端发送的针对目标域名的第一地址查询请求，若在本地未查到对应的网络地址，则向域名系统发送第二地址查询请求，接收域名系统返回的包括第一网络地址和地址转换信息的第二应答报文，向客户端发送第一应答报文，在接收到客户端发送的目的地址为第一网络地址的业务报文后，根据地址转换信息，将业务报文的目的地址转换为述第二网络地址，并向目标服务器发送目的地址转换后的业务报文。本方法可以实现网络地址转换设备的自动运维，确保跨协议网络报文及时、准确地转发。

Description

报文转发及域名地址查询
本申请要求于2019年10月25日提交中国专利局、申请号为201911024527.7发明名称为“报文转发、域名地址查询方法、装置、设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
背景技术
随着互联网的发展，IPv4(互联网协议第四版)地址已经逐步耗尽，IPv6(互联网协议第六版)网络终将取代现有的IPv4成为互联网的骨干网络。但是出于成本、技术限制等诸多原因，IPv4设备仍将在相当长的时间里存在，因此，IPv6的部署是一个平滑演进的过程，IPv6与IPv4将长期共存。
为解决IPv6客户端访问IPv4网络的问题，现有技术提供了NAT64(Network Address Translation for IPv6-IPv4，由互联网协议第六版向互联网协议第四版的网络地址转换)+DNS64(Domain Name System for IPv6-IPv4，供互联网协议第六版客户端查询互联网协议第四版服务器网络地址的域名系统)解决方案。其中，请参考图1，其示出了现有技术提供的基于NAT64+DNS64的报文转发流程图，一次典型的报文转发流程可以包括以下步骤：
1)当IPv6客户端准备访问域名为example.com的服务器时，首先向DNS64服务器发起AAAA查询，请求域名example.com对应的地址；
2)若DNS64服务器本地没有该域名的记录，则向DNS66(Domain Name System for IPv6-IPv6，供互联网协议第六版客户端查询互联网协议第六版服务器网络地址的域名系统)服务器发起AAAA查询，请求域名example.com对应的地址；
3)若DNS66服务器也没有该域名的记录，则返回空值给DNS64服务器；
4)DNS64服务器收到空值后，再向DNS44(Domain Name System for IPv4-IPv4，供互联网协议第四版客户端查询互联网协议第四版服务器网络地址的域名系统)服务器发起A查询，请求域名example.com对应的地址；
5)DNS44服务器有该域名的IPv4地址记录，则向DNS64服务器发送DNS应答报文，告知域名example.com对应的地址是192.0.2.1；
6)DNS64服务器获取到该域名对应的IPv4地址后，使用预设的前缀(例如2001:db8:cdef::)将IPv4地址合成为IPv6地址(例如，2001:db8:cdef:192.0.2.1)，并通过DNS应答报文返回给IPv6客户端；
7)IPv6客户端通过NAT64设备发起IPv6访问，向NAT64设备发送IPv6报文，该IPv6报文的目的地址为合成后的IPv6地址2001:db8:cdef:192.0.2.1，源地址为IPv6客户端自己的地址；
8)NAT64设备接收到IPv6客户端发送的IPv6报文后，通过预先配置的NAT64转换规则将报文的源/目的IPv6地址转换为IPv4地址，并发送给域名为example.com、IPv4地址为192.0.2.1的IPv4服务器，其中，NAT64设备的NAT64转换规则需要与DNS64的前缀配置对应，否则无法转换；
9)NAT64设备收到IPv4服务器回应的IPv4报文，再使用步骤8)中的反向转换关系，将IPv4报文转换为IPv6报文(通常是匹配NAT64设备上的会话进行反向转换)；
10)NAT64设备将转换后的IPv6报文发送至IPv6客户端。
附图简要说明
为了更清楚地说明本申请实施例和现有技术的技术方案，下面对实施例和现有技术中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了现有技术提供的一种报文转发方法的流程示意图；
图2示出了本申请实施例提供的一种应用场景的示意图；
图3示出了本申请实施例提供的一种报文转发方法的流程图；
图4a示出了本申请实施例提供的一种第二应答报文的附加记录的示意图；
图4b示出了本申请实施例提供的一种第二应答报文的附加记录的示意图；
图5示出了本申请实施例提供的一种第二应答报文的头部信息的示意图；
图6示出了本申请实施例提供的一种第二应答报文处理方法的流程图；
图7示出了本申请实施例提供的一种报文转发装置的示意图；
图8示出了本申请实施例提供的一种域名地址查询方法的流程图；
图9示出了本申请实施例提供的一种域名地址查询方法的流程图；
图10示出了本申请实施例提供的一种域名地址查询装置的结构示意图；
图11示出了本申请实施例提供的一种报文转发方法的时序图；
图12示出了本申请实施例提供的一种网络地址转换设备的结构示意图；
图13示出了本申请实施例提供的一种域名系统的结构示意图；
图14示出了本申请实施例提供的一种计算机可读介质的示意图。
具体实施方式
为使本申请实施例的目的、技术方案、及优点更加清楚明白，以下参照附图并举实施例，对本申请实施例进一步详细说明。显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本申请实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请实施例保护的范围。
需要注意的是，除非另有说明，本申请实施例使用的技术术语或者科学术语应当为本申请所属领域技术人员所理解的通常意义。
本申请实施例涉及的部分术语的简要说明如下：
1)、DNS(Domain Name System，域名系统)：为一种用于查询域名对应的网络地址的系统，可以为硬件，也可以为软件。
2)、NAT(Network Address Translation，网络地址转换)设备：为具有NAT功能的网络设备，可以为位于IPv6与IPv4网络之间的网络设备，通过转换网络地址实现报文的跨协议网络转发。
另外，术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
为了便于理解，首先，结合图2所示的应用场景的示意图，对本申请的一种应用场景进行说明如下：
由于图1所示的现有技术，由人工在网络地址转换设备10(例如NAT64)上配置转换策略，策略中 引用的IPv6前缀和DNS64上用于合成IPv6地址的前缀必须保持一致，否则无法转换。
实际使用中，在NAT64设备上人工配置上述转换策略的工作量巨大，无法实现自动运维，效率较低且容易出错。而在上述转换策略同步不及时或同步错误的情况下，则会导致网络中断，无法确保跨协议网络报文及时、准确地转发。因此现有技术存在效率较低、容易出错、无法确保跨协议网络报文及时、准确地转发的问题。本申请实施例打通了网络地址转换设备10与域名系统20之间的通信通道，域名系统20每次进行跨协议域名地址查询后，不仅将支持第二互联网协议的第二网络地址转换为支持第一互联网协议的第一网络地址，还向网络地址转换设备10发送第二网络地址与第一网络地址之间的地址转换信息。使得网络地址转换设备10可以根据地址转换信息，对客户端50发送的目的地址为第一网络地址的业务报文进行目的地址转换，并向服务器60发送目的地址转换后的业务报文。从而可以使网络地址转换设备10根据地址转换信息自动实现与域名系统的同步，促使网络地址转换设备10实现自动运维，进而避免人工为网络地址转换设备10配置地址转换信息而产生的效率较低和容易出错的问题，提高运维效率、稳定性和可靠性，避免网络中断，有助于确保网络地址转换设备10及时、准确地跨协议网络转发报文。
以上仅为本申请实施例提供的一种应用场景的示例性说明，并不表示任何限定，本领域技术人员可以在上述示例性说明的基础上灵活可选实施，其均应在本申请的保护范围之内。
参考上述关于应用场景的说明，本申请实施例提供一种报文转发方法及装置、一种域名地址查询方法及装置、一种网络地址转换设备以及一种计算机可读介质，下面结合附图进行说明。
请参考图3，其示出了本申请实施例所提供的一种报文转发方法的流程图。该报文转发方法应用于网络地址转换设备，如图3所示，该方法可以包括以下步骤S101至S105。
步骤S101：接收客户端发送的针对目标域名的第一地址查询请求，其中，该客户端使用第一互联网协议，目标域名对应的目标服务器使用第二互联网协议。
本实施例可以参照图2和图11进行理解，网络地址转换设备10可以被用作代理DNS，或者网络地址转换设备10至少具有代理DNS的功能。客户端50在需要查询目标域名对应的地址时，不再向DNS20发送地址查询请求，而改为向网络地址转换设备10发送第一地址查询请求，该第一地址查询请求中的目的地址不再是DNS20的地址，而是上述网络地址转换设备10的地址，从而使得客户端50将上述第一地址查询请求发送给网络地址转换设备10。
步骤S102：若在本地未查询到与目标域名对应的网络地址，则向域名系统发送针对目标域名的第二地址查询请求。
网络地址转换设备10接收到第一地址查询请求，在本地查询与目标域名对应的网络地址。若在本地未查到与目标域名对应的网络地址，则向DNS 20发送第二地址查询请求。其中，该第二地址查询请求的源地址为该网络地址转换设备10的地址，目的地址为DNS20的地址，以使得网络地址转换设备10将上述第二地址查询请求发送给DNS20，并能够接收到DNS20返回的应答报文。
域名系统DNS 20在接收到第二地址查询请求后，若查询到的第二网络地址仅支持第二互联网协议，则需要将其转换为支持第一互联网协议的第一网络地址，然后向网络地址转换设备10发送针对第二地址查询请求的第二应答报文。其中，第二应答报文包括第一网络地址和第一网络地址与第二网络地址之间的地址转换信息，从而使得网络地址转换设备10可以根据地址转换信息对客户端50发送的目的地址为第一网络地址的业务报文进行目的地址转换。
步骤S103：接收域名系统针对第二地址查询请求返回的第二应答报文。其中，第二应答报文记录 有第一网络地址和第一网络地址与第二网络地址之间的地址转换信息。
第二网络地址包括目标域名对应的支持第二互联网协议的网络地址，第一网络地址包括域名系统根据第二网络地址转换得到的支持第一互联网协议的网络地址。
步骤S104：向客户端发送针对第一地址查询请求的第一应答报文，其中，第一应答报文包括第一网络地址。
网络地址转换设备10在接收到第一网络地址后，可以向客户端50发送第一网络地址，实现代理DNS作用。
步骤S105：接收客户端发送的目的地址为第一网络地址的业务报文，根据地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文。
客户端50在接收到上述第一网络地址后，即可根据该第一网络地址向目标域名对应的目标服务器(例如服务器60)发送业务报文。
网络地址转换设备10在接收到客户端50发送的目的地址为第一网络地址的业务报文后，即可根据地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器(例如服务器60)发送目的地址转换后的业务报文。
本申请实施例提供的报文转发方法，网络地址转换设备在接收到客户端发送的针对目标域名的第一地址查询请求后，首先在本地查询与目标域名对应的网络地址，若未查到，则向域名系统发送针对目标域名的第二地址查询请求，并接收域名系统返回的包括第一网络地址和地址转换信息的第二应答报文。然后向客户端发送针对第一地址查询请求的第一应答报文，此后，在接收到客户端发送的目的地址为第一网络地址的业务报文后，即可根据上述地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文。
上述方法改变了现有的域名地址查询机制和域名系统应答机制，客户端不再直接向域名系统发送地址查询请求，而是改为向网络地址转换设备发送地址查询请求。网络地址转换设备可利用本地查询和向域名系统查询相结合的方式实现域名地址的查询，并将查到的第一网络地址返回给客户端，从而实现代理域名系统的功能；且由于在查询过程中，域名系统将地址转换信息一并发送给网络地址转换设备，因此，网络地址转换设备即可利用上述地址转换信息对客户端发送的业务报文进行目的地址的转换，从而实现业务报文的跨协议网络转发。
综上，本方法既可以使得域名地址查询的顺利实施，同时可以使网络地址转换设备无需人工参与即可自动、实时地获取到上述地址转换信息，从而实现网络地址转换设备的自动运维，避免人工为网络地址转换设备配置地址转换信息而产生的效率较低和容易出错的问题，提高运维效率、稳定性和可靠性，避免网络中断，进而确保跨协议网络报文及时、准确地转发。
在本申请实施例中，第一互联网协议包括互联网协议第六版IPv6，第二互联网协议包括互联网协议第四版IPv4；或者，第一互联网协议包括互联网协议第四版IPv4，第二互联网协议包括互联网协议第六版IPv6。即业务报文既可以从IPv6网络向IPv4网络转发，也可以从IPv4网络向IPv6网络转发，本申请实施例不做限定，为了更加易于理解和描述，本申请实施例的部分说明中，将上述业务报文称为跨协议网络报文。
另外，本申请实施例中，网络地址转换设备可以是指介于两个不同互联网协议的网络(例如IPv6网络和IPv4网络)之间的报文转发设备，用于跨协议网络转发报文，其可以是从IPv6网络向IPv4网 络转发报文，也可以是从IPv4网络向IPv6网络转发报文，本申请实施例不做限定。
在实际应用中，网络地址转换设备可以具有不同的名称，例如NAT64、NAT46、AFT(Address Family Translation，地址簇转换)等，本申请实施例不做限定。
在本申请实施例的一些实施方式中，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址转换信息。一个示例中，第二应答报文为DNS应答报文。
本实施方式，通过在应答报文中增加附加记录Additional Resource Records(又名附加资源记录，本文统称附加记录)，即可将上述地址转换信息随第二应答报文传递给网络地址转换设备，在现有技术的基础上，对应答报文做轻微的改动即可确保本申请实施例的顺利实施，具有简便易行、实施成本低廉等优点；此外，本申请实施例无需对网络架构中的硬件进行改动，只通过简单的软件升级即可实现功能的升级以实现本申请实施例提供的方法，因此，本申请实施例还具有改造简单易行、改造成本低等优点。
在上述实施方式的基础上，在一些可选实施方式中，在网络地址转换设备接收域名系统针对第二地址查询请求返回的第二应答报文之后，该方法还可以包括：
网络地址转换设备从第二应答报文的附加记录中读取第一网络地址与第二网络地址之间的地址转换信息。
由于应答报文中可能设置有多种附加记录，因此，在另一些可选实施方式中，在网络地址转换设备接收域名系统针对第二地址查询请求返回的第二应答报文之后，该方法还可以包括：
网络地址转换设备从第二应答报文的正文区域查找预定类型的附加记录，从预定类型的附加记录中读取第一网络地址与第二网络地址之间的地址转换信息。
本实施方式中，DNS可以根据预设的格式在应答报文中添加上述附加记录。例如，请参考图4a，图4a示出了本申请实施例的一些实施方式所提供的一种第二应答报文的附加记录的示意图，若第一互联网协议为IPv6，第二互联网协议为IPv4，地址转换信息为用于将第一网络地址与第二网络地址进行转换的前缀信息，则可以在应答报文中根据下表1添加类型为“PREFIX”的附加记录，类型值使用保留位64(此处不做限定，其他值也可以)，用于表示IPv6地址的前缀及长度。
表1
类型 值 含义 参考
PREFIX 64 IPv6地址前缀 新增
上述附加记录的格式和内容可以参考下表2填写：
表2
Figure PCTCN2020123378-appb-000001
Figure PCTCN2020123378-appb-000002
填写后的附加记录可以如图4a所示，此处不再赘述。
如图4b所示，图4b为填写后的附加记录(Additional records)的一种示例。
其中，Name:example.com表示资源记录包含的域名为“example.com”。Type：PREFIX(64)表示资源记录的类型为前缀类型，类型值为64。Class:IN(0x001)表示记录数据(RDATA)的类,其取值为0x0001。TTL：24hours表示附加记录可以缓存的时间为24小时。RDlength：32表示RDATA的长度为32。Rdata：2001：：/96表示附加记录的详细内容为2001：：/96，其中，“2001：：”为IPv6地址的前缀“96”为IPv6地址的长度。
通过上述实施方式，域名系统可以按照预设的格式在第二应答报文中添加附加记录，并指定附加记录的类型，从而可以使得网络地址转换设备可以根据上述格式和类型自动、正确地解析上述附加记录以得到地址转换信息。
在上述实施方式的基础上，在一些可选实施方式中，在从第二应答报文的正文区域查找预定类型的附加记录之前，该方法还可以包括：
若第二应答报文头部信息中的附加记录标识为第一标识，则触发从第二应答报文的正文区域查找预定类型的附加记录的步骤。
本实施方式中，DNS在生成第二应答报文时，可以将第二应答报文头部信息中的附加记录标识修改为第一标识。其中，附加记录标识用于标识该第二应答报文携带的附加记录的数量，例如，附加记录标识为0表示无附加记录，附加记录标识为1表示有1个附加记录，附加记录标识为2表示有2个附加记录。本实施方式中，第一标识可以为任意正整数，即网络地址转换设备若根据附加记录标识确定第二应答报文中有附加记录(不限数量)，即可触发网络地址转换设备从第二应答报文的正文区域查找预定类型的附加记录的步骤。其中，第二应答报文中的“Additional RRs”字段为附加记录标识，“Additional RRs”字段的取值用于表示附加记录的数量。例如，图5中的Additional RRs即为附加记录标识，域名系统将其值修改为1，表示第二应答报文中有一个附加记录。在另一个示例中，若Additional RRs为2，表示第二应答报文中有2个附加记录。
通过本实施方式，可以使网络地址转换设备首先根据附加记录标识确定第二应答报文是否携带有附加记录，若第二应答报文没有携带附加记录，则不必进一步查询附加记录以避免做无用功；若第二应答报文携带有附加记录，再触发网络地址设备执行从第二应答报文的正文区域查找预定类型的附加记录的步骤，从而整体上提高实施效率。
在本申请实施例的一些可选实施方式中，在网络地址转换设备接收域名系统针对第二地址查询请求返回的第二应答报文之后，该方法还可以包括：
网络地址转换设备根据第二应答报文记录的第一网络地址和地址转换信息，确定与第一网络地址对应的第二网络地址，根据第一网络地址、地址转换信息和第二网络地址，生成域名系统缓存表项并存储于本地。
需要说明的是，域名系统缓存表项并不限于包含第一网络地址、地址转换信息和第二网络地址，还可以根据实际需求包括其他字段，本申请实施例不做限定。例如，域名系统缓存表项(DNS缓存表项)可以如下表3所示，其中，IPv6地址和IPv4地址中的一者为第一网络地址，另一者为第二网络地址， 地址转换信息可以是前缀信息(例如2001::)，也可以是DNS缓存表项记录的第一网络地址和第二网络地址之间的对应信息。
表3
域名 IPv6地址 前缀及长度 IPv4地址 老化时间
Example.com 2001::1.2.3.4 2001::/96 1.2.3.4 24hous
…… …… …… …… ……
其中，老化时间TTL可以默认与DNS上的域名记录表项老化时间保持一致，也可手工配置为小于DNS上的域名记录表项的老化时间，本申请实施例不做限定。
通过本实施方式，网络地址转换设备可以生成DNS缓存表项并存储于本地，以便于后续再收到针对目标域名的地址查询请求后，可以直接在本地的DNS缓存表项中查询得到目标域名对应的第一网络地址并反馈给客户端，从而提高域名地址查询效率。
在本申请实施例的一些可选实施方式中，在步骤S101之后，该方法还包括：
网络地址转换设备在本地查询与目标域名对应的网络地址。
参考前述实施方式，在一些实施方式中，网络地址转换设备在本地查询与目标域名对应的网络地址，可以包括：
网络地址转换设备在本地存储的域名系统缓存表项中查询与目标域名对应的网络地址。
通过本实施方式，可以在接收到第一地址查询请求后，首先在本地DNS缓存表项中查询与目标域名对应的网络地址，在从本地DNS缓存表项中查不到的情况下，再从DNS服务器查询，从而可以有效提升域名地址查询效率。
此外，在本申请实施例的一些可选实施方式中，该方法还可以包括：
网络地址转换设备若在本地查询到与目标域名对应的第一网络地址，则触发向客户端发送针对第一地址查询请求的第一应答报文的步骤。
本实施方式中，若网络地址转换设备能够在本地查询到与目标域名对应的第一网络地址，则可以触发步骤S104，而不必再执行步骤S102和S103，从而可以有效提升域名地址查询效率。
容易理解的是，在上述实施方式的基础上，在触发步骤S104的情况下，在步骤S105之前，该方法还可以包括：
网络地址转换设备在本地存储的域名系统缓存表项中查询第一网络地址与第二网络地址之间的地址转换信息，从而确保步骤S105的顺利实施，提高跨协议网络报文的转发效率。
在前述任一实施方式的基础上，在一些可选实施方式中，地址转换信息可以包括用于将第一网络地址与第二网络地址进行转换的前缀信息。
在上述实施方式的基础上，在一些可选实施方式中，网络地址转换设备将业务报文的目的地址转换为第二网络地址，包括：
网络地址转换设备通过对第一网络地址添加或删除前缀信息，将业务报文的目的地址由第一网络地址转换为第二网络地址。
本实施方式，网络地址转换设备通过简单地对第一网络地址添加或删除前缀信息，即可将第一网络地址转换为第二网络地址，具有简单易行、效率高等优点。
在另一些可选实施方式中，在网络地址转换设备接收域名系统针对第二地址查询请求返回的第二应答报文之后，该方法还可以包括：
根据上述前缀信息，生成地址转换规则并存储于本地，地址转换规则的匹配项包括上述前缀信息；
网络地址转换设备将业务报文的目的地址转换为第二网络地址，可以包括：
网络地址转换设备根据第一网络地址的前缀信息，从本地匹配对应的地址转换规则；
若匹配成功，则根据匹配到的地址转换规则，将业务报文的目的地址由第一网络地址转换为第二网络地址。
在一些实例中，地址转换规则可以包括类型项和匹配项，其中类型项可以是“prefix”(表示前缀)，该类型意味着网络地址转换设备可以通过删除前缀信息实现网络地址的转换，匹配项可以包括具体的前缀信息，这样，基于该地址转换规则，网络地址转换设备通过删除前缀信息即可实现网络地址的转换。
例如，若前缀信息如表3所示，则网络地址转换设备根据前缀信息生成的地址转换规则为“nat64prefix-nat64 2001::96”，该地址转换规则的作用是，后续当网络地址转换设备收到前缀为“2001::”的IPv6报文时，通过该地址转换规则删除前缀，将IPv6目的地址(例如2001::1.2.3.4)转换为IPv4地址(例如1.2.3.4)。
通过本实施方式，网络地址转换设备可以准确、方便地将第一网络地址转换为第二网络地址。
此外，为了与正常IPv6地址进行区分，DNS用于网络地址转换的前缀信息可以是指定专用的前缀信息，例如“2001::”、“64:FF9B::”等。DNS64一般默认使用上述指定专用的前缀进行IPv4地址到IPv6地址的合成，因此，DNS合成的多个不同的第一网络地址，其前缀有较大概率是相同的。因此，通过上述实施方式，网络地址转换设备根据上述前缀信息生成地址转换规则后，同一个地址转换规则可用于对多个具有相同前缀的不同第一网络地址进行地址转换，使得网络地址转换设备存储较少的地址转换规则，即可实现对大量网络地址进行跨协议转换。一方面可以节约网络地址转换设备的本地存储空间；另一方面，由于地址转换规则较少，有助于网络地址转换设备根据前缀信息更快地实现地址转换规则的匹配，进而提升网络地址转换效率。
基于上述说明，在一些可选的实施方式中，网络地址转换设备根据前缀信息，生成地址转换规则并存储于本地，可以包括：
网络地址转换设备根据第二应答报文所记录的前缀信息，在本地匹配对应的地址转换规则；
若未匹配到地址转换规则，则网络地址转换设备根据第二应答报文所记录的前缀信息生成地址转换规则并存储于本地；
若匹配到地址转换规则，则触发步骤S104。
由于多个第一网络地址可能具有相同前缀，通过本实施方式，网络地址转换设备在该前缀信息首次出现时生成地址转换规则即可，后续该前缀信息再次出现时可以不必再次生成地址转换规则，从而可以有效减少生成地址转换规则给网络地址转换设备带来的冗余工作和系统负荷，提升网络地址转换设备工作效率。
为了便于理解，请参考图6，其示出了本申请实施例所提供的一种第二应答报文处理方法的流程图，前述实施例可以参考图6进行理解，图6也可以参照前述实施例的描述进行理解，此处不再赘述。
图6中，AAAA应答报文可以理解为DNS应答报文，网络地址转换设备在接收到AAAA应答报文(即第二应答报文)后，可以首先判断该第二应答报文是否存在附加记录，然后判断该附加记录的类型(type) 是否为预定类型(例如“prefix”)，若否，则按其他类型的附加记录进行处理，若是，则解析该附加记录，得到前缀信息(即地址转换信息)、第二网络地址(即图中的IPv4地址)等相关信息，然后，根据上述信息生成地址转换规则(即图中的NAT64转换配置)，然后将IPv6地址(即第一网络地址)添加到第一应答报文后返回给客户端。
在图6中，作为示例，第一互联网协议为IPV6，第一网络地址为IPV6地址，第二互联网协议为IPV4，第二网络地址为IPV4地址。上述域名系统包括DNS64服务器，相应地，网络地址转换设备可以为NAT64设备。具体而言，图6中，NAT64设备在接收到来自DNS64服务器的DNS AAAA应答报文(即第二应答报文)后，可以判断该DNS AAAA应答报文是否存在附加记录，若不存在附加记录，则按普通DNS应答报文进行处理；若存在附加记录，则判断该附加记录的类型(type)是否为预定类型(例如“prefix”)。若该附加记录的类型不是预定类型，则网络地址转换设备按其他类型的附加记录进行处理；若该附加记录的类型是预定类型，则解析附加记录中的前缀和长度，缓存查询域名和合成IPv6地址、前缀及长度、真实IPv4地址的对应关系。其中，通过解析该附加记录，可以得到前缀信息(即地址转换信息)、IPV6地址(即第一网络地址)等相关信息。通过解析该附加记录得到的信息可以参考上文中表2的相关描述，此处不再赘述。网络地址转换设备根据前缀信息，将IPv6地址(即第一网络地址)转换为IPV4地址(即第二网络地址)，并缓存该前缀信息、该IPv6地址和该IPv4地址之间的对应关系。
然后，NAT64设备自动生成对应的NAT64转换配置，用于将以DNS AAAA应答报文中的IPv6地址为目的地址的报文中的IPv6地址转换为对应的IPv4地址。即NAT64设备根据缓存的上述IPv6地址和IPv4地址之间的对应关系生成NAT64转换配置(即地址转换规则)，该NAT64转换配置用于在后续接收到业务报文时，若该业务报文的目的地址为上述DNS AAAA应答报文中的IPv6地址，则将IPv6地址转换为对应的IPv4地址。
然后NAT64设备将合成的IPv6地址填入DNS AAAA应答报文，返回给IPv6客户端。即NAT64设备将IPv6地址(即第一网络地址)添加到DNS AAAA应答报文(第一应答报文)后，将该DNS AAAA应答报文返回IPv6客户端。
上述实施方式，既可以确保域名地址查询的顺利实施，又可以在无人工参与的情况下，使得网络地址转换设备可自动、实时地获取到上述地址转换信息，从而实现网络地址转换设备的自动运维，避免人工为网络地址转换设备配置地址转换信息而产生的效率较低和容易出错的问题，提高运维效率、稳定性和可靠性，避免网络中断，进而确保跨协议网络报文及时、准确地转发。
在本申请实施例的另一些实施方式中，地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
上述对应信息可以记录有具有对应关系的第一网络地址和第二网络地址。
通过本实施方式，也可以有效确保准确地将第一网络地址与第二网络地址进行转换，以确保网络地址转换设备能够准确、及时地转发跨协议网络报文。
在上述实施方式的基础上，在一些可选实施方式中，网络地址转换设备将业务报文的目的地址转换为第二网络地址，可以包括：
网络地址转换设备根据对应信息，将业务报文的目的地址由第一网络地址替换为第二网络地址。
通过本实施方式，网络地址转换设备可以通过简单的替换操作将第一网络地址转换为第二网络地址，具有简便易行、效率较高等优点。
需要说明的是，在一些可选的实施方式中，步骤S105中，网络地址转换设备可以是从域名系统缓存表项中查询业务报文的目的地址对应的地址转换信息，然后根据查到的地址转换信息进行目的地址的转换。步骤S105，具体可以实现为：
网络地址转换设备接收客户端发送的目的地址为第一网络地址的业务报文，在本地存储的域名系统缓存表项中查询第一网络地址对应的地址转换信息，根据查询到的地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文。
例如，如前述关于域名系统缓存表项的示例性描述，域名系统缓存表项可以包括第一网络地址、地址转换信息和第二网络地址，地址转换信息可以是前缀信息(例如2001::)，也可以是域名系统缓存表项记录的第一网络地址和第二网络地址之间的对应信息。
因此，网络地址转换设备根据上述域名系统缓存表项，即可查到第一网络地址与第二网络地址之间的对应信息，并根据该对应信息，将业务报文的目的地址由第一网络地址替换为第二网络地址。或者，网络地址转换设备根据上述域名系统缓存表项，可以查到与第一网络地址对应的前缀信息，根据该前缀信息，即可通过对第一网络地址添加或删除前缀信息，将业务报文的目的地址由第一网络地址转换为第二网络地址。例如，若第一网络地址为IPv6地址，则网络地址转换设备查到前缀信息后，通过删除第一网络地址中的该前缀信息，即可将第一网络地址转换为IPv4地址(即第二网络地址)。又例如，若第一网络地址为IPv4地址，则网络地址转换设备查到前缀信息后，通过在第一网络地址中增加该前缀信息，即可将第一网络地址转换为IPv6地址(即第二网络地址)。
通过本实施方式，网络地址转换设备利用域名系统缓存表项，既可以实现由IPv6地址向IPv4地址的转换，也可以实现由IPv4地址向IPv6地址的转换，具有转换准确性高、效率高等优点。
在其他一些实施例中，可以结合域名系统缓存表项和地址转换规则实现IPv6地址与IPv4地址之间的转换。
例如，若地址转换规则为“nat64 prefix-nat64 2001::96”，该地址转换规则的作用是，后续当网络地址转换设备收到前缀为“2001::”的IPv6报文时，通过该地址转换规则删除前缀，将IPv6目的地址(例如2001::1.2.3.4)转换为IPv4地址(例如1.2.3.4)。又例如，当网络地址转换设备收到目的地址为1.2.3.4的IPv4报文时，未匹配到地址转换规则，此时则在域名系统缓存表项(如表3所示)查询IP地址1.2.3.4。经过查询，查找到对应的表项，则在IPv4报文的目的地址1.2.3.4增加前缀“2001::”，得到对应的IPv6目的地址2001::1.2.3.4。
在上述的实施例中，提供了一种报文转发方法，与之相对应的，本申请实施例还提供一种报文转发装置。本申请实施例提供的报文转发装置可以实施上述报文转发方法，该报文转发装置可以通过软件、硬件或软硬结合的方式来实现。例如，该报文转发装置可以包括集成的或分开的功能模块或单元来执行上述各方法中的对应步骤。请参考图7，其示出了本申请实施例提供的一种报文转发装置的示意图。由于装置实施例基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。下述描述的装置实施例仅仅是示意性的。
如图7所示，本申请实施例提供一种报文转发装置，应用于网络地址转换设备，该装置可以包括：
第一查询请求接收模块101，用于接收客户端发送的针对目标域名的第一地址查询请求，其中，客户端使用第一互联网协议，目标域名对应的目标服务器使用第二互联网协议；
第二查询请求发送模块102，用于若在本地未查询到与目标域名对应的网络地址，则向域名系统发送针对目标域名的第二地址查询请求；
第二应答报文接收模块103，用于接收域名系统针对第二地址查询请求返回的第二应答报文，其中，第二应答报文记录有第一网络地址和第一网络地址与第二网络地址之间的地址转换信息，第二网络地址包括目标域名对应的支持第二互联网协议的网络地址，第一网络地址包括域名系统根据第二网络地址转换得到的支持第一互联网协议的网络地址；
第一应答报文发送模块104，用于向客户端发送针对第一地址查询请求的第一应答报文，其中，第一应答报文包括第一网络地址；
业务报文转发模块105，用于接收客户端发送的目的地址为第一网络地址的业务报文，根据地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文。
在本申请实施例的一些可选实施方式中，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址转换信息。
在本申请实施例的一些可选实施方式中，该装置还可以包括：
附加记录查询模块，用于从第二应答报文的正文区域查找预定类型的附加记录；
附加记录读取模块，用于从预定类型的附加记录中读取第一网络地址与第二网络地址之间的地址转换信息。
在本申请实施例的一些可选实施方式中，该装置还可以包括：
信息读取触发模块，用于若第二应答报文头部信息中的附加记录标识为第一标识，则触发附加记录读取模块运行。
在本申请实施例的一些可选实施方式中，该装置还可以包括：
第二网络地址确定模块，用于根据第二应答报文记录的第一网络地址和地址转换信息，确定与第一网络地址对应的第二网络地址；
缓存表项生成模块，用于根据第一网络地址、地址转换信息和第二网络地址，生成域名系统缓存表项并存储于本地。
在本申请实施例的一些可选实施方式中，该装置还可以包括：
本地查询成功处理模块，用于若在本地查询到与目标域名对应的第一网络地址，则触发第一应答报文发送模块104运行。
在本申请实施例的一些可选实施方式中，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息；
或者，
地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
在本申请实施例的一些可选实施方式中，业务报文转发模块105，可以包括：
对应信息转换单元，用于根据上述对应信息，将业务报文的目的地址由第一网络地址替换为第二网络地址。
在本申请实施例的一些可选实施方式中，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息；
该装置还可以包括：
地址转换规则生成模块，用于根据前缀信息，生成地址转换规则并存储于本地，地址转换规则的匹配项包括前缀信息；
业务报文转发模块105，可以包括：
地址转换规则匹配单元，用于根据第一网络地址的前缀信息，从本地匹配对应的地址转换规则；
根据规则转换单元，用于若匹配成功，则根据匹配到的地址转换规则，将业务报文的目的地址由第一网络地址转换为第二网络地址。
在本申请实施例的一种可选实施方式中，第一互联网协议可以包括互联网协议第六版IPv6，第二互联网协议可以包括互联网协议第四版IPv4；或者，
第一互联网协议可以包括互联网协议第四版IPv4，第二互联网协议可以包括互联网协议第六版IPv6。
本申请实施例提供的报文转发装置，与本申请前述实施例提供的报文转发方法出于相同的发明构思，具有相同的有益效果。
在上述的实施例中，提供了一种报文转发方法，与之相对应的，本申请还提供一种域名地址查询方法，域名地址查询方法是与前述报文转发方法互相配合实施的，属于相同的发明构思。因此，以下关于域名地址查询方法的实施例，可参照前述关于报文转发方法的实施例进行理解，部分内容不再赘述。相应的，前述关于报文转发方法的实施例，也可以参照下述关于域名地址查询方法的实施例进行理解。
请参考图8，其示出了本申请实施例提供的一种域名地址查询方法的流程图，该域名地址查询方法应用于域名系统，可以参考图11所示的时序图对该方法进行理解，该方法可以包括以下步骤：
步骤S201：接收网络地址转换设备发送的针对目标域名的第二地址查询请求，其中，第二地址查询请求的源地址支持第一互联网协议。
步骤S202：响应于第二地址查询请求，查询与目标域名对应的第二网络地址，其中，第二网络地址支持第二互联网协议。
步骤S203：将第二网络地址转换为支持第一互联网协议的第一网络地址。
步骤S204：向网络地址转换设备发送针对第二地址查询请求的第二应答报文，其中，第二应答报文包括第一网络地址和第一网络地址与第二网络地址之间的地址转换信息，以使网络地址转换设备向客户端发送第一网络地址，并根据地址转换信息对客户端发送的目的地址为第一网络地址的业务报文进行目的地址转换。
其中，网络地址转换设备接收到客户端发送的业务报文后，若该业务报文的目的地址为第一网络地址，则网络地址转换设备可以根据地址转换信息，将该业务报文的目的地址转换为第二网络地址。
本申请实施例提供的域名地址查询方法，与本申请前述实施例提供的报文转发方法出于相同的发明构思，至少具有以下相应的有益效果：域名系统在接收到跨协议的地址查询请求后，首先查询目标域名对应的支持第二互联网协议的第二网络地址，然后将第二网络地址转换为支持第一互联网协议的第一网络地址。然后域名系统向网络地址转换设备发送第一网络地址与第二网络地址之间的地址转换信息，从而可以使网络地址转换设备根据地址转换信息自动实现与域名系统的同步，促使网络地址转换设备实现自动运维，进而避免人工为网络地址转换设备配置地址转换信息而产生的效率较低和容易出错的问题，提高运维效率、稳定性和可靠性，避免网络中断，有助于确保网络地址转换设备及时、准确地跨协议网 络转发报文。
此外，域名系统通过向网络地址转换设备发送第一网络地址，可以确保网络地址转换设备将查到的第一网络地址返回给客户端以实现代理DNS的功能，进而确保域名地址查询的顺利实施。且域名系统将第一网络地址和地址转换信息一并发送给网络地址转换设备，可以有效简化域名系统、网络地址转换设备和客户端三者之间的数据传递流程、提高数据传递效率、节省网络传输资源。
在本申请实施例的一些可选实施方式中，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址转换信息。
关于附加记录的相关说明，可以参照前述关于报文转发方法的实施例的相关描述及图4、图5、图6的相关描述，此处不再赘述。
在本申请实施例的一些可选实施方式中，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息。
关于前缀信息的相关说明，可以参照前述关于报文转发方法的实施例的相关描述及图4、图5、图6的相关描述，此处不再赘述。
为了便于理解，请参考图9，其示出了本申请实施例所提供的一种域名地址查询方法的流程图，前述实施例说明可以参考图9进行理解，图9也可以参照前述实施例的描述进行理解，此处不再赘述。
图9中，AAAA应答报文可以理解为DNS应答报文，DNS在接收到AAAA查询报文(即第二地址查询请求)后，可以首先查询是否有与目标域名对应的AAAA记录(IPv6的域名地址)，若有，则直接返回AAAA记录，若没有，则进一步查询是否有A记录(IPv4的域名地址)，若没有，则返回空值，若有，则使用预设的IPv6前缀合成IPv6地址并返回AAAA应答报文(即第二应答报文)，并在该第二应答报文中添加附加记录，在该附加记录中记录上述IPv6前缀和长度信息。
作为示例，图9所示的流程由DNS64服务器执行，相应地，网络地址转换设备可以为NAT64设备。第一互联网协议为IPV6，第一网络地址为IPV6地址，第二互联网协议为IPV4，第二网络地址为IPV4地址。
具体而言，图9中，DNS64服务器在接收到AAAA查询报文(即第二地址查询请求)后，可以首先查询是否有与目标域名对应的AAAA记录(IPv6的域名地址)，若有目标域名对应的AAAA记录，则直接向NAT64设备返回AAAA记录；若没有目标域名对应的AAAA记录，则DNS64服务器进一步查询是否有A记录(IPv4的域名地址)。若没有A记录，则返回空值；若有A记录，则使用预设的IPv6前缀合成IPv6地址，并向NAT64设备返回AAAA应答报文(即第二应答报文)，该第二应答报文中包括附加记录，该附加记录中记录有上述IPv6前缀，该附加记录包括的其他信息可以参见上述表2的相关描述，此处不再赘述。
在本申请实施例的一些可选实施方式中，地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
与上述表2类似的，作为一种可选实施方式，该对应信息可以参考下述表4填写到附加记录中：
表4
Figure PCTCN2020123378-appb-000003
Figure PCTCN2020123378-appb-000004
通过上述实施方式，可以按照预设的格式添加附加记录，并指定附加记录的类型，从而可以确保网络地址转换设备可以根据上述格式和类型自动、正确地解析上述附加记录以得到地址转换信息。
在本申请实施例的一些可选实施方式中，将第二网络地址转换为支持第一互联网协议的第一网络地址，包括：
从预设的地址池中选取一个支持第一互联网协议的网络地址，作为与第二网络地址进行转换的第一网络地址。也就是说，域名系统将从预设地址池中选取的网络地址作为上述第一网络地址。
例如，若第一互联网协议为IPv6，第二互联网协议为IPv4，可以预先在DNS上配置一个IPv6地址池。DNS收到第二地址查询请求后，若查询到目标域名对应的第二网络地址为IPv4地址，则可以从IPv6地址池中挑选一个IPv6地址地址，作为与第二网络地址进行转换的第一网络地址分配给该目标域名。即，将该IPv6地址分配给该目标域名。
通过本实施方式，域名系统可以利用地址池便捷地将第二网络地址转换为第一网络地址，具有实施方便、高效等优点。
在上述的实施例中，提供了一种域名地址查询方法，与之相对应的，本申请实施例还提供一种域名地址查询装置。本申请实施例提供的域名地址查询装置可以实施上述域名地址查询方法，该域名地址查询装置可以通过软件、硬件或软硬结合的方式来实现。例如，该域名地址查询装置可以包括集成的或分开的功能模块或单元来执行上述各方法中的对应步骤。请参考图10，其示出了本申请实施例提供的一种域名地址查询装置的示意图。由于装置实施例基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。下述描述的装置实施例仅仅是示意性的。
本申请实施例的域名地址查询装置应用于域名系统，如图10所示，该装置可以包括：
第二地址查询请求接收模块201，用于接收网络地址转换设备发送的针对目标域名的第二地址查询请求，其中，第二地址查询请求的源地址支持第一互联网协议；
第二地址查询请求处理模块202，用于响应于第二地址查询请求，查询与目标域名对应的第二网络地址，其中，第二网络地址支持第二互联网协议；
网络地址转换模块203，用于将第二网络地址转换为支持第一互联网协议的第一网络地址；
第二应答报文发送模块204，用于向网络地址转换设备发送针对第二地址查询请求的第二应答报文，其中，第二应答报文包括第一网络地址和第一网络地址与第二网络地址之间的地址转换信息，以使网络地址转换设备向客户端发送第一网络地址，并根据地址转换信息对客户端发送的目的地址为第一网络地址的业务报文进行目的地址转换。
在本申请实施例的一些可选实施方式中，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址转换信息。
在本申请实施例的一些可选实施方式中，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息。
在本申请实施例的一些可选实施方式中，地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
在本申请实施例的一些可选实施方式中，网络地址转换模块203，包括：
网络地址选取单元，用于从预设的地址池中选取一个支持第一互联网协议的网络地址，作为与第二网络地址进行转换的第一网络地址。
本申请实施例提供的域名地址查询装置，与本申请前述实施例提供的域名地址查询方法出于相同的发明构思，具有相同的有益效果。
为了便于理解，下面结合图11所示的时序图对本申请实施例提供的方法进行示例性说明，下述示例性说明可以参照前述关于报文转发方法和域名地址查询方法的实施例中的相关描述，前述关于报文转发方法和域名地址查询方法的实施例也可以参照下述示例性说明进行理解。
请参考图11，该具体实施例至少可以包括以下步骤S301-S310。
步骤S301：支持第一互联网协议的客户端在需要查询目标域名对应的地址时，向网络地址转换设备发送针对目标域名的第一地址查询请求。
步骤S302：网络地址转换设备接收到第一地址查询请求后，在本地查询与目标域名对应的网络地址，若未查到，则向域名系统发送针对目标域名的第二地址查询请求。
步骤S303：域名系统在接收到第二地址查询请求后，若查询到的第二网络地址仅支持第二互联网协议，则将查到的第二网络地址转换为支持第一互联网协议的第一网络地址。
步骤S304：域名系统向网络地址转换设备发送针对第二地址查询请求的第二应答报文，第二应答报文记录有第一网络地址和第一网络地址与第二网络地址之间的地址转换信息。
步骤S305：网络地址转换设备接收到第二应答报文后，向客户端发送针对第一地址查询请求的第一应答报文，其中，第一应答报文包括第一网络地址。
步骤S306：网络地址转换设备还至少将第一网络地址与第二网络地址之间的地址转换信息存储至本地。
步骤S307：客户端在接收到上述第一网络地址后，根据该第一网络地址向目标域名对应的目标服务器发送业务报文，该业务报文的目的地址为第一网络地址。
步骤S308：网络地址转换设备接收到业务报文后，根据上述地址转换信息将业务报文的目的地址由第一网络地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文，同时生成客户端与目标服务器之间的会话表项。
步骤S309：目标服务器在接收到上述业务报文后，可以返回针对该业务报文的响应报文，其中，该响应报文的源地址即为上述第二网络地址。
步骤S310：网络地址转换设备接收到上述响应报文后，再根据上述会话表项将响应报文的源地址由第二网络地址转换为第一网络地址，并向客户端发送转换后的响应报文。
与本申请前述实施例提供的报文转发方法对应，本申请实施例还提供一种网络地址转换设备，如图12所示，包括处理器1201、机器可读存储介质1202和收发器1204。机器可读存储介质1202存储有能够被处理器1201执行的机器可执行指令；机器可执行指令促使处理器1201执行以下步骤：
通过收发器1204接收客户端发送的针对目标域名的第一地址查询请求，其中，客户端使用第一互联网协议，目标域名对应的目标服务器使用第二互联网协议；
若在本地未查询到与目标域名对应的网络地址，则通过收发器1204向域名系统发送针对目标域名的第二地址查询请求；
通过收发器1204接收域名系统针对第二地址查询请求返回的第二应答报文，其中，第二应答报文记录有第一网络地址和第一网络地址与第二网络地址之间的地址转换信息，第二网络地址包括目标域名对应的支持第二互联网协议的网络地址，第一网络地址包括域名系统根据第二网络地址转换得到的支持第一互联网协议的网络地址；
通过收发器1204向客户端发送针对第一地址查询请求的第一应答报文，其中，第一应答报文包括第一网络地址；
通过收发器1204接收客户端发送的目的地址为第一网络地址的业务报文，并根据地址转换信息，将业务报文的目的地址转换为第二网络地址，并向目标服务器发送目的地址转换后的业务报文。
可选地，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址转换信息。
可选地，机器可执行指令还促使处理器1201执行以下步骤：
在接收域名系统针对第二地址查询请求返回的第二应答报文之后，从第二应答报文的正文区域查找预定类型的附加记录；
从预定类型的附加记录中读取第一网络地址与第二网络地址之间的地址转换信息。
可选地，机器可执行指令还促使处理器1201执行以下步骤：
若第二应答报文头部信息中的附加记录标识为第一标识，则触发从第二应答报文的正文区域查找预定类型的附加记录的步骤。
可选地，机器可执行指令还促使处理器1201执行以下步骤：
在接收域名系统针对第二地址查询请求返回的第二应答报文之后，根据第二应答报文记录的第一网络地址和地址转换信息，确定与第一网络地址对应的第二网络地址；
根据第一网络地址、地址转换信息和第二网络地址，生成域名系统缓存表项并存储于本地。
可选地，机器可执行指令还促使处理器1201执行以下步骤：
若在本地查询到与目标域名对应的第一网络地址，则触发向客户端发送针对第一地址查询请求的第一应答报文的步骤。
可选地，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息；
或者，
地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
可选地，机器可执行指令还促使处理器1201执行以下步骤：
通过对第一网络地址添加或删除前缀信息，将业务报文的目的地址由第一网络地址转换为第二网络地址；或者，
根据对应信息，将业务报文的目的地址由第一网络地址替换为第二网络地址。
可选地，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息；
机器可执行指令还促使处理器1201执行以下步骤：
在接收域名系统针对第二地址查询请求返回的第二应答报文之后，根据前缀信息，生成地址转换规则并存储于本地，地址转换规则的匹配项包括前缀信息；
机器可执行指令还促使处理器1201执行以下步骤：
根据第一网络地址的前缀信息，从本地匹配对应的地址转换规则；
若匹配成功，则根据匹配到的地址转换规则，将业务报文的目的地址由第一网络地址转换为第二网络地址。
如图12所示，网络地址转换设备还可以包括通信总线1203。处理器1201、机器可读存储介质1202及收发器1204之间通过通信总线1203完成相互间的通信，通信总线1203可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。该通信总线1203可以分为地址总线、数据总线、控制总线等。
收发器1204可以为无线通信模块，收发器1204在处理器1201的控制下，与其他设备(AC和终端)进行数据交互。
机器可读存储介质1202可以包括随机存取存储器(Random Access Memory，RAM)，也可以包括非易失性存储器(Non-Volatile Memory，NVM)，例如至少一个磁盘存储器。另外，机器可读存储介质1202还可以是至少一个位于远离前述处理器的存储装置。
处理器1201可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本申请实施例提供的网络地址转换设备与本申请实施例提供的报文转发方法出于相同的技术构思，具有与其采用、运行或实现的方法相同的有益效果。
与本申请前述实施例提供的域名地址查询方法对应，本申请实施例还提供一种域名系统，如图13所示，包括处理器1301、机器可读存储介质1302和收发器1304。机器可读存储介质1302存储有能够被处理器1301执行的机器可执行指令；机器可执行指令促使处理器1301执行以下步骤：
通过收发器1304接收网络地址转换设备发送的针对目标域名的第二地址查询请求，其中，第二地址查询请求的源地址支持第一互联网协议；
响应于第二地址查询请求，查询与目标域名对应的第二网络地址，其中，第二网络地址支持第二互联网协议；
将第二网络地址转换为支持第一互联网协议的第一网络地址；
通过收发器1304向网络地址转换设备发送针对第二地址查询请求的第二应答报文，其中，第二应答报文包括第一网络地址、和第一网络地址与第二网络地址之间的地址转换信息，以使网络地址转换设备向客户端发送第一网络地址、并根据地址转换信息对客户端发送的目的地址为第一网络地址的业务报文进行目的地址转换。
可选地，第二应答报文包括附加记录，附加记录用于记录第一网络地址与第二网络地址之间的地址 转换信息。
可选地，地址转换信息包括用于将第一网络地址与第二网络地址进行转换的前缀信息；或者，
地址转换信息包括第一网络地址与第二网络地址之间的对应信息。
可选地，地址转换信息包括第一网络地址与第二网络地址之间的对应信息；
机器可执行指令还促使处理器1301执行以下步骤：
从预设的地址池中选取一个支持第一互联网协议的网络地址，作为与第二网络地址进行转换的第一网络地址。
如图13所示，网络地址转换设备还可以包括通信总线1303。处理器1301、机器可读存储介质1302及收发器1304之间通过通信总线1303完成相互间的通信，通信总线1303可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。该通信总线1303可以分为地址总线、数据总线、控制总线等。
收发器1304可以为无线通信模块，收发器1304在处理器1301的控制下，与其他设备(AC和终端)进行数据交互。
机器可读存储介质1302可以包括随机存取存储器(Random Access Memory，RAM)，也可以包括非易失性存储器(Non-Volatile Memory，NVM)，例如至少一个磁盘存储器。另外，机器可读存储介质1302还可以是至少一个位于远离前述处理器的存储装置。
处理器1301可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本申请实施例提供的域名系统与本申请实施例提供的域名地址查询方法出于相同的技术构思，具有与其采用、运行或实现的方法相同的有益效果。
本申请实施方式还提供一种与前述实施方式所提供的报文转发方法和域名地址查询方法对应的计算机可读介质，请参考图14，其示出的计算机可读存储介质为光盘40，其上存储有计算机程序(即程序产品)，所述计算机程序在被处理器(例如上述处理器)运行时，会执行前述任意实施方式所提供的报文转发方法或域名地址查询方法。
需要说明的是，所述计算机可读存储介质的例子还可以包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他光学、磁性存储介质，在此不再一一赘述。
本申请的上述实施例提供的计算机可读存储介质与本申请实施例提供的报文转发方法和域名地址查询方法出于相同的发明构思，具有与其存储的应用程序所采用、运行或实现的方法相同的有益效果。
在本申请提供的另一实施例中，还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述实施例中任一报文转发方法或域名地址查询方法。
需要说明的是，附图中的流程图和框图显示了根据本申请的多个实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的一部分，所述模块、程序段或代码的一部分包含一个或多个用于实现规定的逻辑功能的 可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，又例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些物理端口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本申请的较佳实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (15)

  1. 一种报文转发方法，应用于网络地址转换设备，包括：
    接收客户端发送的针对目标域名的第一地址查询请求，其中，所述客户端使用第一互联网协议，所述目标域名对应的目标服务器使用第二互联网协议；
    若在本地未查询到与所述目标域名对应的网络地址，则向域名系统发送针对所述目标域名的第二地址查询请求；
    接收所述域名系统针对所述第二地址查询请求返回的第二应答报文，其中，所述第二应答报文记录有第一网络地址和所述第一网络地址与第二网络地址之间的地址转换信息，所述第二网络地址包括所述目标域名对应的支持所述第二互联网协议的网络地址，所述第一网络地址包括所述域名系统根据所述第二网络地址转换得到的支持所述第一互联网协议的网络地址；
    向所述客户端发送针对所述第一地址查询请求的第一应答报文，其中，所述第一应答报文包括所述第一网络地址；
    接收所述客户端发送的目的地址为所述第一网络地址的业务报文，根据所述地址转换信息，将所述业务报文的目的地址转换为所述第二网络地址，并向所述目标服务器发送目的地址转换后的业务报文。
  2. 根据权利要求1所述的方法，所述第二应答报文包括附加记录，所述附加记录用于记录所述第一网络地址与第二网络地址之间的地址转换信息；
    所述接收所述域名系统针对所述第二地址查询请求返回的第二应答报文之后，还包括：
    从所述第二应答报文的正文区域查找预定类型的附加记录；
    从所述预定类型的附加记录中读取所述第一网络地址与第二网络地址之间的地址转换信息。
  3. 根据权利要求2所述的方法，所述从所述第二应答报文的正文区域查找预定类型的附加记录之前，还包括：
    若所述第二应答报文头部信息中的附加记录标识为第一标识，则触发从所述第二应答报文的正文区域查找预定类型的附加记录的步骤。
  4. 根据权利要求1所述的方法，所述接收所述域名系统针对所述第二地址查询请求返回的第二应答报文之后，还包括：
    根据所述第二应答报文记录的所述第一网络地址和所述地址转换信息，确定与所述第一网络地址对应的第二网络地址；
    根据所述第一网络地址、所述地址转换信息和所述第二网络地址，生成域名系统缓存表项并存储于本地。
  5. 根据权利要求1所述的方法，所述方法还包括：
    若在本地查询到与所述目标域名对应的第一网络地址，则触发向所述客户端发送针对所述第一地址查询请求的第一应答报文的步骤。
  6. 根据权利要求1至5任一项所述的方法，所述地址转换信息包括用于将所述第一网络地址与所述第二网络地址进行转换的前缀信息；
    或者，
    所述地址转换信息包括所述第一网络地址与所述第二网络地址之间的对应信息。
  7. 根据权利要求6所述的方法，所述将所述业务报文的目的地址转换为所述第二网络地址，包括：
    通过对所述第一网络地址添加或删除所述前缀信息，将所述业务报文的目的地址由所述第一网络地址转换为所述第二网络地址；或者，
    根据所述对应信息，将所述业务报文的目的地址由所述第一网络地址替换为所述第二网络地址。
  8. 根据权利要求6所述的方法，所述地址转换信息包括用于将所述第一网络地址与所述第二网络地址进行转换的前缀信息；
    所述接收所述域名系统针对所述第二地址查询请求返回的第二应答报文之后，还包括：
    根据所述前缀信息，生成地址转换规则并存储于本地，所述地址转换规则的匹配项包括所述前缀信息；
    所述将所述业务报文的目的地址转换为所述第二网络地址，包括：
    根据所述第一网络地址的前缀信息，从本地匹配对应的地址转换规则；
    若匹配成功，则根据匹配到的所述地址转换规则，将所述业务报文的目的地址由所述第一网络地址转换为所述第二网络地址。
  9. 一种域名地址查询方法，应用于域名系统，包括：
    接收网络地址转换设备发送的针对目标域名的第二地址查询请求，其中，所述第二地址查询请求的源地址支持第一互联网协议；
    响应于所述第二地址查询请求，查询与所述目标域名对应的第二网络地址，其中，所述第二网络地址支持第二互联网协议；
    将所述第二网络地址转换为支持所述第一互联网协议的第一网络地址；
    向所述网络地址转换设备发送针对所述第二地址查询请求的第二应答报文，其中，所述第二应答报文包括所述第一网络地址、和所述第一网络地址与所述第二网络地址之间的地址转换信息，以使所述网络地址转换设备向客户端发送所述第一网络地址、并根据所述地址转换信息对所述客户端发送的目的地址为所述第一网络地址的业务报文进行目的地址转换。
  10. 根据权利要求9所述的方法，所述第二应答报文包括附加记录，所述附加记录用于记录所述第一网络地址与第二网络地址之间的地址转换信息。
  11. 根据权利要求9或10所述的方法，所述地址转换信息包括用于将所述第一网络地址与所述第二网络地址进行转换的前缀信息；或者，
    所述地址转换信息包括所述第一网络地址与所述第二网络地址之间的对应信息。
  12. 根据权利要求9或10所述的方法，所述地址转换信息包括所述第一网络地址与所述第二网络地址之间的对应信息；
    所述将所述第二网络地址转换为支持所述第一互联网协议的第一网络地址，包括：
    从预设的地址池中选取一个支持第一互联网协议的网络地址，作为与所述第二网络地址进行转换的第一网络地址。
  13. 一种网络地址转换设备，包括：
    处理器；
    收发器；
    机器可读存储介质，所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令；所述机器可执行指令促使所述处理器执行以下步骤：
    通过所述收发器接收客户端发送的针对目标域名的第一地址查询请求，其中，所述客户端使用第一互联网协议，所述目标域名对应的目标服务器使用第二互联网协议；
    若在本地未查询到与所述目标域名对应的网络地址，则通过所述收发器向域名系统发送针对所述目标域名的第二地址查询请求；
    通过所述收发器接收所述域名系统针对所述第二地址查询请求返回的第二应答报文，其中，所述第二应答报文记录有第一网络地址和所述第一网络地址与第二网络地址之间的地址转换信息，所述第二网络地址包括所述目标域名对应的支持所述第二互联网协议的网络地址，所述第一网络地址包括所述域名系统根据所述第二网络地址转换得到的支持所述第一互联网协议的网络地址；
    通过所述收发器向所述客户端发送针对所述第一地址查询请求的第一应答报文，其中，所述第一应答报文包括所述第一网络地址；
    通过所述收发器接收所述客户端发送的目的地址为所述第一网络地址的业务报文，并根据所述地址转换信息，将所述业务报文的目的地址转换为所述第二网络地址，并向所述目标服务器发送目的地址转换后的业务报文。
  14. 一种域名系统，包括：
    处理器；
    收发器；
    机器可读存储介质，所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令；所述机器可执行指令促使所述处理器执行以下步骤：
    通过所述收发器接收网络地址转换设备发送的针对目标域名的第二地址查询请求，其中，所述第二地址查询请求的源地址支持第一互联网协议；
    响应于所述第二地址查询请求，查询与所述目标域名对应的第二网络地址，其中，所述第二网络地址支持第二互联网协议；
    将所述第二网络地址转换为支持所述第一互联网协议的第一网络地址；
    通过所述收发器向所述网络地址转换设备发送针对所述第二地址查询请求的第二应答报文，其中，所述第二应答报文包括所述第一网络地址、和所述第一网络地址与所述第二网络地址之间的地址转换信息，以使所述网络地址转换设备向客户端发送所述第一网络地址、并根据所述地址转换信息对所述客户端发送的目的地址为所述第一网络地址的业务报文进行目的地址转换。
  15. 一种计算机可读介质，其特征在于，其上存储有计算机可读指令，所述计算机可读指令可被处理器执行以实现如权利要求1至8、9至12任一项所述的方法。
PCT/CN2020/123378 2019-10-25 2020-10-23 报文转发及域名地址查询 WO2021078281A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022521052A JP7478820B2 (ja) 2019-10-25 2020-10-23 メッセージ転送及びドメイン名アドレスクエリ
EP20879262.2A EP4033729B1 (en) 2019-10-25 2020-10-23 Message forwarding and domain name address query

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911024527.7A CN110784562B (zh) 2019-10-25 2019-10-25 报文转发、域名地址查询方法、装置、设备及介质
CN201911024527.7 2019-10-25

Publications (1)

Publication Number Publication Date
WO2021078281A1 true WO2021078281A1 (zh) 2021-04-29

Family

ID=69387833

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123378 WO2021078281A1 (zh) 2019-10-25 2020-10-23 报文转发及域名地址查询

Country Status (4)

Country Link
EP (1) EP4033729B1 (zh)
JP (1) JP7478820B2 (zh)
CN (1) CN110784562B (zh)
WO (1) WO2021078281A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738866A (zh) * 2020-12-31 2021-04-30 百果园技术(新加坡)有限公司 一种终端接入方法、装置、设备及介质
CN113938459A (zh) * 2021-09-06 2022-01-14 锐捷网络股份有限公司 一种IPv6配置方法及装置
CN114268605A (zh) * 2021-12-16 2022-04-01 云盾智慧安全科技有限公司 一种智能dns实现方法、装置及计算机存储介质
CN114268604A (zh) * 2021-12-21 2022-04-01 中国电信股份有限公司 访问服务的提供方法和系统
CN115037551A (zh) * 2022-06-29 2022-09-09 北京奇艺世纪科技有限公司 连接权限控制方法、装置、电子设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113783974B (zh) * 2021-09-09 2023-06-13 烽火通信科技股份有限公司 一种动态下发map域规则的方法及装置
CN116074248A (zh) * 2021-11-02 2023-05-05 华为技术有限公司 报文处理方法及装置、通信系统
CN114422469B (zh) * 2022-01-25 2023-10-24 北京天维信通科技有限公司 IPv4/IPv6流量智能调度方法、装置和调度系统
CN114884917B (zh) * 2022-04-26 2023-07-28 北京华信傲天网络技术有限公司 一种地址解析协议报文的控制系统及方法
CN115118700B (zh) * 2022-06-27 2024-03-15 北京天融信网络安全技术有限公司 一种通信方法及通信系统
CN115412531A (zh) * 2022-08-31 2022-11-29 深圳市创维软件有限公司 网络查询方法、装置、设备及存储介质
CN115801731B (zh) * 2023-02-08 2023-06-23 天翼云科技有限公司 网络报文的处理方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103109517A (zh) * 2012-09-28 2013-05-15 华为技术有限公司 一种双栈终端访问服务器的方法、终端和系统
CN103957152A (zh) * 2014-04-22 2014-07-30 广州杰赛科技股份有限公司 IPv4与IPv6网络通信方法及NAT-PT网关
US20180097729A1 (en) * 2016-10-03 2018-04-05 Guavus, Inc. Detecting tethering in networks

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004254203A (ja) * 2003-02-21 2004-09-09 Matsushita Electric Ind Co Ltd ゲートウェイ装置
US7529852B2 (en) * 2004-05-17 2009-05-05 Cisco Technology, Inc. Method and apparatus for handling IPv4 DNS PTR queries across IPv4 and IPv6 networks
CN100518378C (zh) * 2007-03-05 2009-07-22 中山大学 一种实现移动节点从IPv6网络切换到IPv4网络的通信方法
CN101119382A (zh) * 2007-09-06 2008-02-06 中兴通讯股份有限公司 IPv4网络与IPv6网络互相通信的方法及通信网元系统
US20120259998A1 (en) * 2011-04-11 2012-10-11 Matthew Kaufman System and method for translating network addresses
US9843554B2 (en) * 2012-02-15 2017-12-12 F5 Networks, Inc. Methods for dynamic DNS implementation and systems thereof
JP5889955B2 (ja) * 2014-05-13 2016-03-22 西日本電信電話株式会社 中継装置及びプログラム
CN105306607A (zh) * 2014-05-28 2016-02-03 无锡韩光电器有限公司 一种域名查询方法及系统
CN105227687B (zh) * 2014-06-20 2019-05-03 中国电信股份有限公司 IPv4用户访问IPv6资源的通信方法与系统
CN110225150B (zh) * 2019-06-27 2020-09-15 中星科源(北京)信息技术有限公司 不同网络协议间的通信方法、系统和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103109517A (zh) * 2012-09-28 2013-05-15 华为技术有限公司 一种双栈终端访问服务器的方法、终端和系统
CN103957152A (zh) * 2014-04-22 2014-07-30 广州杰赛科技股份有限公司 IPv4与IPv6网络通信方法及NAT-PT网关
US20180097729A1 (en) * 2016-10-03 2018-04-05 Guavus, Inc. Detecting tethering in networks

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738866A (zh) * 2020-12-31 2021-04-30 百果园技术(新加坡)有限公司 一种终端接入方法、装置、设备及介质
CN112738866B (zh) * 2020-12-31 2024-04-30 百果园技术(新加坡)有限公司 一种终端接入方法、装置、设备及介质
CN113938459A (zh) * 2021-09-06 2022-01-14 锐捷网络股份有限公司 一种IPv6配置方法及装置
CN114268605A (zh) * 2021-12-16 2022-04-01 云盾智慧安全科技有限公司 一种智能dns实现方法、装置及计算机存储介质
CN114268605B (zh) * 2021-12-16 2023-11-24 云盾智慧安全科技有限公司 一种智能dns实现方法、装置及计算机存储介质
CN114268604A (zh) * 2021-12-21 2022-04-01 中国电信股份有限公司 访问服务的提供方法和系统
CN114268604B (zh) * 2021-12-21 2024-03-22 中国电信股份有限公司 访问服务的提供方法和系统
CN115037551A (zh) * 2022-06-29 2022-09-09 北京奇艺世纪科技有限公司 连接权限控制方法、装置、电子设备及存储介质
CN115037551B (zh) * 2022-06-29 2024-04-26 北京奇艺世纪科技有限公司 连接权限控制方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
JP7478820B2 (ja) 2024-05-07
CN110784562A (zh) 2020-02-11
EP4033729A1 (en) 2022-07-27
JP2022551147A (ja) 2022-12-07
EP4033729B1 (en) 2024-03-06
CN110784562B (zh) 2021-10-01
EP4033729A4 (en) 2022-10-19

Similar Documents

Publication Publication Date Title
WO2021078281A1 (zh) 报文转发及域名地址查询
US11425037B2 (en) Stateless protocol translation
US8769057B1 (en) Employing a hierarchy of servers to resolve fractional IP addresses
JP5551247B2 (ja) マルチｎａｔ６４環境のための方法及びホストノード
CN113162857B (zh) 按需获取路由的方法及网关
TW200924462A (en) System and method for connection of hosts behind NATs
CN110933156A (zh) 一种域名解析的方法及装置
WO2016155796A1 (en) Hybrid access dns optimization for multi-source download
WO2020181735A1 (zh) 一种提供网络地址转换nat服务的方法及控制器
CN110225150B (zh) 不同网络协议间的通信方法、系统和存储介质
CN115022283A (zh) 一种支持域名解析的可编程交换机以及网络报文处理方法
EP2719118B1 (en) Routing by resolution
CN110677512B (zh) 一种地址解析方法及装置
CN107040616B (zh) Tcp/dn/ip网络兼容tcp/ip网络的转换方法及报文收发方法
CN105939398B (zh) 一种IPv6过渡方法及装置
US20180367452A1 (en) Information centric networking over multi-access network interfaces
CN115225606A (zh) 一种容器云平台的跨网络协议的域名访问方法和系统
CN105306607A (zh) 一种域名查询方法及系统
WO2021088357A1 (zh) 一种用于生成转发信息的方法、装置和系统
US20240214345A1 (en) Message Forwarding and Domain Name Address Querying
CN114268604B (zh) 访问服务的提供方法和系统
CN116760796A (zh) Dns64和nat64的配置方法及装置
CN115428415A (zh) 使用可变长度地址在分层网络架构中转发报文的系统和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20879262

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022521052

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020879262

Country of ref document: EP

Effective date: 20220422