CN110933156A - Domain name resolution method and device - Google Patents
Domain name resolution method and device Download PDFInfo
- Publication number
- CN110933156A CN110933156A CN201911175628.4A CN201911175628A CN110933156A CN 110933156 A CN110933156 A CN 110933156A CN 201911175628 A CN201911175628 A CN 201911175628A CN 110933156 A CN110933156 A CN 110933156A
- Authority
- CN
- China
- Prior art keywords
- domain name
- dns
- address information
- address
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000004044 response Effects 0.000 claims abstract description 19
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
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]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a domain name resolution method and device. In the application, forwarding equipment in a local area network is used for replacing a local DNS server to perform domain name resolution. After receiving a DNS request message carrying domain name information of a target website, the forwarding device analyzes the domain name information based on a preset DNS analysis record to obtain address information of the target website, and finally returns a response message carrying the address information. Because the DNS request message sent by the user host is acquired by the forwarding equipment and the domain name resolution is completed, the DNS request message is prevented from being forwarded from the local area network to the local DNS server for multiple times. Because the forwarding device in the local area network receives the DNS request message faster, the efficiency of domain name resolution of the forwarding device is higher than that of a local DNS server.
Description
Technical Field
The application relates to the technical field of internet, in particular to a method and a device for domain name resolution.
Background
The DNS (Domain Name System) is a distributed network directory service, and is mainly used for interconversion between Domain names and IP addresses. Based on the DNS technology, an internet user can access a target website by using a domain name instead of an address, so that the internet can be accessed more conveniently.
In the DNS technology, when a user host accesses a website using a domain name, if address information corresponding to domain name information of a website to be accessed is not queried in a cache of the user host, address information corresponding to the domain name information is queried for a local DNS server. After receiving the DNS request message, the local DNS server first queries the domain name information in a local cache, and if the address information corresponding to the domain name information is not cached, continues querying to other DNS servers. Until the address information corresponding to the domain name information of the website to be accessed is successfully inquired. And after inquiring the address information, the local DNS server returns the address information to the user host.
Because the user host is generally located in the local area network, when the user host queries the local DNS server for address information corresponding to the domain name of the website to be accessed, the DNS request message sent by the user host needs to be forwarded to the local DNS server via the local area network gateway. And the network situation between the local area network gateway and the local DNS server is complex, and there are many forwarding devices such as routers and switches, so the DNS request message needs to be forwarded many times before being finally sent to the local DNS server, and the response message sent by the local DNS server needs to be forwarded many times before being sent to the user host, which greatly reduces the efficiency of the user host in querying the local DNS server for the address information corresponding to the domain name of the website to be accessed.
Disclosure of Invention
In view of the above technical problems, the present application provides a method and an apparatus for domain name resolution, which can effectively improve the efficiency of domain name resolution.
According to a first aspect of the present application, there is provided a method of domain name resolution, the method comprising:
receiving a DNS request message sent by the user host; the DNS request message carries domain name information of a target website to be accessed;
searching address information of a target website corresponding to the domain name information based on a preset DNS analysis record; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website;
if the address information is found, returning the address information of the target website to the user host, so that the user host accesses the target website based on the address information.
According to a second aspect of the present application, there is provided an apparatus for domain name resolution, the apparatus comprising:
a receiving unit, configured to receive a DNS request packet sent by the user host; the DNS request message carries domain name information of a target website to be accessed;
the first searching unit is used for searching address information of a target website corresponding to the domain name information based on a preset DNS analysis record; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website;
and the response unit is used for returning the address information of the target website to the user host if the address information is found so as to enable the user host to access the target website based on the address information.
According to the method and the device, forwarding equipment in a local area network is used for replacing a local DNS server to perform domain name resolution, after receiving a DNS request message to be forwarded, which is sent by a user host, the forwarding equipment acquires domain name information of a target website in the DNS request message, inquires address information corresponding to the domain name information based on a preset DNS resolution record, and returns a response message carrying the address information to the user host.
Because the DNS request message sent by the user host is acquired by the forwarding equipment in the local area network and the domain name resolution is completed, not only is the DNS request message prevented from being forwarded from the local area network forwarding equipment to the local DNS server for multiple times, but also the DNS response message is prevented from being forwarded from the local DNS server to the local area network forwarding equipment for multiple times. The forwarding device in the local area network receives the DNS request message faster, and the user host receives the DNS response message returned by the forwarding device faster, so that the resolution efficiency of the forwarding device on the domain name of the website to be accessed by the user host is higher than that of a local DNS server.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of an application scenario illustrated in an exemplary embodiment of the present application;
FIG. 2 is a flow chart illustrating a domain name resolution method according to an exemplary embodiment of the present application;
fig. 3 is a hardware structure diagram of a forwarding device according to an exemplary embodiment of the present application;
fig. 4 is a block diagram of a domain name resolution apparatus according to an exemplary embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
For the convenience of memory, when a user accesses a target website, a domain name is usually used to identify the address of the website instead of an IP address.
After receiving the Domain name information of the target website to be accessed, the user host needs to use a Domain Name System (DNS) to realize the interconversion between the Domain name and the IP address.
Referring to fig. 1, fig. 1 is a schematic diagram of an application scenario shown in an exemplary embodiment of the present application, where the application scenario includes a user host, a forwarding device 1, a forwarding device 2, and a local DNS server, where the user host and the forwarding device 1 are located in a local area network.
The user host refers to a PC, a server or a mobile terminal and other equipment needing to access a target website; the forwarding equipment refers to network equipment such as a switch, a router or a VPN server and the like and is used for forwarding a data packet between the user host and the local DNS server; the local DNS server refers to a local DNS server provided by an operator, and provides domain name resolution service for a user host of a local area network (e.g., the local area network in fig. 1), and the local DNS server caches domain names of some conventional websites and address information corresponding to the domain names. In a general network environment, a large number of forwarding devices are generally deployed between a user host and a local DNS server, and in this embodiment, only the forwarding device 1 and the forwarding device 2 shown in fig. 1 are taken as an example.
In the existing domain name resolution technology, domain name resolution is generally implemented by a local DNS server. Taking the scenario shown in fig. 1 as an example, assume that the domain name of the website that the user host needs to access is www.111.com.
And if the local cache of the user host does not have the address information corresponding to the domain name, the user host initiates a DNS request carrying the domain name to a local DNS server. The request message is forwarded to the local DNS server via forwarding device 1 and forwarding device 2.
After receiving the DNS request, the local DNS server first queries its cache. If the address information corresponding to the domain name exists in the cache, the local DNS server returns a response message carrying the address information to the user host; and if the domain name does not exist, the local DNS server inquires the address information corresponding to the domain name from other servers. And returning a response message carrying the address to the user host by the local DNS server until the address information corresponding to the domain name is successfully inquired.
According to the domain name resolution method, due to the fact that the network situation between the local area network gateway and the local DNS server is complex, and a large number of forwarding devices such as routers and switches exist, DNS request messages initiated by user hosts in the local area network need to be forwarded in a multi-layer mode through a large number of forwarding devices to reach the local DNS server, the local DNS server receives the DNS request slowly, and therefore domain name resolution efficiency is low.
In view of the above, the present application provides a new domain name resolution method. In the application, forwarding equipment in a local area network is used for replacing a local DNS server to perform domain name resolution. After receiving a DNS request message carrying domain name information of a target website, the forwarding device analyzes the domain name information based on a preset DNS analysis record to obtain address information of the target website, and finally returns a response message carrying the address information. Because the DNS request message sent by the user host is acquired by the forwarding equipment and the domain name resolution is completed, the DNS request message is prevented from being forwarded from the local area network to the local DNS server for multiple times. Because the forwarding device in the local area network receives the DNS request message faster, the efficiency of domain name resolution of the forwarding device is higher than that of a local DNS server.
It should be noted that the address information described in this application includes IP address information and the like, and of course, the address information may also include other types of address information. Here, the address information is merely exemplary and is not particularly limited.
The following describes the domain name resolution method provided in the present application in detail, taking address information as an IP address as an example.
Referring to fig. 2, fig. 2 is a flowchart illustrating a domain name resolution method according to an exemplary embodiment of the present application.
As shown in fig. 2, the method comprises the following steps:
step S201: the forwarding equipment receives a DNS request message; the DNS request message carries domain name information of a target website to be accessed.
In the embodiment of the application, when the user host receives an access request of a user to a certain target website, the domain name information of the target website is generally received. And if the IP address corresponding to the domain name information of the target website is not cached locally by the user host, filling the domain name information into the DNS request message, and sending the DNS request message by taking the preset IP address of the local DNS server as the destination address of the DNS request message.
Because the user host and the local DNS server are not two directly connected network devices, the forwarding device in the local area network will receive the DNS request message first.
As an optional embodiment, the forwarding device may determine all received messages, and if the message is a DNS request message, execute step S202; if the message is not a DNS request message, forwarding the message according to the destination IP address in the message.
As another optional embodiment, the forwarding device is preset with a subscriber host address table, where the address table includes a plurality of subscriber host address table entries, where each entry includes an IP address or a MAC address. After receiving any message, the forwarding device may process the received message through steps S2011 and S2012.
Step S2011: the forwarding device determines whether the message is a DNS request message, and if the message is a DNS request message, step S2012 is executed; if the message is not a DNS request message, forwarding the message according to the destination IP address in the message.
Step S2012: the forwarding device obtains the source address of the message and checks whether the source address of the message hits the preset user host address table. If yes, go to step S202; if not, the message is forwarded according to the destination IP address in the message.
Step S202: the forwarding equipment searches address information of a target website corresponding to the domain name information based on a preset DNS analysis record; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website.
The forwarding device is preset with DNS analysis records, which comprise a plurality of record table entries, wherein each record table entry comprises a record type, information before analysis and information after mapping. The DNS analysis record types are 9 types, namely an A record, an AAAA record, an NS record, an SOA record, a CNAME record, an MX record, a TXT record, a PTR record and an SRV record, and each analysis record type plays a corresponding role in the domain name analysis process. For example, a record is used to provide IPv4 information, an AAAA record is used to provide IPv6 information, a CNAME record is used to provide alias information, and so on, and will not be described in detail herein.
The DNS resolution record can be set specifically for the actual needs of the subscriber host in the local network in which the forwarding device is located. For example, in fig. 1, a forwarding device 1 presets a DNS resolution record 1 for a user host in a local area network.
After receiving the DNS request message, the forwarding device obtains the domain name information of the target website with access, which is carried in the message, queries the record type of the domain name information in a preset DNS resolution record, further queries according to the record type, and finally queries the address information corresponding to the domain name information through one or more entries in the DNS resolution record.
The method for searching the address information of the target website corresponding to the domain name information is described below by two specific embodiments.
Assume that the DNS resolution record preset by the forwarding device is shown in table 1:
| type of record | Pre-mapping information | Post-mapping information |
| CNAME | www.111.com | www.222.com |
| A | www.222.com | 14.215.177.39 |
| A | www.123.com | 18.1.1.1 |
TABLE 1
Example 1: assume that the domain name information carried in the DNS request message received by the forwarding device is www.111.com.
Firstly, after acquiring domain name information www.111.com, the forwarding device queries in table 1 that the record type of the domain name is CNAME, and the alias corresponding to the domain name (i.e., www.111.com) is www.222.com; the forwarding device then looks up in table 1 that the record type of www.222.com is a and the IP address corresponding to the domain name (i.e., www.222.com) is 14.215.177.39.
Thus, the IP address corresponding to the domain name information www.111.com to be resolved can be determined to be 14.215.177.39.
Example 2: assume that the domain name information carried in the DNS request message received by the forwarding device is www.222.com.
After obtaining the domain name information www.222.com, the forwarding device queries in table 1 that the record type of the domain name is a, and the IP address corresponding to the domain name (i.e., www.222.com) is 14.215.177.39.
Thus, the IP address corresponding to the domain name information www.222.com to be resolved can be determined to be 14.215.177.39.
Step S203: if the address information is found, the forwarding equipment returns the address information of the target website to the user host indicated by the source address of the DNS request message, so that the user host accesses the target website based on the address information.
In step S201, after the forwarding device obtains the DNS request message, it may also obtain a source address of the DNS request message, where the source address is generally an address of a user host that initiates the DNS request message. If the address information is queried in step S202, the forwarding device returns a DNS reply packet carrying the address information queried in step S202 to the user host, so that the user host accesses the target website based on the address information.
Thus, the flow shown in fig. 2 is completed.
As can be seen from the flow shown in fig. 2, in the present application, a forwarding device is used to replace a local DNS server for domain name resolution, and after receiving a DNS request message to be forwarded, which is sent by a user host, the forwarding device obtains domain name information of a target website to be accessed in the DNS request message, queries address information corresponding to the domain name information based on a preset DNS resolution record, and returns a response message carrying the address information to the user host. Because the DNS request message sent by the user host is acquired by the forwarding equipment in the local area network and the domain name resolution is completed, the DNS request message is prevented from being forwarded to the local DNS server from the local area network for multiple times. The forwarding device in the local area network receives the DNS request message faster, so that the efficiency of domain name resolution of the forwarding device is higher than that of a local DNS server.
It can be understood that the method shown in fig. 2 is applied to a forwarding device, which may be any forwarding device in a network where the user host is located, as long as the forwarding device can receive a message sent by the user host, and the forwarding device includes a switch, a router, a VPN server, or the like, and is not limited specifically herein.
Alternatively, the forwarding device may be a gateway device in a local area network. Since all network traffic in the local area network needs to pass through the gateway device, the gateway device only needs to be modified to execute the method described in fig. 2. Meanwhile, after receiving the DNS request message, the gateway device does not need to forward the message to a local DNS server through a complex network environment, but directly performs domain name resolution, so that the efficiency of domain name resolution can be effectively improved, and other forwarding devices do not need to be modified to influence the normal use of the forwarding devices.
In step S202 in fig. 2, if the forwarding device does not query the preset DNS resolution record for the address information corresponding to the domain name information of the target website in the DNS request message, the forwarding device queries the DNS server for the address information corresponding to the domain name information, and adds the address information and the domain name information of the target website to the DNS resolution record based on the corresponding relationship between the queried address information and the domain name information of the target website.
The method of "forwarding a device query to a DNS server" is explained below by two embodiments.
As an alternative embodiment, the forwarding device may query a local DNS server.
It can be understood that, since the message is a DNS request message initiated by the user host, the destination IP address of the message is the IP address of the local DNS server, and the message is forwarded according to the destination IP address in the message.
After the forwarding device forwards the DNS request packet to the local DNS server, the local DNS server first determines whether to locally cache the address information corresponding to the domain name information carried in the DNS request packet, and if not, the local DNS server queries the address information corresponding to the domain name from other DNS servers. After the local DNS server inquires the address information corresponding to the domain name information, a DNS response message carrying the address information is returned according to the source address in the DNS request message.
After receiving the DNS response message, the forwarding device analyzes the DNS response message and obtains address information corresponding to the domain information of the target website. On one hand, a response message is returned to the user host according to the method of step S203 in fig. 2, and on the other hand, the queried domain name information of the target website and the address information corresponding to the queried domain name information are added to the locally stored DNS resolution record.
As another alternative embodiment, the forwarding device may not forward the message to the local DNS server, but re-initiate the query request to a DNS server other than the local DNS server.
After the forwarding device queries the address information corresponding to the domain name information, on one hand, a response message is returned to the user host according to the method in step S203 in fig. 2, and on the other hand, the queried domain name information of the target website and the address information corresponding to the queried domain name information are added to the locally stored DNS resolution record.
In the two embodiments, the DNS resolution record may be dynamically updated, and when the forwarding device subsequently performs domain name resolution, the forwarding device may perform query based on the updated DNS resolution record, so that the coverage is wider, and the efficiency of domain name resolution is improved.
The domain name resolution method proposed in the present application is explained in detail by a specific embodiment.
Assume that the IP address of the user host in the local area network is 192.168.1.2 and the IP address of the local DNS server is 114.114.114.114. Assume that the domain name information of the target website to be accessed received by the user host is www.123.com.
The first step is as follows: the user host sends a DNS request message carrying domain name information www.123.com, wherein the source IP address of the message is 192.168.1.2, and the destination IP address is 114.114.114.114.
The second step is that: the forwarding device receives the message and judges that the message is a DNS request message.
The third step: the DNS resolution record preset by the forwarding device is shown in table 1, and it can be known from table 1 that the record type of www.123.com is an a record, and the IP address corresponding to the domain name is obtained by querying to be 18.1.1.1.
The fourth step: the forwarding device sends a DNS reply message carrying address information 18.1.1.1 to the user host with the IP address of 192.168.1.2.
The fifth step: the user host receives the response message and accesses the target website according to the address information (namely 18.1.1.1) carried in the response message.
To this end, the forwarding device completes the resolution of domain name www.123.com.
Referring to fig. 3, fig. 3 is a hardware structure diagram of a load balancing apparatus according to an exemplary embodiment of the present application.
The load balancing apparatus includes: a communication interface 301, a processor 302, a machine-readable storage medium 303, and a bus 304; wherein the communication interface 301, the processor 302, and the machine-readable storage medium 303 communicate with each other via a bus 304. The processor 302 may perform the traffic scheduling method described above by reading and executing machine-executable instructions in the machine-readable storage medium 303 corresponding to domain name resolution control logic.
The machine-readable storage medium 303 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 303 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.
The methods provided herein are described above. The following describes the apparatus provided in the present application:
referring to fig. 4, fig. 4 is a block diagram illustrating a domain name resolution apparatus according to an exemplary embodiment of the present application. The apparatus may be applied to the forwarding device shown in fig. 3, and the apparatus may include:
a receiving unit 401, configured to receive a DNS request packet sent by the user host; the DNS request message carries domain name information of a target website to be accessed;
a first searching unit 402, configured to search, based on a preset DNS resolution record, address information of a target website corresponding to the domain name information; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website;
a response unit 403, configured to, if the address information is found, return the address information of the target website to the user host, so that the user host accesses the target website based on the address information.
Optionally, the apparatus further comprises:
an obtaining unit 404 (not shown in the figure), configured to obtain a source address of the DNS request packet before analyzing the domain name information based on the preset DNS resolution record to obtain address information of a target website corresponding to the domain name information;
a judging unit 405 (not shown in the figure) for checking whether the source address is an address of a specified subscriber host;
a second searching unit 406 (not shown in the figure), configured to search, based on a preset DNS resolution record, address information of a target website corresponding to the domain name information if the source address is an address of a specified user host;
a forwarding unit 407 (not shown in the figure), configured to forward the DNS request message if it is checked that the source address is not the address of the specified subscriber host.
An adding unit 408 (not shown in the figure), configured to query, if the address information is not found, the DNS server for address information corresponding to the domain name information, return the address information to the user host, and add, in the DNS resolution record, a correspondence between the address information obtained by the query and the domain name information of the target website.
As an embodiment, the device is applied to the gateway equipment of the local area network where the user host is located.
Thus, the block diagram of the apparatus shown in fig. 4 is completed.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A method for domain name resolution is applied to forwarding equipment, wherein the forwarding equipment is located in a local area network where a user host is located, and the method comprises the following steps:
receiving a DNS request message sent by the user host; the DNS request message carries domain name information of a target website to be accessed;
searching address information of a target website corresponding to the domain name information based on a preset DNS analysis record; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website;
if the address information is found, returning the address information of the target website to the user host, so that the user host accesses the target website based on the address information.
2. The method according to claim 1, wherein before the analyzing the domain name information based on the preset DNS resolution record to obtain the address information of the target website corresponding to the domain name information, the method further comprises:
acquiring a source address of the DNS request message;
checking whether the source address is the address of a specified subscriber host;
and if so, executing the preset DNS analysis record, and searching address information of the target website corresponding to the domain name information.
3. The method of claim 2, further comprising:
and if not, forwarding the DNS request message.
4. The method according to claim 1, wherein the forwarding device is a gateway device of a local area network in which the user host is located.
5. The method of claim 1, further comprising:
if the address information cannot be found, inquiring the address information corresponding to the domain name information from a DNS server, returning the address information to the user host, and adding the corresponding relation between the address information obtained by inquiry and the domain name information of the target website into the DNS analysis record.
6. A device for domain name resolution is applied to forwarding equipment, wherein the forwarding equipment is located in a local area network where a user host is located, and the device comprises:
a receiving unit, configured to receive a DNS request packet sent by the user host; the DNS request message carries domain name information of a target website to be accessed;
the first searching unit is used for searching address information of a target website corresponding to the domain name information based on a preset DNS analysis record; the DNS analysis record comprises the corresponding relation between the domain name information and the address information of each website;
and the response unit is used for returning the address information of the target website to the user host if the address information is found so as to enable the user host to access the target website based on the address information.
7. The apparatus of claim 6, further comprising:
an obtaining unit, configured to obtain a source address of the DNS request packet before analyzing the domain name information based on the preset DNS analysis record to obtain address information of a target website corresponding to the domain name information;
a judging unit for checking whether the source address is the address of the specified subscriber host;
and the second searching unit is used for searching the address information of the target website corresponding to the domain name information based on a preset DNS analysis record if the source address is the address of the specified user host.
8. The apparatus of claim 7, further comprising:
and the forwarding unit is used for forwarding the DNS request message if the source address is not the address of the specified user host.
9. The apparatus according to claim 6, wherein the forwarding device is a gateway device of a local area network in which the user host is located.
10. The apparatus of claim 6, further comprising:
and the adding unit is used for inquiring the address information corresponding to the domain name information from the DNS if the address information cannot be found, returning the address information to the user host, and adding the corresponding relation between the address information obtained by inquiry and the domain name information of the target website into the DNS analysis record.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175628.4A CN110933156A (en) | 2019-11-26 | 2019-11-26 | Domain name resolution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175628.4A CN110933156A (en) | 2019-11-26 | 2019-11-26 | Domain name resolution method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110933156A true CN110933156A (en) | 2020-03-27 |
Family
ID=69851158
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911175628.4A Pending CN110933156A (en) | 2019-11-26 | 2019-11-26 | Domain name resolution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110933156A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111629079A (en) * | 2020-04-29 | 2020-09-04 | 四川速宝网络科技有限公司 | System and device for realizing network access acceleration |
| CN111885217A (en) * | 2020-07-21 | 2020-11-03 | 深信服科技股份有限公司 | Data communication method, device, equipment and storage medium |
| CN112866430A (en) * | 2021-01-19 | 2021-05-28 | 北京嘀嘀无限科技发展有限公司 | Domain name filing detection system, method, apparatus, storage medium, and computer program product |
| CN113783975A (en) * | 2021-09-24 | 2021-12-10 | 中国第一汽车股份有限公司 | Request management method, device, medium and equipment based on local DNS (Domain name Server) |
| CN113935438A (en) * | 2021-12-14 | 2022-01-14 | 杭州海康威视数字技术股份有限公司 | Internet of things equipment anomaly detection method, system and device based on equipment roles |
| CN113992626A (en) * | 2021-10-22 | 2022-01-28 | 浪潮思科网络科技有限公司 | Method, device and storage medium for realizing DNS |
| CN115378906A (en) * | 2022-08-16 | 2022-11-22 | 北京轻网科技股份有限公司 | VPN framework-based local DNS proxy method, device, equipment and medium |
| CN115473869A (en) * | 2022-08-15 | 2022-12-13 | 中国电信股份有限公司 | Data processing method and device for domain name |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100199188A1 (en) * | 2008-12-05 | 2010-08-05 | Suhayya Abu-Hakima | Auto-discovery of diverse communications devices for alert broadcasting |
| CN101873358A (en) * | 2010-06-11 | 2010-10-27 | 杭州华三通信技术有限公司 | Method and device for balancing link load on basis of domain name resolution |
| CN103973834A (en) * | 2014-05-12 | 2014-08-06 | 重庆邮电大学 | Domain name resolution (DNS) acceleration method and device based on home gateway |
-
2019
- 2019-11-26 CN CN201911175628.4A patent/CN110933156A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100199188A1 (en) * | 2008-12-05 | 2010-08-05 | Suhayya Abu-Hakima | Auto-discovery of diverse communications devices for alert broadcasting |
| CN101873358A (en) * | 2010-06-11 | 2010-10-27 | 杭州华三通信技术有限公司 | Method and device for balancing link load on basis of domain name resolution |
| CN103973834A (en) * | 2014-05-12 | 2014-08-06 | 重庆邮电大学 | Domain name resolution (DNS) acceleration method and device based on home gateway |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111629079A (en) * | 2020-04-29 | 2020-09-04 | 四川速宝网络科技有限公司 | System and device for realizing network access acceleration |
| CN111629079B (en) * | 2020-04-29 | 2023-02-28 | 四川速宝网络科技有限公司 | System and device for realizing network access acceleration |
| CN111885217A (en) * | 2020-07-21 | 2020-11-03 | 深信服科技股份有限公司 | Data communication method, device, equipment and storage medium |
| CN111885217B (en) * | 2020-07-21 | 2023-11-07 | 深信服科技股份有限公司 | Data communication method, device, equipment and storage medium |
| CN112866430B (en) * | 2021-01-19 | 2023-02-24 | 北京嘀嘀无限科技发展有限公司 | Domain name record detection system, method, device and storage medium |
| CN112866430A (en) * | 2021-01-19 | 2021-05-28 | 北京嘀嘀无限科技发展有限公司 | Domain name filing detection system, method, apparatus, storage medium, and computer program product |
| CN113783975A (en) * | 2021-09-24 | 2021-12-10 | 中国第一汽车股份有限公司 | Request management method, device, medium and equipment based on local DNS (Domain name Server) |
| CN113992626A (en) * | 2021-10-22 | 2022-01-28 | 浪潮思科网络科技有限公司 | Method, device and storage medium for realizing DNS |
| CN113935438B (en) * | 2021-12-14 | 2022-04-26 | 杭州海康威视数字技术股份有限公司 | Internet of things equipment anomaly detection method, system and device based on equipment roles |
| CN113935438A (en) * | 2021-12-14 | 2022-01-14 | 杭州海康威视数字技术股份有限公司 | Internet of things equipment anomaly detection method, system and device based on equipment roles |
| CN115473869A (en) * | 2022-08-15 | 2022-12-13 | 中国电信股份有限公司 | Data processing method and device for domain name |
| CN115378906A (en) * | 2022-08-16 | 2022-11-22 | 北京轻网科技股份有限公司 | VPN framework-based local DNS proxy method, device, equipment and medium |
| CN115378906B (en) * | 2022-08-16 | 2024-02-13 | 北京轻网科技股份有限公司 | Local DNS proxy method, device, equipment and medium based on VPN framework |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110933156A (en) | Domain name resolution method and device | |
| EP2556438B1 (en) | Reverse dns lookup with modified reverse mappings | |
| US9525749B2 (en) | DNS server arrangement and method | |
| CN111245972B (en) | Domain name resolution method, device, medium and equipment | |
| JP5150769B2 (en) | Updating routing information using request routing and client location information | |
| US12192165B2 (en) | Message forwarding and domain name address querying | |
| EP2666281B1 (en) | Domain name system server | |
| CN102469167B (en) | Domain name query implementing method and system | |
| US7573903B2 (en) | IPv6/IPv4 translator | |
| CN101656765A (en) | Address mapping system and data transmission method of identifier/locator separation network | |
| EP2093960A1 (en) | Network architecture of mutiple address spaces, and method for host information register and data transmission | |
| CN103701957A (en) | Domain name server (DNS) recursive method and system thereof | |
| CN104144123B (en) | Access method, system and the route type gateway apparatus of internet | |
| US9954815B2 (en) | Domain name collaboration service using domain name dependency server | |
| CN105376344A (en) | Method and system for analyzing recursive domain name server related to source address | |
| US12069023B2 (en) | Domain name system services for variable-length address networks | |
| CN110677512B (en) | Address resolution method and device | |
| CN100419729C (en) | A content server system and its processing procedure | |
| CN111953802A (en) | A method, system, device and storage medium for resolving domain names | |
| CN117294675A (en) | Method, device and equipment for inquiring IP (Internet protocol) based on identification DNS (Domain name System) inquiry request | |
| Bajko | Locating IEEE 802.21 mobility services using DNS | |
| CN116800718B (en) | Domain name query method, device, non-volatile storage medium and electronic device | |
| CN114866508B (en) | Domain name resolution method, domain name-based data processing method and device | |
| van Zyl et al. | A review of current DNS TTL practices | |
| CN102263832A (en) | Method and device for realizing intercommunication between International protocol version 4 (IPv4) single-stack equipment and International protocol version 6 (IPv6) single-stack 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200327 |
|
| RJ01 | Rejection of invention patent application after publication |