Domain name resolution method, server, terminal and system

Abstract

The invention discloses a domain name resolution method, a server, a terminal and a system and belongs to the technical field of internet. The method includes the following steps: a domain name resolution request, which carries a domain name which needs to be resolved and IP information of the terminal, sent by the terminal is received; an IP address attribute of the terminal is determined; an IP address which matches the domain name which needs to be resolved and the IP address attribute of the terminal; and according to the IP address which matches the IP address attribute of the terminal, a domain name resolution result is obtained and a domain name resolution result is returned to the terminal. Through reception of the domain name resolution request, which carries the IP information of the terminal, sent by the terminal, and according to the IP information of the terminal, the IP address attribute of the terminal is determined and according to the domain name which needs to be resolved and the IP address attribute of the terminal, the domain name resolution result is obtained. The domain name resolution method is simple and the domain name resolution efficiency can be improved so that the terminal is enabled to access websites rapidly and nearest access is arranged for the terminal according to the IP address attribute of the terminal so that global traffic configuration and refined scheduling of the terminal can be realized.

Description

technical field [0001] The invention relates to the technical field of the Internet, in particular to a domain name resolution method, server, terminal and system. Background technique [0002] Domain name resolution is the process of obtaining the IP (Internet Protocol, Internet Protocol) address of the web space pointed to by the domain name, so that users can easily access the website through the domain name. Usually, when resolving the domain name, the obtained resolving result is an IP address corresponding to the domain name that matches the attribute of the IP address of the terminal. For example, the analysis result is an IP address that matches the geographic location and network attribution of the IP address of the terminal. By resolving the domain name to an IP address that matches the attribute of the IP address of the terminal, an ICP (Internet Content Provider, Internet Content Service Provider) can implement global traffic scheduling and user access nearby. ...

AI Technical Summary

Problems solved by technology

At this time, when the recursive DNS server determines that the ICP authoritative DNS server to which the domain name to be resolved belongs is not in the network of the operator, the recursive DNS server needs to replace the source IP address of the egress through NAT (Network Address Translation) It is the address of the operator of the ICP authoritative DNS server to which the domain name belongs, and sends a domain name resolution request to the ICP authoritative DNS server, so that the ICP authoritative DNS server mistakenly identifies the source of the domain name resolution request, thus returning an unexpected error message to the recursive DNS server The result of domain name resolution causes the recursive DNS server to return the wrong IP address to the terminal, which not only easily leads to the slow or even abnormal service of terminal access to ICP, but also makes ICP fail to realize user access scheduling traffic

[0009] For the second method above: Initiating domain name resolution through a third-party recursive DNS server can avoid the hijacking of domain name requests and the failure of user traffic scheduling caused by the first method, but it is difficult for mobile terminals to use third-party recursive DNS servers , so that the scope of application of the method of domain name resolution through the second method is limited

In addition, due to the insufficient coverage of the nearest recursive DNS servers that can be assigned by the third-party recursive DNS server, there may be situations where terminals in different provinces share recursive DNS servers, and due to the lack of coverage of the nearest recursive DNS servers designated by the third-party recursive DNS server The IP address changes frequently

Therefore, the ICP authoritative DNS server cannot correctly identify the IP attributes of the nearest recursive DNS server, making ICP unable to control the terminal's nearby access, which leads to slow user access and increased cross-network and cross-province traffic of operators

Images