CN116489128A

CN116489128A - Domain name resolution method and electronic equipment

Info

Publication number: CN116489128A
Application number: CN202310651980.0A
Authority: CN
Inventors: 王佳
Original assignee: Beijing Yunkuanzhiye Network Technology Co ltd
Current assignee: Beijing Yunkuanzhiye Network Technology Co ltd
Priority date: 2023-06-02
Filing date: 2023-06-02
Publication date: 2023-07-25

Abstract

The disclosure provides a domain name resolution method and electronic equipment, and relates to the technical field of computer networks. The specific implementation scheme is as follows: receiving a DNS request sent by a client; determining DNS analysis records corresponding to the DNS requests according to the attribute information of the client and the data information in the database, wherein the attribute information of the client at least comprises source IP, line outlet and domain name attribute of the client and a network service providing point connected with the client; and feeding back the DNS analysis record to the client. According to the technical scheme of the disclosure, a quick and high-quality DNS service is provided for a user using an SD-WAN according to network attribute information of a client.

Description

Domain name resolution method and electronic equipment

Technical Field

The present disclosure relates to the field of computer networks, and in particular, to a domain name resolution method and an electronic device.

Background

In the environment that cloud computing, mobile application and enterprise globalization become a big background, more and more real-time applications (such as remote offices, video conferences, remote desktops, payment transaction systems, remote medical treatment and the like) are transmitted among a plurality of nodes, and the problems of disconnection, slow access and the like can amplify the dissatisfaction of users and cause transaction loss. The SD-WAN not only solves the problems of unstable Internet and expensive cost of special lines, but also can meet the requirements of instantaneity and instantaneity of the applications to a great extent.

Disclosure of Invention

The disclosure provides a domain name resolution method and electronic equipment.

According to an aspect of the present disclosure, there is provided a domain name resolution method, including:

receiving a DNS request sent by a client;

determining DNS analysis records corresponding to the DNS requests according to the attribute information of the client and the data information in the database, wherein the attribute information of the client at least comprises source IP, line outlet and domain name attribute of the client and a network service providing point connected with the client;

and feeding back the DNS analysis record to the client.

According to another aspect of the present disclosure, there is provided an electronic device for domain name resolution, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the embodiments of the present disclosure.

According to the technology of the present disclosure, a fast and high-quality DNS service can be provided to a user using an SD-WAN according to network attribute information of a client.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a flow diagram of a domain name resolution method according to an embodiment of the present disclosure;

FIG. 2 is a flow chart diagram II of a domain name resolution method according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a domain name resolution system performing the domain name resolution method of the present disclosure, according to an embodiment of the present disclosure;

fig. 4 is a block diagram of an electronic device used to implement a domain name resolution method of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

SD-WAN, software defined wide area network, is a service formed by applying SDN (software design network, software defined network) technology to a wide area network scenario. Such services are used to connect enterprise networks, data centers, internet applications, and cloud services over a wide geographic range, and are intended to help users reduce the expense of wide area networks and increase the flexibility of network connections.

SD-WAN is a software-based network application technology applied to WAN transport connections that enables enterprises to integrate and virtualize wide area network connections and functions into a centralized strategy to simplify the deployment and management of complex WAN topologies.

However, since multiple bandwidths belong to different operators, each operator can only rapidly analyze own broadband, but other bandwidths cannot be analyzed and error reported, so that the situation that the network speed is slow and the user is blocked when the SD-WAN is configured is caused.

Based on this, the present disclosure provides a domain name resolution method, and fig. 1 is a schematic flow diagram of a domain name resolution method according to an embodiment of the present disclosure, including:

s110, receiving a DNS request sent by a client;

s120, determining DNS analysis records corresponding to the DNS requests according to attribute information of the clients and data information in a database, wherein the attribute information of the clients at least comprises source IP, line outlet and domain name attribute of the clients and network service providing points connected with the clients;

s130, feeding back the DNS analysis record to the client.

Illustratively, the method of the present embodiment may be applied to a domain name resolution system, and a user using an SD-WAN may erect a CPE (Customer Premise Equipment, client terminal device) at a network outlet, where a firewall may be set to intercept the DNS request and forward the DNS request to the domain name resolution system.

Further, in this embodiment, the domain name resolution system may receive a DNS request sent by a client (i.e. CPE), determine a DNS resolution record corresponding to the DNS request according to attribute information of the client (including at least a source IP of the client, a line outlet, a domain name attribute, and a network service providing point connected to the client) and data information in a database, and feed back a correct resolution result to the client. Thereby providing a dedicated domain name resolution service for the SD-WAN and providing a more appropriate DNS service according to the network properties of the client.

In one embodiment, step S120 includes:

inquiring a target cache pool corresponding to the source IP of the client according to the source IP of the client in the attribute information and a mapping relation table in a database, wherein the mapping relation table reflects the corresponding relation between the source IP of the client and the cache pool;

if the target cache pool exists, determining a DNS analysis record corresponding to the DNS request in the target cache pool.

It can be understood that the domain name resolution system may further store a DNS resolution record obtained after the DNS request received before is resolved by the DNS server, and store the DNS resolution record in a cache pool corresponding to the source IP according to different source IPs, where a mapping relationship table including a correspondence between the source IP and the cache pool is stored in a database of the system. For a received DNS request sent by a client, a target cache pool corresponding to a source IP of the client may be queried according to the mapping table, and a DNS resolution record corresponding to the DNS request may be matched in the target cache pool.

In one embodiment, step S120 further includes:

if the target cache pool does not exist or the DNS analysis record corresponding to the DNS request does not exist in the target cache pool, determining a DNS server corresponding to the DNS request according to the attribute information of the client and a domain name list in a database;

and obtaining a DNS analysis record corresponding to the DNS request by using a DNS server.

It will be appreciated that for a received DNS request sent by a client, there may not be a target cache pool in the system that matches the source IP of its client, or even if there is a target cache pool, there may not be a match to the DNS resolution record corresponding to the DNS request. In this case, it is necessary to determine a DNS server that processes the DNS request from the attribute information of the client and the domain name list in the database, and acquire a DNS resolution record corresponding to the DNS request using the DNS server.

In one embodiment, after obtaining the DNS resolution record corresponding to the DNS request, the method further includes:

and storing the DNS analysis record corresponding to the DNS request according to the source IP of the client.

It can be appreciated that if the DNS request needs to be resolved by using the DNS server to obtain a resolution result, it is indicated that the DNS resolution record corresponding to the current DNS request is not stored in the system. Therefore, after obtaining the DNS resolution record corresponding to the DNS request by using the DNS server, the DNS resolution record needs to be stored.

Further, storing DNS resolution records also includes two cases, case one:

and if the target cache pool exists, storing the DNS analysis record into the target cache pool.

It will be appreciated that the target cache pool, i.e. the cache pool corresponding to the source IP of the client sending the current DNS request, in this case, there is already a cache pool in the system that can be used to store the DNS resolution record corresponding to the current DNS request, and only the DNS resolution record needs to be stored in the target cache pool.

And a second case:

if the target cache pool does not exist, constructing a cache pool corresponding to the source IP of the client according to the source IP of the client and the line outlet;

and storing the DNS analysis record into a cache pool corresponding to the source IP of the client.

It can be understood that if the target cache pool does not exist in the system, a cache pool corresponding to the source IP of the client needs to be constructed according to the source IP and the line outlet of the client sending the current DNS request, and then the DNS resolution record is stored in the constructed cache pool.

By adopting the method of the embodiment, the analysis record of the DNS server for the DNS request is stored in the cache pool corresponding to the client source IP, so that the corresponding DNS analysis record can be obtained quickly in a matching mode in the cache pool under the condition that the DNS request analyzed before is received later, and the analysis result feedback efficiency for the DNS request under the SD-WAN use scene is improved.

In one embodiment, when there is no target cache pool or no DNS resolution record corresponding to the DNS request exists in the target cache pool, determining, according to attribute information of the client and a domain name list in the database, a DNS server corresponding to the DNS request includes:

determining whether a DNS server corresponding to the DNS request belongs to a local DNS server according to the domain name attribute in the attribute information and a domain name list in a database;

if the client belongs to the local DNS server, determining the DNS server corresponding to the DNS request according to the network service providing point connected with the client in the attribute information.

The system database is provided with a domain name list, the domain name list contains the local domain name analyzed and sorted by the prior system according to the processed DNS request, and the DNS server suitable for analyzing the current DNS request can be judged whether belongs to the local DNS server or not based on the domain name attribute of the domain name list comparison client.

If the domain name of the client exists in the domain name list, it is indicated that the DNS server adapted to resolve the current DNS request belongs to a local server, and the DNS server specifically handling the current DNS request may be further determined according to a network service providing point connected to the client.

On the basis, if the domain name of the client does not exist in the domain name list, it is stated that the DNS server suitable for resolving the current DNS request does not belong to a local server, and in this case, the determination manner of the DNS server processing the current DNS request is:

if the client does not belong to the local DNS server, determining the DNS server corresponding to the DNS request according to the line outlet of the client in the attribute information.

By adopting the method of the embodiment, under the condition that the DNS analysis record corresponding to the current DNS request is not stored in the cache pool, the distribution mode of the DNS request can be accurately determined according to the pre-stored local domain name list, and proper and high-quality DNS service can be provided for the SD-WAN according to the network attribute of the client.

In one embodiment, as shown in fig. 2, the domain name resolution method of the present application further includes:

s210, recording log data of a DNS request which is analyzed by a DNS server corresponding to the DNS request;

s220, analyzing the log data to obtain an analysis result corresponding to the log data;

and S230, updating a domain name list in the database according to the analysis result.

Illustratively, the domain name resolution system may record log data of DNS server resolution DNS requests, including domain name resolution request behavior, request status, request results, and duration, among others. The system can periodically analyze the log data to obtain an analysis result corresponding to the log data. And judging whether the domain name belongs to the local domain name according to the analysis result, and updating a domain name list in the database under the condition of belonging to the local domain name.

By adopting the method of the embodiment, the log data analyzed by the DNS can be recorded, and the log data can be analyzed to update the domain name list in the database. Further, the DNS server suitable for resolving the current DNS request can be quickly determined by using the domain name list, so that the resolution efficiency of the DNS request sent by the client is improved.

In one embodiment, the mapping relationship table in the database may also be updated periodically based on the log data, and the log data may be analyzed to determine a mapping relationship between the client source IP and the cache pool, which is not included in the mapping relationship table, and update the mapping relationship table based on the mapping relationship.

Fig. 3 illustrates a schematic structure diagram of a domain name resolution system performing the domain name resolution method of the present disclosure, and as illustrated in fig. 3, the domain name resolution system includes a primary analyzer, a secondary analyzer, a cache pool, a configuration database, a timer, a request log processor, a data analyzer, and the like.

The configuration database stores cache pool configuration information, a local domain name list and a mapping relation table reflecting the corresponding relation between the source IP of the client and the cache pool.

The request log processor may record log data of DNS requests that are resolved by the DNS server, including domain name resolution request behavior, request status, request results, and duration, etc. The data analyzer may periodically write log data into the monitoring service state, analyze the request content and the result to determine whether the domain name is a local domain name, and update the local domain name list in the configuration database if the domain name belongs to the local domain name.

The cache pool is used for storing DNS analysis records according to time information, and different combinations of client source IP and line outlet belong to different cache pools.

The timer comprises a source IP corresponding cache pool data synchronization timer and a local domain name data synchronization timer which are respectively used for periodically updating a mapping relation table and a local domain name list in a configuration database according to the analysis result of the data analyzer. The timer also comprises an expiration cache cleaning timer, and the expiration cache cleaning timer is used for regularly cleaning the DNS analysis records which are not used for a long time in the cache pool so as to ensure that a certain storage space is provided in the cache pool to store new DNS analysis records.

The first-level analyzer is used for determining in which cache pool to match the current DNS request with the stored DNS analysis record according to a mapping relation table reflecting the corresponding relation between the source IP of the client and the cache pool in the configuration database.

If there is no cache pool corresponding to the client source IP of the current DNS request, or the DNS resolution record corresponding to the current DNS request cannot be matched in the cache pool, the current DNS request needs to be further processed by using a secondary analyzer. The secondary analyzer is used for determining how to distribute the current DNS request to the corresponding DNS server according to the local domain name list in the configuration database and the domain name attribute of the client side sending the current DNS request.

Specifically, if the domain name of the current DNS request belongs to the local domain name, the DNS server corresponding to the current DNS request may be determined according to a network service provider point (POP point) connected by the client. If the domain name of the current DNS request does not belong to the local domain name, a DNS server corresponding to the current DNS request may be determined according to the line outlet of the client.

Specific arrangements and implementations of embodiments of the present application are described above from different perspectives. By using the method provided by the embodiment, the DNS analysis record can be stored in the domain name analysis system, if the corresponding DNS analysis record can be matched in the storage under the condition of receiving a new DNS request, the analysis result can be directly fed back, if the corresponding DNS analysis record can not be matched in the storage, the DNS request can be distributed to a proper DNS server for analysis according to the network attribute of the client side, and therefore the analysis efficiency and the analysis effect for the DNS request under the SD-WAN use scene are improved.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user personal information all conform to the regulations of related laws and regulations, and the public sequence is not violated.

Fig. 4 shows a block diagram of an electronic device according to an embodiment of the present application. As shown in fig. 4, the electronic device includes: memory 410 and processor 420, with instructions executable on processor 420 stored in memory 410. The processor 420, when executing the instructions, implements the methods of the embodiments described above. The number of memories 410 and processors 420 may be one or more. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.

The electronic device may further include a communication interface 430 for communicating with external devices for data interactive transmission. The various devices are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor 420 may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of a GUI on an external input/output device, such as a display device coupled to an interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 4, but not only one bus or one type of bus.

Alternatively, in a specific implementation, if the memory 410, the processor 420, and the communication interface 430 are integrated on a chip, the memory 410, the processor 420, and the communication interface 430 may communicate with each other through internal interfaces.

It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an advanced reduced instruction set machine (Advanced RISC Machines, ARM) architecture.

The present embodiments provide a computer readable storage medium (such as the memory 410 described above) storing computer instructions that when executed by a processor implement the methods provided in the embodiments of the present application.

Alternatively, the memory 410 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for functions; the storage data area may store data created from the use of the electronic device that identifies the lane edge, and the like. In addition, memory 410 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 410 may optionally include memory generated remotely from processor 420, which may be connected to the electronic device that identifies lane edges via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), random Access Memory (RAM) of other physical types, read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage media, or any other non-transmission media, that can be used to store information that can be accessed by a computing device. Computer-readable Media, as defined herein, does not include non-Transitory computer-readable Media (transmission Media), such as modulated data signals and carrier waves.

Illustratively, the processor in the controller or electronic device includes an Automated Domain Control Module (ADCM).

The vehicle in the present embodiment may be exemplified by any power-driven vehicle such as a fuel vehicle, an electric vehicle, a solar vehicle, or the like. The vehicle in the present embodiment may be an autonomous vehicle, for example.

Other structures of the vehicle of the present embodiment, such as the specific structures of the frame and the wheels, the connection fastening members, etc., may be applied to various technical solutions that are known to those skilled in the art now and in the future, and will not be described in detail herein.

In the description of this specification, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various changes or substitutions within the technical scope of the present application, and these should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for domain name resolution, comprising:

receiving a DNS request sent by a client;

determining a DNS analysis record corresponding to the DNS request according to the attribute information of the client and the data information in the database, wherein the attribute information of the client at least comprises a source IP (Internet protocol), a line outlet and a domain name attribute of the client and a network service providing point connected with the client;

and feeding back the DNS analysis record to the client.

2. The method according to claim 1, wherein determining a DNS resolution record corresponding to the DNS request according to the attribute information of the client includes:

inquiring a target cache pool corresponding to the source IP of the client according to the source IP of the client in the attribute information and a mapping relation table in the database, wherein the mapping relation table reflects the corresponding relation between the source IP of the client and the cache pool;

and if the target cache pool exists, determining a DNS analysis record corresponding to the DNS request in the target cache pool.

3. The method according to claim 2, wherein determining a DNS resolution record corresponding to the DNS request according to the attribute information of the client, further comprises:

if the target cache pool does not exist or the DNS analysis record corresponding to the DNS request does not exist in the target cache pool, determining a DNS server corresponding to the DNS request according to the attribute information of the client and a domain name list in the database;

and obtaining a DNS analysis record corresponding to the DNS request by utilizing the DNS server.

4. The method of claim 3, wherein the obtaining, with the DNS server, a DNS resolution record corresponding to the DNS request further comprises:

and storing a DNS analysis record corresponding to the DNS request according to the source IP of the client.

5. The method of claim 4, wherein storing the DNS resolution record corresponding to the DNS request according to the source IP of the client comprises:

6. The method of claim 4, wherein storing DNS resolution records corresponding to the DNS request according to the source IP of the client, further comprises:

and storing the DNS analysis record into the cache pool corresponding to the source IP of the client.

7. A method according to claim 3, wherein said determining a DNS server corresponding to the DNS request based on the attribute information of the client and the list of domain names in the database comprises:

determining whether a DNS server corresponding to the DNS request belongs to a local DNS server according to the domain name attribute in the attribute information and a domain name list in the database;

and if the DNS server belongs to the local DNS server, determining the DNS server corresponding to the DNS request according to the network service providing point connected with the client in the attribute information.

8. The method of claim 7, wherein determining a DNS server corresponding to the DNS request based on the attribute information of the client and the list of domain names in the database, further comprises:

and if the DNS server does not belong to the local DNS server, determining the DNS server corresponding to the DNS request according to the line outlet of the client in the attribute information.

9. A method according to claim 3, characterized in that the method further comprises:

recording a DNS server corresponding to the DNS request and analyzing log data of the DNS request;

analyzing the log data to obtain an analysis result corresponding to the log data;

and updating a domain name list in the database according to the analysis result.

10. An electronic device for domain name resolution, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.