CN113497811A

CN113497811A - Domain name system server distribution method and related equipment

Info

Publication number: CN113497811A
Application number: CN202010190740.1A
Authority: CN
Inventors: 张银叶; 何烨
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-03-18
Filing date: 2020-03-18
Publication date: 2021-10-12

Abstract

The embodiment of the application discloses a domain name system DNS server distribution method, which can be applied to the situation that a user device changes a DNS server after being on line. The method in the embodiment of the application comprises the following steps: the access server determines a first DNS server connected with the user equipment; the access server judges whether the first DNS server meets preset conditions or not; and if so, the access server sends the relevant information of the second DNS server to the user equipment, wherein the relevant information of the second DNS server is used for indicating the user equipment to be replaced from the first DNS server to the second DNS server. The problem that the speed of the user equipment for accessing the webpage is reduced due to the failure of the first DNS server and other reasons in the online process of the user equipment is solved.

Description

Domain name system server distribution method and related equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a domain name system server distribution method and related equipment.

Background

When the user equipment accesses a webpage, the user equipment performs domain name resolution through a Domain Name System (DNS) server to obtain an Internet Protocol (IP) address corresponding to the webpage, and then accesses the webpage according to the IP address, where the DNS server is allocated to the user equipment by a Broadband Remote Access Server (BRAS).

The related art indicates that, when the user equipment applies for online to the access server, the access server stores a corresponding relationship between the DNS server and the IP address of the user equipment, and the access server allocates a corresponding DNS server to the user equipment according to the corresponding relationship. Two DNS servers are typically allocated, one as primary and one as backup.

However, after the access server allocates the DNS server to the user equipment, when the user equipment is always online and the DNS server connected to the user equipment fails or is overloaded, the speed of accessing the web page by the user equipment may be slow, and even the user equipment may fail to access the web page.

Disclosure of Invention

The embodiment of the application provides a domain name system server distribution method and related equipment. The method and the device are used for solving the problem that the speed of the user equipment for accessing the webpage is reduced due to the failure of the first DNS server and other reasons in the online process of the user equipment.

A first aspect of an embodiment of the present application provides a method for assigning a server to a domain name system, where the method includes: the access server determines a first DNS server connected with the user equipment; the access server judges whether the first DNS server meets preset conditions or not; and if so, the access server sends the relevant information of the second DNS server to the user equipment, wherein the relevant information of the second DNS server is used for indicating the user equipment to be replaced from the first DNS server to the second DNS server.

In the embodiment of the application, after the access server determines the first DNS server connected with the user equipment, if the first DNS server connected with the user equipment meets the preset condition, the access server sends the related information of the second DNS server to the user equipment, so that the user equipment can replace the first DNS server with the second DNS server, and the problem that the speed of the user equipment for accessing the webpage is reduced due to the fault of the first DNS server and the like in the online process of the user equipment is solved.

Optionally, in a possible implementation manner of the first aspect, the step of: the access server sends the relevant information of the second DNS server to the user equipment, and the relevant information comprises the following steps: and the access server sends a target message to the user equipment, wherein the target message comprises the related information of the second DNS server.

Because a network manager does not generally have the authority to manage the user equipment, the embodiment of the application can inform the user equipment of replacing the DNS server by sending the target message to the user equipment through the access server.

Optionally, in a possible implementation manner of the first aspect, the target packet in the above step carries an option6 attribute.

In the possible implementation manner, a new target message is added, and the second DNS information is sent to the user equipment through the option6 attribute, so that web page operation delay caused by the fact that the user equipment cannot replace a failed DNS server after going online is avoided.

Optionally, in a possible implementation manner of the first aspect, the target packet in the foregoing step is a lease renewal response packet, and the lease renewal response packet carries an option6 attribute.

In this possible implementation manner, the second DNS information is sent to the user equipment by using the attribute of option6 carried by the existing lease renewal response packet, and the requirement on the user equipment is not high, that is, the lease renewal response packet is identified without identifying a new packet.

Optionally, in a possible implementation manner of the first aspect, the step further includes: and the access server distributes a first DNS server for the user equipment according to the load information of the plurality of DNS servers.

The possible implementation mode improves the realizability of the scheme.

Optionally, in a possible implementation manner of the first aspect, the step of: the access server determines whether the first DNS server meets a preset condition, which may specifically be: the access server judges whether the load value of the first DNS server is larger than a target threshold value.

In this possible implementation manner, whether to send the second DNS information is triggered by comparing the target threshold value with the load value, and the DNS server with smoother processing efficiency can be changed for the user equipment in time.

Optionally, in a possible implementation manner of the first aspect, the step of: the access server determines whether the first DNS server satisfies a preset condition, which may specifically be: the access server determines whether the first DNS server is down.

A second aspect of the embodiments of the present application provides a method for assigning a server to a domain name system, where the method includes: the user equipment is connected with a first DNS server; the user equipment receives the related information of the second DNS sent by the access server; the user equipment identifies the relevant information; and the user equipment is connected with the second DNS server according to the relevant information.

In the embodiment of the application, the user equipment feeds back the load information of the first DNS to the access server, receives the second DNS information, and replaces the first DNS server with the second DNS server, so that the problem that the speed of the user equipment for accessing the webpage is reduced due to the fault of the first DNS server and other reasons in the online process of the user equipment is solved.

Optionally, in a possible implementation manner of the second aspect, the step of: the method for receiving the relevant information of the second DNS sent by the access server by the user equipment comprises the following steps: and the user equipment receives a target message sent by the access server, wherein the target message comprises the related information of the second DNS server.

The possible implementation mode improves the realizability of the scheme.

Optionally, in a possible implementation manner of the second aspect, the target packet in the above step carries an option6 attribute.

Optionally, in a possible implementation manner of the second aspect, the target packet in the foregoing step is a lease renewal response packet, and the lease renewal response packet carries an option6 attribute.

A third aspect of the present application provides an access server configured to perform the method of the first aspect or any possible implementation manner of the first aspect. In particular, the access server comprises means or an element for performing the method of the first aspect or any possible implementation manner of the first aspect.

A fourth aspect of the present application provides a user equipment configured to perform the method of the second aspect or any possible implementation manner of the second aspect. In particular, the user equipment comprises means or an element for performing the method of the second aspect or any possible implementation of the second aspect.

A fifth aspect of the present application provides an access server performing the method of the first aspect or any possible implementation manner of the first aspect.

A sixth aspect of the present application provides a user equipment, which performs the method of the second aspect or any possible implementation manner of the second aspect.

A seventh aspect of the present application provides a computer storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the foregoing first aspect or any possible implementation manner of the first aspect, the second aspect or any possible implementation manner of the second aspect.

An eighth aspect of the present application provides a computer program product which, when executed on a computer, causes the computer to perform the method of the foregoing first aspect or any possible implementation manner of the first aspect, the second aspect or any possible implementation manner of the second aspect.

For technical effects brought by any one of the third, fifth, seventh and eighth aspects or any one of the possible implementation manners, reference may be made to technical effects brought by different possible implementation manners of the first aspect or the first aspect, and details are not described here.

For technical effects brought by the fourth, sixth, eighth, and eighth aspects or any one of possible implementation manners, reference may be made to technical effects brought by the second aspect or different possible implementation manners of the second aspect, and details are not described here.

Drawings

Fig. 1 is a schematic diagram of an architecture of a domain name system server distribution system in an embodiment of the present application;

fig. 2 is a schematic flow chart illustrating a domain name system server allocation method according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an access server in the embodiment of the present application;

fig. 4 is another schematic structural diagram of an access server in the embodiment of the present application;

fig. 5 is a schematic structural diagram of a user equipment in an embodiment of the present application;

fig. 6 is another schematic structural diagram of an access server in the embodiment of the present application;

fig. 7 is a schematic structural diagram of another user equipment in the embodiment of the present application.

Detailed Description

The embodiment of the application provides a domain name system server allocation method and related equipment, which are used for solving the problem that the speed of a user equipment for accessing a webpage is reduced due to the failure of a first DNS (domain name system) server and the like.

The following describes in detail the implementation principle, specific embodiments and corresponding beneficial effects of the technical solutions of the present application with reference to the drawings.

Fig. 1 is a schematic structural diagram of a domain name system server allocation system according to an embodiment of the present application. Referring to fig. 1, a system architecture in the embodiment of the present application includes: an access server 101, a domain name system, DNS, server 102, and a user equipment 103.

The access server 101 establishes connections with the DNS server 102 and the user equipment 103, respectively. The user equipment 103 establishes a connection with the DNS server 102.

Information interaction between the access server 101 and the DNS server 102 can be realized through a connection between the access server 101 and the DNS server 102.

In the embodiment of the present application, only one access server 101, one DNS server 102, and one user equipment 103 are taken as an example for description, and in practical applications, there may be more access servers, DNS servers, and user equipments.

The main function of the access server 101 is to assign a DNS server 102 to the user equipment 103 so that the user equipment 103 can access web pages through the DNS server 102.

The main function of the DNS server 102 is the conversion of domain names to IP addresses.

The access server 101 in this embodiment may be one or more of a BRAS, an optical network access server (ONT), an optical line access server (OLT), a Customer Premise Equipment (CPE), and other servers. And is not particularly limited herein.

The DNS server 102 in the embodiment of the present application is a computer and network service naming system organized into a domain hierarchy. It is composed of resolver and domain name server, and is used for transmission control protocol/internet protocol (TCP/IP) network. The domain name server may refer to a server that stores domain names and corresponding IP addresses of all hosts in the network and has a function of converting domain names into IP addresses. Wherein, the domain name must correspond to an IP address, and the IP address does not necessarily have a domain name. The DNS employs a hierarchical structure like a directory tree. The domain name server is the server side in the client/server model, and has two main forms: a main server and a forwarding server.

The user device 103 in the embodiments of the present application may be a device that provides voice and/or data connectivity only to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. The user equipment 103 may communicate with one or more core networks via a Radio Access Network (RAN), and may be mobile terminal equipment such as a mobile telephone (or "cellular" telephone) and a computer having mobile terminal equipment, for example, the user equipment 103 may be a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device that exchanges language and/or data with the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. A wireless user equipment may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), a user device (user device), or a user equipment (user equipment). And is not particularly limited herein.

The following describes a domain name system server allocation method in the embodiment of the present application with reference to the network framework of fig. 1:

referring to fig. 2, an embodiment of a domain name system server allocation method in the embodiment of the present application includes:

201. the user equipment is connected with a first DNS server.

There are various ways for the user equipment to connect to the first DNS server, which are described below:

and firstly, the access server allocates a first DNS server to the user equipment according to the corresponding relation.

The access server stores a corresponding relationship between the DNS server and the IP address of the user equipment, the corresponding relationship is configured manually and statically, and the access server cannot modify the corresponding relationship. When the user equipment applies for online to the access server, the access server allocates a first DNS server corresponding to the IP address of the user equipment to the user equipment according to the stored corresponding relation between the DNS server and the IP address of the user equipment.

And secondly, the access server distributes a first DNS server to the user equipment according to the load information.

The load information includes one or more of the number of the user devices allocated to the DNS server, the number of domain name resolution requests received by the DNS server within a certain time, and the processor usage of the DNS server. The access server can select a first DNS server from at least one DNS server according to the load condition of each DNS server for distributing to the user equipment applying for online.

Illustratively, the access server is connected with 3DNS servers, which are DNS server No. 1, DNS server No. 2, and DNS server No. 3, respectively, where the number of DNS server No. 1 connected to the user equipment is 10, the number of DNS server No. 2 connected to the user equipment is 5, and the number of DNS server No. 3 connected to the user equipment is 8. It is explained that the load of the DNS server No. 2 is smaller than the load of the DNS servers No. 1 and No. 2. The access server may assign DNS server No. 2 as the first DNS server to the user equipment that requested to go online.

Illustratively, the access server is connected to 2 DNS servers, which are DNS server No. 4 and DNS server No. 5, the DNS server No. 4 receives 5000 domain name resolution requests within 5 minutes, and the DNS server No. 5 receives 4000 domain name resolution requests within 5 minutes. It is explained that the load of the DNS server No. 5 is smaller than that of the DNS server No. 4. The access server may assign DNS server No. 5 as the first DNS server to the user equipment that requested to go online.

In the embodiment of the present application, the manner in which the user equipment connects to the first DNS server includes other manners besides the above two manners, and is not limited herein.

After the access server distributes a first DNS server to the user equipment applying for online, the user equipment is connected with the first DNS server.

202. The access server determines whether the first DNS server meets a preset condition, if yes, step 203 is executed.

The access server connects with a DNS server in the deployment networking, and the connection may be maintained for a long time or may be periodic, which is not limited herein.

The access server establishes connection with the first DNS server to inform the first DNS server of the first quantity and the second quantity, wherein the first quantity is the quantity of user equipment of which the main DNS server and/or the standby DNS server are/is the first DNS server in the user equipment on line. And the main DNS server and/or the standby DNS server in the second number of the user equipment which is offline are/is the number of the user equipment of the first DNS server.

After the first DNS server obtains the first number of the online user devices and the second number of the offline user devices, the target number of the user devices to be processed (that is, how many main DNS servers of the user devices are the first DNS servers, and how many standby DNS servers of the user devices are the first DNS servers) is recalculated.

The first DNS server may obtain load information and send it to the access server.

The load information in this embodiment may be the target number, or may be the number of domain name resolution requests received by the first DNS server within a certain time, and in practical application, the load information may also be other types of information, for example: the load information is the processor usage of the first DNS server, and is not limited herein.

After the access server acquires the load information or the communication information of the first DNS server, whether the first DNS server meets preset conditions or not is judged.

In the embodiment of the present application, there are various ways for the access server to determine whether the first DNS server meets the preset condition, which are described below:

firstly, the access server judges whether the first DNS server fails.

Because of the interaction of the load information between the access server and the first DNS server, the server can sense the connectivity of the first DNS server.

For example, after the access server sends the first number and the second number to the first DNS server, the access server does not receive the load information fed back by the first DNS server, that is, the access server determines that the first DNS server fails.

And secondly, the access server judges whether the load value in the load information sent by the first DNS server is greater than or not less than a target threshold value.

The target threshold in the embodiment of the present application is set according to actual needs, and is not limited herein.

In the embodiment of the present application, the load value of the first DNS server has multiple forms, which are respectively described as follows:

1. a target number.

Illustratively, the first DNS server has been assigned 10 user devices, and the access server informs the first DNS server to: there are 5 newly online user equipments allocated to the first DNS server, and 3 user equipments served by the first DNS server are offline, i.e. the first number is 5 and the second number is 3. The target number is 10+5-3 and 12. When the target threshold value set on the access server is 10, the access server determines that the load value of the first DNS server is greater than the target threshold value. That is, the number of the user equipments served by the first DNS server is too large, and if the new user equipment is reallocated, the internet access rate of the new user equipment is affected.

The target threshold may be set on the access server (i.e., the first DNS server sends load information to the access server, and the access server performs comparison between the load value and the target threshold), or may be set on the first DNS server (i.e., the first DNS server compares the load value and the target threshold, and sends the comparison result to the access server), which is not limited herein.

2. And the first DNS server receives the number of the domain name resolution requests within a certain time.

Illustratively, the first DNS server accepts the domain name resolution request 2 ten thousand times in 10 minutes. When the target threshold is 1 ten thousand times, the access server determines that the load value of the first DNS server is greater than the target threshold. That is, the first DNS server receives too many requests, and if new user equipment is reallocated, the rate at which the first DNS server responds to the domain name resolution request of the new user equipment is affected.

3. Processor usage of the first DNS server.

In the embodiment of the present application, only the determination method of the utilization rate of the processor is as follows: the ratio of the processor resources occupied by the processing service to the total processor resources is schematically illustrated as an example, and it can be understood that, in practical applications, the processor utilization of the first DNS server may also be determined in other manners.

Illustratively, the processor usage of the first DNS server is 90%, and when the target threshold is 80%, the access server determines that the load value of the first DNS server is greater than the target threshold. That is, if new user devices are reassigned, the first DNS server processor usage will be higher and the processor temperature will increase, which will tend to affect the processor lifetime.

In the embodiment of the present application, the load value of the first DNS server has other ways besides the three ways, and is not limited herein.

It should be understood that the foregoing two manners indicate examples, and in practical applications, the access server may also determine whether the first DNS server satisfies the preset condition in other manners, for example, triggered by an operator, and the details are not limited herein.

If the access server determines that the first DNS server meets the preset condition, that is, the first DNS server fails or the load value of the first DNS server is not less than the target threshold, that is, the first DNS server affects the use of the user equipment, step 203 is executed.

If the access server determines that the first DNS server does not satisfy the preset condition, that is, the first DNS server does not have a fault or the load value of the first DNS server is smaller than the target threshold, that is, the first DNS server does not affect the use of the user equipment, step 203 may not be performed.

203. And the access server sends the target message to the user equipment.

The method for triggering the access server to send the target packet may be, in addition to the above-described satisfaction of the preset condition, a manual trigger or a timing trigger performed by the configuration issued by the user equipment provided by the operator or by the third-party tool, which is not limited herein.

If the access server determines that the first DNS server meets the preset condition, that is, the first DNS server fails or the load value of the first DNS server is not less than the target threshold, that is, the first DNS server affects the use of the user equipment, the access server may send a target packet to the user equipment, where the target packet includes related information of a second DNS server (hereinafter referred to as second DNS information), so that the user equipment changes the first DNS server to the second DNS server.

In the embodiment of the application, the access server can make a preset condition for dynamically updating the DNS information, and when the preset condition is met, the access server triggers sending of second DNS information to the user equipment.

The preset conditions and rules are shown in table 1:

TABLE 1

And the second DNS server is a DNS server which does not have a fault or a server with a load value smaller than a target threshold value. The access server may also set an alternative list comprising a plurality of second DNS servers.

The rules in table 1 may be configured by an operator, or may be issued to the access server through a third-party tool, which is not limited herein.

The access server may also select an optimal DNS server from the plurality of second DNS servers in the candidate list, and send information related to the optimal DNS server (hereinafter referred to as optimal DNS information) to the user equipment.

The target packet in the embodiment of the present application may have various forms, which are described below:

firstly, adding a message.

The newly added message is used for triggering the access server to send a message of second DNS information to the user equipment when the first DNS server meets the preset condition. The second DNS information includes an IP address of the second DNS server, and if the optimal DNS information is sent, the optimal DNS information includes the IP address of the optimal DNS server.

The new message is a DHCP message extended by the embodiment of the application, that is, a new DHCP message type, where the name of the message type may be: forced update DNS information (DHCP DNS _ FORCE), the format of this message type may be as follows:

Option(53)DHCP Message Type(DNS_FORCE)；

Lenth:1；

DHCP:DNS_FORCE(20)。

wherein, the expanded 20 is the number of the newly added message, it is understood that 20 is only an example, and that 20 may also use other numerical values, and is not limited herein. The access Server actively triggers the new message according to the rule in table 1, and the new message also carries an Option 6(Domain name Server) attribute, including the second DNS information. The format of Option6 can be as follows:

Option：(6)Domain Name Server；

Lenth:8；

Domain Name Server：2.2.2.2；

Domain Name Server：3.3.3.3。

wherein, 2.2.2.2 represents the address of the primary DNS server, and 3.3.3.3 represents the address of the backup DNS server. If the access server selects two second DNS servers, the addresses of the two DNS servers are 2.2.2.2 and 3.3.3.3.

And II, renewing lease response message.

After the user equipment sends a lease renewing message to the access server, the access server sends a lease renewing response message to the user equipment. The lease renewal response message contains the second DNS information. That is, when the access server renews the lease response message to the ue, the Option6 attribute is added, and the Option6 attribute includes the second DNS information, so that the ue processes the lease information and the second DNS information at the same time.

Compared with the newly added message, the lease renewal response message has certain limitation, namely the lease renewal response message is not real-time and depends on the triggering of the lease renewal process.

In this embodiment, the target packet may have other types in addition to the two types described above, as long as the target packet contains DNS information, which is not limited herein.

204. The user equipment identifies second DNS information in the target message.

And after receiving the target message sent by the access server, the user equipment identifies second DNS information in the target message. I.e. identify the address in the Option6 attribute, as exemplified in step 203, the address of the primary DNS server is identified as 2.2.2.2, and the address of the standby DNS server is identified as 3.3.3.3.

When the target message is a newly added message, the user equipment identifies that the type of the message is 20, and then analyzes the message to obtain second DNS information.

And when the target message is a renewal lease response message and the user equipment processes lease information, acquiring second DNS information through an Option6 attribute.

205. And the user equipment replaces the first DNS server with the second DNS server.

And after identifying the second DNS information in the target message, the user equipment is connected to the second DNS server through the address of the second DNS server in the Option6 attribute.

In the above description on the domain name system server allocation method in the embodiment of the present application, an access server in the embodiment of the present application is described below with reference to fig. 3, and an embodiment of the access server in the embodiment of the present application includes:

a determining unit 301, configured to determine a first DNS server to which a user equipment is connected;

a judging unit 302, configured to judge whether the first DNS server satisfies a preset condition;

a sending unit 303, configured to send, if yes, relevant information of the second DNS server to the user equipment, where the relevant information of the second DNS server is used to instruct the user equipment to replace from the first DNS server to the second DNS server.

In this embodiment, operations performed by each unit in the access server are similar to those described in the embodiment shown in fig. 2, and are not described again here.

In this embodiment, after the determining unit 301 determines the first DNS server connected to the user equipment, if the determining unit 302 determines that the first DNS server connected to the user equipment meets the preset condition, the sending unit 303 sends the relevant information of the second DNS server to the user equipment, so that the user equipment changes the first DNS server to the second DNS server, and the problem that the speed of accessing the web page by the user equipment is slowed due to a failure of the first DNS server and the like in the online process of the user equipment is avoided.

Referring to fig. 4, another embodiment of an access processor in the embodiment of the present application includes:

a determining unit 401, configured to determine a first DNS server to which a user equipment is connected;

a judging unit 402, configured to judge whether the first DNS server satisfies a preset condition;

a sending unit 403, configured to send, if yes, relevant information of the second DNS server to the user equipment, where the relevant information of the second DNS server is used to instruct the user equipment to replace from the first DNS server to the second DNS server.

The access server in this embodiment further includes:

an allocating unit 404, configured to allocate a first DNS server to the user equipment according to load information of the plurality of DNS servers.

The sending unit 403 is specifically configured to send a target packet to the user equipment, where the target packet includes related information of the second DNS server.

The target message is an extended dynamic host configuration protocol message, carries an extended option 53 to indicate that the user equipment is changed from the first DNS server to the second DNS server, and carries an option6 attribute, and carries related information of the second DNS server in an option6 attribute.

The target message is a dynamic host configuration protocol lease renewal response message, the lease renewal response message carries an option6 attribute, and the option6 attribute carries related information of the second DNS server.

The determining unit 402 is specifically configured to determine whether a load value of the first DNS server is greater than a target threshold.

The determining unit 402 is specifically configured to determine whether the first DNS server fails.

In this embodiment, after the determining unit 401 determines the first DNS server connected to the user equipment, if the determining unit 402 determines that the first DNS server connected to the user equipment satisfies the preset condition, the sending unit 403 sends relevant information of the second DNS server to the user equipment, so that the user equipment changes the first DNS server to the second DNS server, and the problem that the speed of accessing a web page by the user equipment is slowed due to a failure of the first DNS server and the like in the process of online of the user equipment is avoided.

Referring to fig. 5, a user equipment in an embodiment of the present application is described below, where an embodiment of the user equipment in the embodiment of the present application includes:

a connection unit 501, configured to connect to a first DNS server;

a receiving unit 502, configured to receive relevant information of the second DNS server sent by the access server;

an identifying unit 503 for identifying the relevant information;

the connecting unit 501 is further configured to connect to a second DNS server according to the relevant information.

In this embodiment, operations performed by each unit in the ue are similar to those described in the embodiment shown in fig. 2, and are not described again here.

Referring to fig. 6, an access server in an embodiment of the present application is described below, where an embodiment of the access server in the embodiment of the present application includes:

the access server 600 may include one or more processors 601, an input/output interface 603, and a memory 604, where the input/output interface 603 is configured to send information related to the second DNS server to the user equipment or forward the target packet generated by the processor 601 to the user equipment. The memory 604 stores one or more application programs or data.

Memory 604 may be volatile storage or persistent storage, among others. The program stored in memory 604 may include one or more modules, each of which may include a sequence of instructions operating on the access server 600. Still further, the processor 601 may be configured to communicate with the memory 604 and execute a series of instruction operations in the memory 604 on the access server 600.

The access server 600 may also include one or more power supplies 602, and/or one or more operating systems, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The processor 601 may perform the operations performed by the access server in the embodiment shown in fig. 2, which are not described herein again.

Referring to fig. 7, a user equipment in an embodiment of the present application is described below, where an embodiment of the user equipment in the embodiment of the present application includes:

the user equipment 700 may include one or more processors 701, input output interfaces 703, and memory 704. The input/output interface 703 is configured to receive information related to the second DNS server sent by the access server. The memory 704 stores one or more applications or data.

Memory 704 may be volatile storage or persistent storage, among others. The program stored in memory 705 may include one or more modules, each of which may include a sequence of instructions operating on the user equipment 700. Still further, processor 701 may be configured to communicate with memory 704 to perform a series of instruction operations in memory 704 on user device 700.

The user device 700 may also include one or more power supplies 702, and/or one or more operating systems, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The processor 701 may perform the operations performed by the user equipment in the embodiment shown in fig. 2, which are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims

1. A Domain Name System (DNS) server distribution method is characterized by comprising the following steps:

the access server determines a first DNS server connected with the user equipment;

the access server judges whether the first DNS server meets preset conditions or not;

if yes, the access server sends relevant information of a second DNS server to the user equipment, and the relevant information of the second DNS server is used for indicating the user equipment to be replaced from the first DNS server to the second DNS server.

2. The method of claim 1, wherein the access server sends information about a second DNS server to the user equipment, and wherein the sending comprises:

and the access server sends a target message to the user equipment, wherein the target message comprises the related information of the second DNS server.

3. The method of claim 2, wherein the target packet is an extended dynamic host configuration protocol packet carrying an extended option 53 to instruct the UE to change from the first DNS server to the second DNS server, and wherein the target packet carries an option6 attribute carrying information related to the second DNS server in the option6 attribute.

4. The method of claim 2, wherein the target packet is a dhcp renewal reply packet, and wherein the lease renewal reply packet carries an option6 attribute and information related to the second DNS server is carried in the option6 attribute.

5. The method of any of claims 1 to 4, wherein the access server determines the first DNS server to which the user equipment is connected, and wherein the method further comprises:

and the access server distributes the first DNS server for the user equipment according to the load information of the plurality of DNS servers.

6. The method according to any one of claims 1 to 5, wherein the determining, by the access server, whether the first DNS server satisfies a preset condition comprises:

and the access server judges whether the load value of the first DNS server is greater than a target threshold value.

7. The method according to any one of claims 1 to 5, wherein the determining, by the access server, whether the first DNS server satisfies a preset condition comprises:

the access server judges whether the first DNS server fails.

8. A Domain Name System (DNS) server distribution method is characterized by comprising the following steps:

the user equipment is connected with a first DNS server;

the user equipment receives related information of a second DNS sent by an access server;

the user equipment identifies the relevant information;

and the user equipment is connected with the second DNS server according to the related information.

9. The method of claim 8, wherein the receiving, by the user equipment, the information related to the second DNS server sent by the access server comprises:

and the user equipment receives a target message sent by an access server, wherein the target message comprises the related information of the second DNS server.

10. The method of claim 9, wherein the target packet is an extended dynamic host configuration protocol packet carrying an extended option 53 to instruct the UE to change from the first DNS server to the second DNS server, and wherein the target packet carries an option6 attribute carrying information related to the second DNS server in the option6 attribute.

11. The method of claim 9, wherein the target packet is a dhcp renewal reply packet, and wherein the lease renewal reply packet carries an option6 attribute and information related to the second DNS server is carried in the option6 attribute.

12. An access server, comprising:

a determining unit, configured to determine a first DNS server to which a user equipment is connected;

the judging unit is used for judging whether the first DNS server meets preset conditions or not;

a sending unit, configured to send, if yes, relevant information of a second DNS server to the user equipment, where the relevant information of the second DNS server is used to instruct the user equipment to replace the first DNS server with the second DNS server.

13. The access server according to claim 12, wherein the sending unit is specifically configured to send a target packet to the user equipment, where the target packet includes information related to the second DNS server.

14. The access server of claim 13, wherein the target packet is an extended dhcp packet carrying an extended option 53 to instruct the ue to change from the first DNS server to the second DNS server, and wherein the target packet carries an option6 attribute carrying information related to the second DNS server in the option6 attribute.

15. The access server of claim 13, wherein the target packet is a dhcp renewal reply packet, and the lease renewal reply packet carries an option6 attribute, and the option6 attribute carries information related to the second DNS server.

16. An access server as claimed in any one of claims 12 to 15, further comprising:

and the distribution unit is used for distributing the first DNS server to the user equipment according to the load information of the plurality of DNS servers.

17. The access server according to any one of claims 12 to 16, wherein the determining unit is specifically configured to determine whether the load value of the first DNS server is greater than a target threshold.

18. The access server according to any one of claims 12 to 16, wherein the determining unit is specifically configured to determine whether the first DNS server fails.

19. A user device, comprising:

a connection unit configured to connect to a first DNS server;

the receiving unit is used for receiving the related information of the second DNS sent by the access server;

an identifying unit configured to identify the related information;

the connecting unit is further configured to connect to the second DNS server according to the relevant information.

20. The ue of claim 19, wherein the receiving unit is specifically configured to receive a target packet sent by an access server, and the target packet includes information related to the second DNS server.

21. The UE of claim 20, wherein the target packet is an extended DHCP packet carrying an extended option 53 to instruct the UE to change from the first DNS server to the second DNS server, and wherein the target packet carries an option6 attribute carrying information related to the second DNS server in the option6 attribute.

22. The UE of claim 20, wherein the target packet is a DHCP renewal response packet, and wherein the lease renewal response packet carries an option6 attribute, and wherein the option6 attribute carries information related to the second DNS server.

23. An access server, comprising:

the system comprises a processor, a memory and an input/output interface;

the processor is connected with the memory and the input/output interface;

the processor performs the method of any one of claims 1 to 7.

24. A user device, comprising:

the system comprises a processor, a memory and an input/output interface;

the processor is connected with the memory and the input/output interface;

the input and output interface is used for receiving the related information of the second DNS sent by the access server;

the processor performs the method of any one of claims 8 to 11.

25. A computer storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 11.

26. A computer program product, characterized in that the computer program product, when executed on a computer, causes the computer to perform the method according to any of claims 1 to 11.