CDN-based domain name parse service model

Abstract

In order to solve various performance and security problems like querying delay, update delay, and vulnerability to DoS attack and the like in the existing domain name parse system, the invention brings forward a novel domain name parse service model that is capable of realize incremental deployment, is compatible with the existing DNS, and has the good performance. To be specific, the invention relates to a content-distribution-network (CDN)-based domain name parse service model. The core concept of the model design is as follows: CDN network node server systems that are distributed widely form a system. On the basis of the content distribution and storage mechanism of the CDN network, authoritative DNS records all domain names are distributed at the node servers that are distributed widely by a pushing way. The DNS records are distributed by using the CDN architecture. The authoritative DNS records are distributed to all node servers; all node servers replace a domain name parse system and a domain name server in the existing DNS architecture to response to a domain name parse request of a user and provide a domain name parse service; and the query result is returned to the user directly by a network node server.

Description

technical field [0001] The invention relates to Internet technology, in particular to a domain name resolution service model based on content distribution networks (Content Distribution Networks). Background technique [0002] The domain name resolution system (DomainName System) is an important Internet infrastructure, which resolves the network domain name (such as www.example.com) that is easy for users to identify into the corresponding IP address (such as 10.0.0.1) that can be recognized by the computer. Various Internet-based Web services, Email services, etc. may rely on DNS. The current DNS adopts a distributed hierarchical structure design, which is composed of a domain name resolver and a domain name server. When resolving a domain name, the user sends a domain name resolution request to the domain name resolver for resolution. If the DNS record of the request is stored in the cache of the domain name resolver, the domain name resolver immediately responds to the ...

AI Technical Summary

Problems solved by technology

In addition, due to factors such as server unreachability, data packet loss, and unresponsive domain name resolution requests, the average time required to resolve a domain name is relatively long

[0004] 2)DNS update delay

For the DNS records in the domain name resolver cache, when the DNS records on the domain name server are updated, the DNS records in the domain name resolver cache will not be updated in time, but wait until the TTL value of the domain name DNS record in the domain name resolver cache After the expiration, the domain name resolver accesses the corresponding domain name server to obtain the updated DNS record in a "pull" manner. Therefore, there is a delay in updating the DNS record. At this time, the DNS record in the domain name resolution cache is redundant information. At this time, when resolving the domain name, an exception may occur

[0005] 3) DNS is vulnerable to network failures and a

Images