CN111416885A - Outer chain rewriting distributed system with fixed-length domain name - Google Patents

Outer chain rewriting distributed system with fixed-length domain name Download PDF

Info

Publication number
CN111416885A
CN111416885A CN202010203446.XA CN202010203446A CN111416885A CN 111416885 A CN111416885 A CN 111416885A CN 202010203446 A CN202010203446 A CN 202010203446A CN 111416885 A CN111416885 A CN 111416885A
Authority
CN
China
Prior art keywords
ipv6
domain name
resource
rewritten
skylight
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010203446.XA
Other languages
Chinese (zh)
Other versions
CN111416885B (en
Inventor
郭文强
陈其谋
林志远
谢玉燕
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujian Wutongyilian Network Technology Co ltd
Original Assignee
Fujian Wutongyilian Network Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujian Wutongyilian Network Technology Co ltd filed Critical Fujian Wutongyilian Network Technology Co ltd
Priority to CN202010203446.XA priority Critical patent/CN111416885B/en
Publication of CN111416885A publication Critical patent/CN111416885A/en
Application granted granted Critical
Publication of CN111416885B publication Critical patent/CN111416885B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • 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/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/301—Name conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The outer chain rewriting distributed system provided by the invention has the advantages that a DNS server generates a DNS response containing an IPV6 address and returns the DNS response to an end user when detecting that the end user supports IPV6, a CDN edge cache device returns cached page resources returned by an IPV6 skylight reconstruction device to the end user according to an HTTP request of the end user, the IPV6 skylight reconstruction device performs outer chain rewriting of a fixed-length domain name on outer chain resources embedded in response content returned by a resource request initiated by the CDN edge cache device and returns the rewritten response to the CDN edge cache device, the outer chain resources UR L are restored and corresponding page resources are obtained and returned to the CDN edge cache device when detecting that the resource request is rewritten outer chain resources UR L, the problem that domain names are too long after rewriting in the prior art is solved, and the outer chain resources request after rewriting can be correctly restored to be original domain names when the domain name server receives the rewritten outer chain resource request, and the system is suitable for a.

Description

Outer chain rewriting distributed system with fixed-length domain name
Technical Field
The invention belongs to the technical field of solving skylight problems by source station IPV6 transformation, and particularly relates to an outer chain rewriting distributed system with a fixed-length domain name.
Background
The shortage of IPV4 address space has hindered and limited the development of the internet, and therefore, the substitution of IPV6 for IPV4 has been a necessary trend. In the process of modifying the source station IPV6, if only simple conversion from an IPV4 address to an IPV6 address is performed, if a source station using out-link resources by a website does not support the IPV6, the out-link resources cannot be accessed under the environment of pure IPV6, and a skylight problem is caused. Therefore, some existing schemes for upgrading and transforming the IPV6 of the source station can rewrite the external chain of the third party of the website, and solve the skylight problem.
The conventional rewriting method generally includes:
1. changing the character of the existing domain name into the character, and then splicing the general domain name supporting the IPV6 domain name resolution, so that the rewritten domain name can support the IPV6 resolution. But because the DNS namesystem has a limit on the length of the domain name: the limitation of the domain name length at each stage is 63 characters, and the total domain name length cannot exceed 253 characters, so the rewriting mode of the method easily causes the domain name length to exceed the limitation, the DNS analysis cannot be carried out, and the normal access cannot be carried out.
2. In practice, however, many js scripts use the logic of the URI or query string, so that the modification mode can cause the content of the URI or query string to change, cause js execution abnormity and easily cause page errors.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides an outer-link rewriting distributed system of a domain name with a fixed length, which solves the problem that the rewritten domain name is too long in the prior art, and meanwhile, when a rewritten outer-link resource request is received, the original domain name can be correctly restored, and the system is suitable for deploying and deploying systems in different parts.
An outer-link rewrite distributed system for fixed-length domain names, comprising:
at least one DNS server: the terminal user DNS request processing module is used for receiving a DNS request initiated by the terminal user, and generating a DNS response containing an IPV6 address to return to the terminal user when the DNS request judges that the terminal user supports IPV 6;
at least one CDN edge cache device: the system comprises a server and a server, wherein the server is used for receiving an HTTP request initiated by a terminal user, returning cached page resources or page resources returned by an IPV6 skylight transformation device to the terminal user according to the HTTP request, and allowing the terminal user to access the page resources;
the system comprises at least one IPV6 skylight improvement device, a CDN edge cache device and a CDN edge cache device, wherein the IPV6 skylight improvement device is used for receiving a resource request from the CDN edge cache device, carrying out outer chain rewriting of a fixed-length domain name on outer chain resources UR L contained in response content when detecting that the response content corresponding to the resource request needs to be rewritten, returning the rewritten response content to the CDN edge cache device, restoring the outer chain resources UR L when detecting that the resource request is the rewritten outer chain resources UR L, and acquiring page resources corresponding to the restored original UR L and returning the page resources to the CDN edge cache device.
Preferably, the CDN edge cache device is specifically configured to:
receiving an HTTP request initiated by a terminal user;
when the page resources corresponding to the HTTP request are cached in the CDN edge cache device, generating an HTTP response containing the page resources and returning the HTTP response to the terminal user;
and when the page resources corresponding to the HTTP request do not exist in the CDN edge cache device, generating a resource request, sending the resource request to the IPV6 skylight reconstruction device, generating an HTTP response according to the page resources returned by the IPV6 skylight reconstruction device, and returning the HTTP response to the terminal user.
Preferably, the CDN edge caching device is further configured to:
and caching page resources returned by the IPV6 skylight transformation device.
Preferably, the IPV6 skylight retrofitting device is specifically configured to:
when detecting that the response content corresponding to the resource request contains the out-link resource UR L, considering that the response content needs to be rewritten, performing out-link rewriting of the fixed-length domain name on the out-link resource UR L contained in the response content, and returning the rewritten response content to the CDN edge cache device;
when the resource request is detected to be the rewritten external link resource UR L, restoring the external link resource UR L to obtain an original UR L, acquiring the page resource from the external link source station according to the original UR L, and returning the page resource to the CDN edge cache device.
Preferably, the format of the rewritten external link resource UR L is encrypted character-rewritten device ID-safety check string-universal domain name;
the encrypted character is 32 bits, the rewriting device ID is 8 bits, the safety check string is 4 bits, and the universal domain name supports IPV6 resolution.
Preferably, the IPV6 skylight retrofitting device is specifically configured to:
and after the outer chain rewriting of the fixed-length domain name is finished for the outer chain resource UR L, adding the corresponding relation among the encrypted character, the client domain name and the outer chain domain name in the outer chain resource UR L obtained after rewriting into a domain name mapping table, and persisting to a disk.
Preferably, the IPV6 skylight retrofitting device is specifically configured to:
and when the resource request is detected to be the rewritten external link resource UR L, searching the domain name mapping table to obtain an external link domain name corresponding to the external link resource UR L in the resource request in the domain name mapping table, and restoring to obtain the original UR L according to the external link domain name.
Preferably, the IPV6 skylight retrofit device is further configured to:
and when the rewritten out-link resource UR L is obtained, performing security check on the security check string in the rewritten out-link resource UR L, and when the check fails, closing the connection with the end user and rejecting the response.
According to the technical scheme, the outer chain rewriting distributed system of the fixed-length domain name provided by the invention has the following advantages:
1. the problem that the rewritten domain name is too long in the conventional rewriting method is avoided.
2. When receiving the rewritten external link resource request, the method can correctly restore the external link resource request to the original domain name and correctly acquire the response of the external link resource.
3. The method is suitable for an IPV6 CDN sub-deployment system, and can be used for rewriting the outer chain resources to solve the skylight problem of source station IPV6 modification while improving the system availability by using the sub-deployment system.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
Fig. 1 is a block diagram of an out-link rewrite distributed system according to an embodiment of the present invention.
Fig. 2 is a flowchart of an operation method of a CDN edge cache device according to an embodiment of the present invention.
FIG. 3 is a flowchart illustrating a method for operating a sunroof retrofitting device of IPV6 according to an embodiment of the present invention.
Fig. 4 is a flowchart of the IPV6 skylight renovation device restoring UR L through the domain name mapping table in the third embodiment of the present invention.
Fig. 5 is a flowchart of the security verification of the IPV6 skylight retrofit device in the third embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are only for illustrating the technical solutions of the present invention more clearly, and therefore are only examples, and the protection scope of the present invention is not limited thereby. It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which the invention pertains.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
The first embodiment is as follows:
an outer-link rewrite distribution system for fixed-length domain names, see fig. 1, comprising:
at least one DNS server: the terminal user DNS request processing module is used for receiving a DNS request initiated by the terminal user, and generating a DNS response containing an IPV6 address to return to the terminal user when the DNS request judges that the terminal user supports IPV 6;
at least one CDN edge cache device: the system comprises a server and a server, wherein the server is used for receiving an HTTP request initiated by a terminal user, returning cached page resources or page resources returned by an IPV6 skylight transformation device to the terminal user according to the HTTP request, and allowing the terminal user to access the page resources; referring to fig. 2, the CDN edge cache device is specifically configured to:
receiving an HTTP request initiated by a terminal user;
when the page resources corresponding to the HTTP request are cached in the CDN edge cache device, generating an HTTP response containing the page resources and returning the HTTP response to the terminal user;
and when the page resources corresponding to the HTTP request do not exist in the CDN edge cache device, generating a resource request, sending the resource request to the IPV6 skylight reconstruction device, generating an HTTP response according to the page resources returned by the IPV6 skylight reconstruction device, and returning the HTTP response to the terminal user.
Specifically, after receiving the HTTP response, the end user parses the HTTP response, and accesses the page resource included in the HTTP response, where the page resource includes the rewritten out-link resource UR L.
At least one IPV6 skylight reforming device, which is used for receiving a resource request from a CDN edge cache device, rewriting outer links with fixed-length domain names for outer link resources UR L contained in response content when detecting that the response content corresponding to the resource request needs to be rewritten, and returning the rewritten response content to the CDN edge cache device, and restoring the outer link resources UR L and acquiring page resources corresponding to original UR L after restoration and returning the page resources to the CDN edge cache device when detecting that the resource request is rewritten outer link resources UR L, referring to FIG. 3, the IPV6 skylight reforming device is specifically used for:
when detecting that the response content corresponding to the resource request contains the out-link resource UR L, considering that the response content needs to be rewritten, performing out-link rewriting of the fixed-length domain name on the out-link resource UR L contained in the response content, and returning the rewritten response content to the CDN edge cache device;
when the resource request is detected to be the rewritten external link resource UR L, restoring the external link resource UR L to obtain an original UR L, acquiring the page resource from the external link source station according to the original UR L, and returning the page resource to the CDN edge cache device.
Specifically, the IPV6 skylight retrofit device is logically separate from the CDN edge servers, but may physically share servers. Referring to fig. 1, assuming that the website visited by the end user relates to the out-link resource, taking the lowermost MAC end user (assumed to be IPV6 user) in fig. 1 as an example, the rewriting method of the system includes the following steps:
step 2.1: a terminal user initiates a DNS request to a DNS server, and the DNS server carries out DNS analysis on the DNS request;
step 2.2: when the DNS server judges that the terminal user supports the IPV6, the DNS server responds to the IPV6 address;
step 2.3: a terminal user initiates an HTTP request to the CDN edge cache device 1 to obtain page resources;
step 2.4: and if the CDN edge cache device 1 has cached page resources, responding to the user. In FIG. 1, the DNS request and HTTP request issued by the mobile phone or the computer refer to steps 1.1-1.4, 3.1-3.4.
Step 1: if the CDN edge cache device 1 does not have cached page resources, requesting resources from the IPV6 skylight reconstruction device 1, returning the IPV6 skylight reconstruction device 1 to the source station to obtain the resources, and determining whether response content corresponding to the resources needs to rewrite the outer link, and if so, performing outer link rewriting on the response content corresponding to the resources;
step 2: the IPV6 skylight reconstruction device 1 returns the returned resources and/or the rewritten response content to the CDN edge cache device 1;
step 2.4: the CDN edge cache device 1 responds the returned page request to the end user.
The method comprises the following steps of assuming that when receiving the condition that the terminal user accesses the external link resource which is rewritten last time:
step 2.5: a terminal user initiates an HTTP request to the CDN edge cache device 2 to obtain page resources;
step 2.10: and if the CDN edge cache device 2 has cached page resources, responding to the user.
Step 2.6: if the CDN edge cache device 2 does not have cached page resources, the CDN edge cache device requests resources from the IPV6 skylight reconstruction device 3;
step 2.7, judging that the external link resource UR L in the resource request is rewritten by the IPV6 skylight reconstruction device 3 according to the rewriting rule by the IPV6 skylight reconstruction device 3, restoring the original UR L according to the rewriting rule, and sending the request to an external link source station by using the original UR L;
step 2.8: the external link source station obtains a response and returns the response to the IPV6 skylight improvement device 3;
step 2.9: the IPV6 skylight retrofit device 3 responds to the CDN edge server 2.
Step 2.10: the CDN edge cache 2 responds to the user.
The outer chain rewriting distributed system of the domain name with fixed length has the following advantages:
1. the problem that the rewritten domain name is too long in the conventional rewriting method is avoided.
2. When receiving the rewritten external link resource request, the method can correctly restore the external link resource request to the original domain name and correctly acquire the response of the external link resource.
3. The method is suitable for an IPV6 CDN sub-deployment system, and can be used for rewriting the outer chain resources to solve the skylight problem of source station IPV6 modification while improving the system availability by using the sub-deployment system.
Preferably, the CDN edge caching device is further configured to:
and caching page resources returned by the IPV6 skylight transformation device.
Specifically, the CDN edge caching device receives the page resource returned by the IPV6 skylight modified device, and stores the page resource to a disk if the page resource can be cached. Therefore, when the resource request of the terminal user reaches the CDN edge cache device, the CDN edge cache device may directly return the cached page resource.
Example two:
the second embodiment adds a specific rewriting method on the basis of the first embodiment:
the format of the rewritten external link resource UR L is encrypted character, rewritten device ID, safety check string and general domain name;
the encrypted character is 32 bits, the rewriting device ID is 8 bits, the safety check string is 4 bits, and the universal domain name supports IPV6 resolution.
Specifically, the format of the rewritten foreign chain resource UR L is 32-bit encrypted character-8-bit rewriting device ID-4-bit safety check string, and the generic domain name supporting IPV6 resolution, for example, 4076ac4fcacc1a1cc1ebb6c8c5706b06-6f067506-x94o.
Because the domain names obtained by the rewriting method are all the same in length, the situation that the domain names are overlong after being rewritten in the conventional rewriting method does not occur. The 32-bit encrypted character includes an MD5 value and a hash value, and may be a fixed-length character string calculated by using an MD5 algorithm or other algorithms, for example, the out-link domain name is www.ipv4.com, the client domain name is www.custom.com, and the 32-bit hash value of the rewritten domain name is 4076ac4fcacc1a1cc1ebb6c8c5706b 06. The 8-bit rewriting device ID can be obtained by 16-system conversion of the IPV6 skylight renovation device IP, and is mainly used for distinguishing the rewritten IPV6 skylight renovation device, or can be obtained according to a certain rule, as long as the CDN edge cache device can find the IPV6 skylight renovation device. For example, the IPV6 skylight retrofit device IP is: 111.6.171.6, an 8-bit overwriting device ID can be represented using 6f 067506. The 4-bit security check string may be simply configured in the client domain name or otherwise calculated.
For the sake of brief description, the embodiments of the present invention do not refer to the corresponding contents in the foregoing embodiments of the present invention.
Example three:
third embodiment on the basis of the above embodiments, a method for restoring the original UR L through the domain name mapping table is added.
The IPV6 skylight reconstruction device is particularly used for:
and after the outer chain rewriting of the fixed-length domain name is finished for the outer chain resource UR L, adding the corresponding relation among the encrypted character, the client domain name and the outer chain domain name in the outer chain resource UR L obtained after rewriting into a domain name mapping table, and persisting to a disk.
Specifically, after the outer link resource UR L is rewritten, the correspondence between the encrypted characters, the client domain name and the outer link domain name in the outer link resource UR L obtained after rewriting may be persisted to a disk, including persisted through text or a database, etc., to obtain a domain name mapping table, for example, after the outer link resource UR L is rewritten in the above example, the IPV6 skylight reforming apparatus stores a record 4076ac4fcacc1a1cc1ebb6c8c5706b06 www.ipv4.com www.custom.com.
Referring to fig. 4, the IPV6 skylight retrofit device is specifically configured to:
and when the resource request is detected to be the rewritten external link resource UR L, searching the domain name mapping table to obtain an external link domain name corresponding to the external link resource UR L in the resource request in the domain name mapping table, and restoring to obtain the original UR L according to the external link domain name.
Specifically, when the IPV6 skylight reconstruction device stores the rewrite record in the domain name mapping table, if the rewritten foreign chain resource UR L is received, the corresponding foreign chain domain name can be found according to the 32-bit encrypted character in the rewritten foreign chain resource UR L, and the original UR L is recovered, for example, the rewritten foreign chain resource UR L is 4076ac4fcacc1a1cc1ebb6c8c5706b06-6f 067506-x94o.wanwuyuunlian.com, the IPV6 skylight reconstruction device reads the encrypted character 4076ac4fcacc1a1cc1ebb6c8c5706b06, and then searches the domain name mapping table, and finds that the domain name of the original UR L is www.ipv4.com.
Referring to fig. 5, the IPV6 skylight retrofit device is also configured to:
and when the rewritten out-link resource UR L is obtained, performing security check on the security check string in the rewritten out-link resource UR L, and when the check fails, closing the connection with the end user and rejecting the response.
Specifically, when a user accesses a rewritten resource request to the IPV6 skylight reconstruction device, the IPV6 skylight reconstruction device needs to perform security judgment on an external link, determine whether the external link is rewritten by the IPV6 skylight reconstruction device, and if not, indicate that the external link is an illegal request, close the connection or reject the response.
For the sake of brief description, the embodiments of the present invention do not refer to the corresponding contents in the foregoing embodiments of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.

Claims (8)

1. An outer-link rewrite distributed system for fixed-length domain names, comprising:
at least one DNS server: the terminal user DNS request processing module is used for receiving a DNS request initiated by the terminal user, and generating a DNS response containing an IPV6 address to return to the terminal user when the DNS request judges that the terminal user supports IPV 6;
at least one CDN edge cache device: the system comprises a server and a server, wherein the server is used for receiving an HTTP request initiated by a terminal user, returning cached page resources or page resources returned by an IPV6 skylight transformation device to the terminal user according to the HTTP request, and allowing the terminal user to access the page resources;
the system comprises at least one IPV6 skylight improvement device, a CDN edge cache device and a CDN edge cache device, wherein the IPV6 skylight improvement device is used for receiving a resource request from the CDN edge cache device, carrying out outer chain rewriting of a fixed-length domain name on outer chain resources UR L contained in response content when detecting that the response content corresponding to the resource request needs to be rewritten, returning the rewritten response content to the CDN edge cache device, restoring the outer chain resources UR L when detecting that the resource request is the rewritten outer chain resources UR L, and acquiring page resources corresponding to the restored original UR L and returning the page resources to the CDN edge cache device.
2. The system according to claim 1, wherein the CDN edge cache device is specifically configured to:
receiving an HTTP request initiated by a terminal user;
when the page resources corresponding to the HTTP request are cached in the CDN edge cache device, generating an HTTP response containing the page resources and returning the HTTP response to the terminal user;
and when the page resources corresponding to the HTTP request do not exist in the CDN edge cache device, generating a resource request, sending the resource request to the IPV6 skylight reconstruction device, generating an HTTP response according to the page resources returned by the IPV6 skylight reconstruction device, and returning the HTTP response to the terminal user.
3. The system of claim 2, wherein the CDN edge cache is further configured to:
and caching page resources returned by the IPV6 skylight transformation device.
4. The outer-link rewrite distribution system for fixed-length domain names of claim 1, wherein the IPV6 skylight-modifying apparatus is specifically configured to:
when detecting that the response content corresponding to the resource request contains the out-link resource UR L, considering that the response content needs to be rewritten, performing out-link rewriting of the fixed-length domain name on the out-link resource UR L contained in the response content, and returning the rewritten response content to the CDN edge cache device;
when the resource request is detected to be the rewritten external link resource UR L, restoring the external link resource UR L to obtain an original UR L, acquiring the page resource from the external link source station according to the original UR L, and returning the page resource to the CDN edge cache device.
5. The fixed length domain name out-chaining rewriting distribution system of claim 4,
the format of the rewritten external link resource UR L is encrypted character, rewritten device ID, safety check string and general domain name;
the encrypted character is 32 bits, the rewriting device ID is 8 bits, the safety check string is 4 bits, and the universal domain name supports IPV6 resolution.
6. The outer-link rewrite distribution system for fixed-length domain names of claim 5, wherein the IPV6 skylight-modifying device is specifically configured to:
and after the outer chain rewriting of the fixed-length domain name is finished for the outer chain resource UR L, adding the corresponding relation among the encrypted character, the client domain name and the outer chain domain name in the outer chain resource UR L obtained after rewriting into a domain name mapping table, and persisting to a disk.
7. The outer-link rewrite distribution system for fixed-length domain names of claim 6, wherein the IPV6 skylight-modifying apparatus is specifically configured to:
and when the resource request is detected to be the rewritten external link resource UR L, searching the domain name mapping table to obtain an external link domain name corresponding to the external link resource UR L in the resource request in the domain name mapping table, and restoring to obtain the original UR L according to the external link domain name.
8. The fixed-length domain name outer-link rewrite distribution system of claim 5, wherein the IPV6 skylight-modifying apparatus is further configured to:
and when the rewritten out-link resource UR L is obtained, performing security check on the security check string in the rewritten out-link resource UR L, and when the check fails, closing the connection with the end user and rejecting the response.
CN202010203446.XA 2020-03-20 2020-03-20 Outer chain rewriting distributed system with fixed-length domain name Active CN111416885B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010203446.XA CN111416885B (en) 2020-03-20 2020-03-20 Outer chain rewriting distributed system with fixed-length domain name

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010203446.XA CN111416885B (en) 2020-03-20 2020-03-20 Outer chain rewriting distributed system with fixed-length domain name

Publications (2)

Publication Number Publication Date
CN111416885A true CN111416885A (en) 2020-07-14
CN111416885B CN111416885B (en) 2021-04-06

Family

ID=71494503

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010203446.XA Active CN111416885B (en) 2020-03-20 2020-03-20 Outer chain rewriting distributed system with fixed-length domain name

Country Status (1)

Country Link
CN (1) CN111416885B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112398963A (en) * 2020-10-13 2021-02-23 易讯科技股份有限公司 Method for realizing intelligent recognition and flexible translation of IPv4 external link
CN112600950A (en) * 2020-12-09 2021-04-02 福建万物易联网络科技有限公司 Outer chain rewriting method and system of short crossbar format
CN112600949A (en) * 2020-12-09 2021-04-02 福建万物易联网络科技有限公司 Outer chain rewriting method and system for reserving original domain name
CN112702425A (en) * 2020-12-22 2021-04-23 杭州易安联科技有限公司 WEB application access agent method, device and system based on domain name extensive resolution

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217576A (en) * 2008-01-18 2008-07-09 厦门纳网科技有限公司 A dynamic domain name analysis system and the corresponding dynamic analysis method
WO2015095311A1 (en) * 2013-12-21 2015-06-25 Akamai Technologies, Inc. Countering security threats with domain name system
WO2015120750A1 (en) * 2014-02-17 2015-08-20 中国科学院计算机网络信息中心 Dns-based ipv6 and ipv4 interworking method
WO2017173766A1 (en) * 2016-04-08 2017-10-12 网宿科技股份有限公司 Domain name parsing acceleration method, system and apparatus
CN109543121A (en) * 2018-11-09 2019-03-29 深圳万物云联科技有限公司 A kind of exterior chain url resource transfer method and device
CN109561078A (en) * 2018-11-09 2019-04-02 深圳万物云联科技有限公司 A kind of exterior chain url resource transfer method and device
CN110392130A (en) * 2019-08-23 2019-10-29 北京天融信网络安全技术有限公司 Network-based information processing method, electronic equipment and network system

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217576A (en) * 2008-01-18 2008-07-09 厦门纳网科技有限公司 A dynamic domain name analysis system and the corresponding dynamic analysis method
WO2015095311A1 (en) * 2013-12-21 2015-06-25 Akamai Technologies, Inc. Countering security threats with domain name system
WO2015120750A1 (en) * 2014-02-17 2015-08-20 中国科学院计算机网络信息中心 Dns-based ipv6 and ipv4 interworking method
WO2017173766A1 (en) * 2016-04-08 2017-10-12 网宿科技股份有限公司 Domain name parsing acceleration method, system and apparatus
CN109543121A (en) * 2018-11-09 2019-03-29 深圳万物云联科技有限公司 A kind of exterior chain url resource transfer method and device
CN109561078A (en) * 2018-11-09 2019-04-02 深圳万物云联科技有限公司 A kind of exterior chain url resource transfer method and device
CN110392130A (en) * 2019-08-23 2019-10-29 北京天融信网络安全技术有限公司 Network-based information processing method, electronic equipment and network system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
付明腾: "一种基于SPACE6的政府网站群IPv6改造方案", 《电脑知识与技术》 *
李伟波等: "通过睿哲6aaS实现数据中心应用服务IPv6快速升级", 《科研信息化技术与应用》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112398963A (en) * 2020-10-13 2021-02-23 易讯科技股份有限公司 Method for realizing intelligent recognition and flexible translation of IPv4 external link
CN112600950A (en) * 2020-12-09 2021-04-02 福建万物易联网络科技有限公司 Outer chain rewriting method and system of short crossbar format
CN112600949A (en) * 2020-12-09 2021-04-02 福建万物易联网络科技有限公司 Outer chain rewriting method and system for reserving original domain name
CN112702425A (en) * 2020-12-22 2021-04-23 杭州易安联科技有限公司 WEB application access agent method, device and system based on domain name extensive resolution
CN112702425B (en) * 2020-12-22 2022-12-23 杭州易安联科技有限公司 WEB application access proxy method, device and storage medium based on domain name extensive resolution

Also Published As

Publication number Publication date
CN111416885B (en) 2021-04-06

Similar Documents

Publication Publication Date Title
CN111416885B (en) Outer chain rewriting distributed system with fixed-length domain name
US6983318B2 (en) Cache management method and system for storing dynamic contents
US7480761B2 (en) System and methods for an overlay disk and cache using portable flash memory
CN111416862B (en) CDN platform access method and system based on IPV6IPV4
US6202087B1 (en) Replacement of error messages with non-error messages
US8806133B2 (en) Protection against cache poisoning
US20020078087A1 (en) Content indicator for accelerated detection of a changed web page
CN109413163B (en) Service access method and device
WO2007115288A2 (en) Method and system for providing improved url mangling performance using fast re-write
US7949724B1 (en) Determining attention data using DNS information
WO2012130009A1 (en) Method and device for module repair in software
JP2006519534A (en) Method and apparatus for local IP address translation
KR100385083B1 (en) Computer network system on internet using realname and networking method thereof
US8271829B2 (en) Network connection device and method for detecting network errors
US20230089710A1 (en) Data request server code and configuration file deployment
CN103678295B (en) Method and device for providing files for user
US8694659B1 (en) Systems and methods for enhancing domain-name-server responses
US20060242105A1 (en) Pack URI scheme to identify and reference parts of a package
US20210014298A1 (en) Message display method and device, and storage medium
US20100082690A1 (en) System And Method For Recording Files Of Data
CN111782244A (en) Configuration file updating method and device, computer equipment and storage medium
US20060224720A1 (en) Method, computer program product, and system for mapping users to different application versions
WO2020178340A1 (en) Distributed data processing
JPH1040180A (en) Information repeating device
CN112398852B (en) Message detection method, device, storage medium and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant