CN109462667B - Domain name list acquisition method and related device - Google Patents
Domain name list acquisition method and related device Download PDFInfo
- Publication number
- CN109462667B CN109462667B CN201811237871.XA CN201811237871A CN109462667B CN 109462667 B CN109462667 B CN 109462667B CN 201811237871 A CN201811237871 A CN 201811237871A CN 109462667 B CN109462667 B CN 109462667B
- Authority
- CN
- China
- Prior art keywords
- domain name
- name list
- name server
- list
- routing
- 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.)
- Active
Links
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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Abstract
The disclosure provides a domain name list acquisition method and a related device, and relates to the technical field of network communication. The method comprises the steps that when a cache domain name list does not exist, gateway equipment sends a first unicast routing notification message to a domain name server corresponding to a domain name server address, and receives a first routing request message sent by the domain name server, wherein the domain name server sends the first routing request message when the cache domain name list is not carried in the first unicast routing notification message, the first routing request message carries the domain name list in the domain name server, the domain name list in the domain name server is cached, and the domain name list in the domain name server is used as the cache domain name list. The gateway equipment can dynamically acquire and cache the domain name list in the domain name server through interaction with the domain name server, so that manual configuration of a large number of domain name lists is reduced, and configuration efficiency of the domain name lists is improved.
Description
Technical Field
The present disclosure relates to the field of network communication technologies, and in particular, to a domain name list acquisition method and a related apparatus.
Background
In an IPv6(Internet Protocol Version 6, sixth edition) networking, a Host may obtain an address prefix and a default gateway through an RA (Router Advertisement) message sent by a gateway device, and other configurations, such as DNS (Domain Name System ) information, need to be obtained through a DHCP (Dynamic Host Configuration Protocol) or the like, which increases Configuration complexity in networking. At present, a domain name list which needs to be issued through an RA message is generally configured on gateway equipment through a static configuration mode, but the mode of manually configuring the domain name list is complicated, and particularly when the domain name list on a DNS server changes, the domain name list configured on the gateway equipment also needs to be manually and synchronously modified.
Disclosure of Invention
The invention aims to provide a domain name list acquisition method and a related device, wherein a gateway device can dynamically acquire and cache a domain name list in a domain name server through interaction with the domain name server, so that manual configuration of a large number of domain name lists is reduced, and the configuration efficiency of the domain name list is improved.
In order to achieve the above purpose, the technical scheme adopted by the disclosure is as follows:
in a first aspect, the present disclosure provides a method for obtaining a domain name list, where the method is applied to a gateway device, and a domain name server address is preconfigured on the gateway device, and the method includes: when a cache domain name list does not exist in the gateway equipment, sending a first unicast routing notification message to a domain name server corresponding to the domain name server address; receiving a first routing request message sent by the domain name server, wherein the domain name server sends the first routing request message when the first unicast routing notification message does not carry the cache domain name list, and the first routing request message carries the domain name list in the domain name server; caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list.
In a second aspect, the present disclosure provides a method for obtaining a domain name list, which is applied to a domain name server, and the method includes: receiving a first unicast routing notification message sent by gateway equipment according to a pre-configured domain name server address, wherein the domain name server address corresponds to the domain name server; and when the first unicast routing notification message does not carry a cached domain name list, sending a first routing request message to the gateway device, wherein the first routing request message carries the domain name list in the domain name server, so that the gateway device caches the domain name list in the domain name server and takes the domain name list in the domain name server as the cached domain name list.
In a third aspect, the present disclosure further provides a device for acquiring a domain name list, where the device is applied to a gateway device, and a domain name server address is preconfigured on the gateway device, and the device includes: a routing advertisement message sending module, configured to send a first unicast routing advertisement message to a domain name server corresponding to the domain name server address when a cached domain name list does not exist in the gateway device; a routing request message receiving module, configured to receive a first routing request message sent by the domain name server, where the domain name server sends the first routing request message when the first unicast routing notification message does not carry the cached domain name list, and the first routing request message carries a domain name list in the domain name server; and the domain name list caching module is used for caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list.
In a fourth aspect, the present disclosure further provides a domain name list obtaining apparatus, which is applied to a domain name server, and the apparatus includes: a routing notification message receiving module, configured to receive a first unicast routing notification message sent by a gateway device according to a preconfigured domain name server address, where the domain name server address corresponds to a domain name server; a routing request packet sending module, configured to send a first routing request packet to the gateway device when the first unicast routing advertisement packet does not carry a cached domain name list, where the first routing request packet carries a domain name list in the domain name server, so that the gateway device caches the domain name list in the domain name server and takes the domain name list in the domain name server as the cached domain name list.
In a fifth aspect, the present disclosure also proposes a computer-readable storage medium, on which a computer program is stored, which computer program, when read and executed by a first processor, implements the method of the first aspect.
In a sixth aspect, the present disclosure also proposes a computer-readable storage medium, on which a computer program is stored, which computer program, when read and executed by a second processor, implements the method of the second aspect described above.
In a seventh aspect, the present disclosure also provides a gateway device, including a computer-readable storage medium storing a computer program and a first processor, where the computer program is read by the first processor and executed to implement the method of the first aspect.
In an eighth aspect, the present disclosure further provides a domain name server, including a computer-readable storage medium storing a computer program and a second processor, where the computer program is read by the second processor and executed to implement the method according to the second aspect.
The method for obtaining the domain name list and the related device provided by the disclosure are characterized in that a domain name server address is configured on a gateway device in advance, when a cache domain name list does not exist in the gateway device, a first unicast routing notification message is sent to a domain name server corresponding to the domain name server address, and a first routing request message sent by the domain name server is received, wherein the domain name server sends the first routing request message when the cache domain name list is not carried in the first unicast routing notification message, the first routing request message carries the domain name list in the domain name server, the domain name list in the domain name server is cached, and the domain name list in the domain name server is used as the cache domain name list. In the application, the gateway device can dynamically acquire and cache the domain name list in the domain name server through interaction with the domain name server, so that manual configuration of a large number of domain name lists is reduced, and configuration efficiency of the domain name lists is improved.
Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the disclosure. The objectives and other advantages of the disclosure may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
To more clearly illustrate the technical solutions of the present disclosure, the drawings needed for the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present disclosure, and therefore should not be considered as limiting the scope, and those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 shows an application environment schematic diagram of a domain name list obtaining method and apparatus provided by the present disclosure.
Fig. 2 shows a block diagram of a gateway device provided by the present disclosure.
Fig. 3 shows a block diagram of a domain name server provided by the present disclosure.
Fig. 4 shows a flowchart of a domain name list obtaining method applied to a gateway device according to the present disclosure.
Fig. 5 shows another flowchart of the domain name list obtaining method applied to the gateway device provided by the present disclosure.
Fig. 6 shows a flowchart of a domain name list obtaining method applied to a domain name server according to the present disclosure.
Fig. 7 shows another flowchart of the domain name list obtaining method applied to the domain name server provided by the present disclosure.
Fig. 8 shows a functional block diagram of a first domain name list acquiring apparatus provided by the present disclosure.
Fig. 9 shows a functional block diagram of a second domain name list acquisition apparatus provided by the present disclosure.
Icon: 100-a gateway device; 200-a domain name server; 300-a terminal device; 400-first domain name list obtaining means; 500-second domain name list obtaining means; 110 — a first memory; 120-a first processor; 130-a first communication interface; 210-a second memory; 220-a second processor; 230-a second communication interface; 410-route advertisement message sending module; 420-routing request message receiving module; 430-domain name list caching module; 440-a judgment module; 510-a route advertisement message receiving module; 520-routing request message sending module.
Detailed Description
The technical solutions in the present disclosure will be described clearly and completely with reference to the accompanying drawings in the present disclosure, and it is to be understood that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The components of the present disclosure, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present disclosure, presented in the figures, is not intended to limit the scope of the claimed disclosure, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the disclosure without making creative efforts, shall fall within the protection scope of the disclosure.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Fig. 1 is a schematic view of an application environment of a method and an apparatus for obtaining a domain name list according to the present disclosure. The gateway device 100 is in communication connection with the domain name server 200 and the plurality of terminal devices 300, where the gateway device 100 and the plurality of terminal devices 300 are located in a local area network, and the domain name server 200 and the gateway device 100 may be in the same local area network or in different local area networks from the gateway device 100. In this embodiment, the gateway device 100 interacts with the domain name server 200, and can dynamically acquire the domain name list configured in the domain name server 200, and multicast the acquired domain name list to the plurality of terminal devices 300 periodically for use by the plurality of terminal devices 300.
In this embodiment, the gateway device 100 may be a switch, a router, or the like, the terminal device 300 may be a smart phone, a tablet computer, a Personal Computer (PC), a Mobile Internet Device (MID), a Personal Digital Assistant (PDA), or the like, and the domain name server 200 is configured to provide a domain name resolution function for the terminal device 300.
As shown in fig. 2, a block diagram of a gateway device 100 provided by the present disclosure is shown. The gateway device 100 may include a first memory 110, a first processor 120, and a first communication interface 130, where the first memory 110, the first processor 120, and the first communication interface 130 are electrically connected to each other directly or indirectly to enable data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The first memory 110 may be used to store software programs and modules, such as program instructions/modules corresponding to the method and apparatus for obtaining a domain name list applied to the gateway device 100 provided in the present disclosure, and the first processor 120 executes various functional applications and data processing by executing the software programs and modules stored in the first memory 110. The first communication interface 130 may be used for communicating signaling or data with other node devices.
The first Memory 110 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.
The first processor 120 may be an integrated circuit chip having signal processing capabilities. The first Processor 120 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
It will be appreciated that the configuration shown in fig. 2 is merely illustrative and that gateway apparatus 100 may include more or fewer components than shown in fig. 2 or may have a different configuration than shown in fig. 2. The components shown in fig. 2 may be implemented in hardware, software, or a combination thereof.
The present disclosure also provides a computer-readable storage medium on which a computer program is stored, which, when executed by the first processor 120, implements the domain name list acquisition method applied to the gateway apparatus 100 disclosed in the present disclosure.
As shown in fig. 3, a block diagram of a domain name server 200 is provided for the present disclosure. The domain name server 200 may include a second memory 210, a second processor 220, and a second communication interface 230, the second memory 210, the second processor 220, and the second communication interface 230 being electrically connected to each other directly or indirectly to enable data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The second memory 210 may be used to store software programs and modules, such as program instructions/modules corresponding to the method and apparatus for obtaining a domain name list applied to the domain name server 200 provided in the present disclosure, and the second processor 220 executes various functional applications and data processing by executing the software programs and modules stored in the second memory 210. The second communication interface 230 may be used for communication of signaling or data with other node devices.
The second Memory 210 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (Read Only Memory,
ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), electrically Erasable Programmable Read-Only Memory (EEPROM), and the like.
The second processor 220 may be an integrated circuit chip having signal processing capabilities. The second Processor 220 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
It is to be understood that the configuration shown in fig. 3 is merely illustrative, and that domain name server 200 may include more or fewer components than shown in fig. 3, or have a different configuration than shown in fig. 3. The components shown in fig. 3 may be implemented in hardware, software, or a combination thereof.
The present disclosure also provides a computer-readable storage medium on which a computer program is stored, which, when executed by the second processor 220, implements the domain name list acquisition method disclosed by the present disclosure applied to the domain name server 200.
Fig. 4 is a schematic flow chart of a domain name list obtaining method provided in the present disclosure. It should be noted that the domain name list obtaining method according to the present disclosure is not limited by fig. 4 and the specific sequence described below, and it should be understood that, in other embodiments, the sequence of some steps in the domain name list obtaining method according to the present disclosure may be interchanged according to actual needs, or some steps may be omitted or deleted. The domain name list obtaining method can be applied to the gateway device 100 described above, and a detailed description will be given below of a specific flow shown in fig. 4.
Step S101, when the cached domain name list does not exist in the gateway device 100, sending a first unicast routing notification packet to the domain name server 200 corresponding to the domain name server address.
In this embodiment, the gateway device 100 is configured with the domain name server address of the domain name server 200 in advance, and when the cached domain name list is not cached in the gateway device 100, the gateway device 100 sends the first unicast routing notification packet with the destination address being the domain name server address to the domain name server 200. The first unicast routing advertisement message carries an RDNSS (Recursive DNS Server) option and does not carry a DNS Search List (DNS Search List) option, the RDNSS option is used for recording a domain name Server address, and the DNS ssl option is used for recording a cache domain name List.
In this embodiment, the domain name server address may be a local link address or a global unicast address. When the domain name server address configured on the gateway device 100 is a local link address, the source address of the first unicast routing advertisement message uses the local link address of the gateway device 100, and when the domain name server address configured on the gateway device 100 is a global unicast address, the source address of the first unicast routing advertisement message uses a global unicast address corresponding to the output interface of the gateway device 100.
Step S102, receiving a first routing request packet sent by the domain name server 200, where the domain name server 200 sends the first routing request packet when the first unicast routing notification packet does not carry the cached domain name list, and the first routing request packet carries the domain name list in the domain name server 200.
In this embodiment, a domain name list is pre-configured in the domain name server 200, when receiving the first unicast routing notification message, the domain name server 200 finds that the DNS server specified by the gateway device 100 is itself according to the domain name server address in the RDNSS option, and the first unicast routing notification message does not carry a DNSSL option, and sends a first routing request message with a destination address of the gateway device 100 and the first routing request message carrying a DNSSL option, which records the domain name list in the domain name server 200, to the gateway device 100.
Step S103, caching the domain name list in the domain name server 200 and using the domain name list in the domain name server 200 as the cached domain name list.
In this embodiment, when receiving the first routing request packet sent by the domain name server 200, the gateway device 100 caches the DNSSL option, and uses the domain name list in the domain name server 200 recorded in the DNSSL option as the cached domain name list in the gateway device 100.
In this embodiment, the gateway device 100 performs message interaction with the domain name server 200, and can dynamically acquire and cache the domain name list from the domain name server 200, thereby avoiding the trouble of manually configuring the domain name list on the gateway device 100, improving the domain name list configuration efficiency, and reducing the labor cost. When the domain name list on the domain name server 200 changes, the gateway device 100 may dynamically update the cached domain name list, as shown in fig. 5, where the method for obtaining the domain name list further includes:
step S104, a multicast route notification message is sent every other first preset time, wherein the multicast route notification message carries the domain name server address and the cache domain name list.
In this embodiment, when the cache domain name list exists in the gateway device 100, the multicast route notification packet sent by the gateway device 100 every first preset time may be received by all the terminal devices 300 in the local area network. The multicast routing notification message carries an RDNSS option and a DNSSL option, the domain name server address is recorded in the RDNSS option, the cached domain name list is recorded in the DNSSL option, and the terminal device 300 can obtain and use the domain name server address and the cached domain name list through the RDNSS option and the DNSSL option.
Step S105, determining whether the domain name server address is a local link address or a global unicast address.
In the present embodiment, when the domain name server address configured on the gateway device 100 is the local link address, step S106 is performed, and when the domain name server address configured on the gateway device 100 is the global unicast address, step S108 is performed.
Step S106, receiving a second routing request packet sent by the domain name server 200, where the domain name server 200 sends the second routing request packet when the domain name server address is a local link address and a domain name list in the domain name server 200 changes relative to the cache domain name list, and the second routing request packet carries a first new domain name list in the domain name server 200.
In this embodiment, when the domain name server address is a local link address, it indicates that the domain name server 200, the gateway device 100 and the plurality of terminal devices 300 are in the same local area network, and both the domain name server 200 and the plurality of terminal devices 300 may receive the multicast route notification message sent by the gateway device 100. After receiving the multicast routing notification packet, the domain name server 200 determines whether the cached domain name lists recorded in the DNSSL option carried in the multicast routing notification packet are consistent with each other, and if not, indicates that the domain name lists in the domain name server 200 have changed, constructs a second routing request packet with a destination address of the gateway device 100, and sends the second routing request packet to the gateway device 100, where the second routing request packet carries the DNSSL option and the DNSSL option records the domain name list (i.e., a first new domain name list) changed in the domain name server 200.
Step S107, updating the cached domain name list to the first new domain name list.
In this embodiment, when receiving the second routing request packet sent by the domain name server 200, the gateway device 100 updates the cached domain name list, which is cached originally, to the first new domain name list recorded in the DNSSL option carried in the second routing request packet.
Step S108, when the domain name server address is a global unicast address, sending a second unicast routing notification message to the domain name server 200 at intervals of a second preset time, where the second unicast routing notification message carries the cached domain name list.
In this embodiment, when the domain name server address is a global unicast address, it indicates that the domain name server 200 and the gateway device 100 are not in the same local area network, so that the domain name server 200 cannot receive the multicast route notification packet sent by the gateway device 100. In order to facilitate the domain name server 200 to compare the cache domain name list in the gateway device 100 with the domain name list in the domain name server 200, the gateway device 100 needs to send a second unicast routing notification packet to the domain name server 200 at intervals of a second preset time, where the second routing notification packet carries an RDNSS option and a DNSSL option, an address of the domain name server is recorded in the RDNSS option, and the cache domain name list in the gateway device 100 is recorded in the DNSSL option.
Step S109, receiving a third routing request message sent by the domain name server 200, where the domain name server 200 sends the third routing request message when a domain name list in the domain name server 200 changes relative to the cached domain name list, and the third routing request message carries a second new domain name list in the domain name server 200.
In this embodiment, after receiving the second unicast routing advertisement message, the domain name server 200 determines whether the cached domain name lists recorded in the dns option carried in the second unicast routing advertisement message are consistent with each other, and if not, it indicates that the domain name list in the domain name server 200 has changed, constructs a third routing request message with a destination address of the gateway device 100, and sends the third routing request message to the gateway device 100, where the third routing request message carries the dns option, and the dns option records the domain name list (i.e., a second new domain name list) changed in the domain name server 200.
Step S110, updating the cached domain name list to the second new domain name list.
In this embodiment, when receiving the third routing request packet sent by the domain name server 200, the gateway device 100 updates the cached domain name list that is originally cached to a second new domain name list recorded in the DNSSL option carried in the third routing request packet.
As can be seen, the gateway device 100 performs message interaction with the domain name server 200, so that not only can the domain name list be dynamically acquired, but also the cached domain name list can be automatically updated to the new domain name list in the domain name server 200 when the domain name list in the domain name server 200 changes, which reduces the manual configuration caused by the change of the domain name list compared with the prior art.
Fig. 6 is a schematic flow chart of a domain name list obtaining method provided in the present disclosure. It should be noted that the domain name list obtaining method according to the present disclosure is not limited by fig. 6 and the specific sequence described below, and it should be understood that, in other embodiments, the sequence of some steps in the domain name list obtaining method according to the present disclosure may be interchanged according to actual needs, or some steps may be omitted or deleted. The domain name list obtaining method can be applied to the domain name server 200, and the specific flow shown in fig. 6 will be described in detail below.
Step S201, receiving a first unicast routing notification packet sent by the gateway device 100 according to a preconfigured domain name server address, where the domain name server address corresponds to the domain name server 200.
In this embodiment, when the cached domain name list does not exist in the gateway device 100, the gateway device 100 will send a first unicast routing advertisement packet to the domain name server 200.
Step S202, when the first unicast routing advertisement message does not carry a cached domain name list, sending a first routing request message to the gateway device 100, where the first routing request message carries the domain name list in the domain name server 200, so that the gateway device 100 caches the domain name list in the domain name server 200 and uses the domain name list in the domain name server 200 as the cached domain name list.
In this embodiment, when receiving the first unicast routing advertisement message, the domain name server 200 finds that the DNS server specified by the gateway device 100 is itself, and the first unicast routing advertisement message does not carry a DNS option, and then sends the first routing request message with the destination address as the gateway device 100 and the first routing request message carrying a DNS option to the gateway device 100, where the DNS option records a domain name list in the domain name server 200, and when receiving the first routing request message, the gateway device 100 caches the DNS option, and uses the domain name list in the domain name server 200 recorded in the DNS option as a cached domain name list in the gateway device 100.
Further, as shown in fig. 7, the method for acquiring a domain name list further includes:
step S203, when the domain name server address is a local link address, receiving a multicast routing notification packet sent by the gateway device 100 every other first preset time, where the multicast routing notification packet carries the domain name server address and the cache domain name list.
In this embodiment, when the cached domain name list exists in the gateway device 100, a multicast routing advertisement message is periodically sent, where the multicast routing advertisement message carries an RDNSS option and a DNSSL option, and a domain name server address recorded in the RDNSS option and the cached domain name list recorded in the DNSSL option are available for the terminal device 300 in the local area network to use. When the address of the domain name server configured in the gateway device 100 is a local link address, the domain name server 200 may receive the multicast route advertisement packet, and determine whether the cached domain name list recorded in the DNSSL option is consistent with the domain name list in the local device.
Step S204, when the domain name list in the domain name server 200 changes relative to the cached domain name list, sending a second routing request message to the gateway device 100, where the second routing request message carries the first new domain name list in the domain name server 200, so that the gateway device 100 updates the cached domain name list to the first new domain name list.
In this embodiment, when the domain name list in the domain name server 200 changes relative to the cached domain name list, the domain name server 200 sends a second routing request packet with a destination address of the gateway device 100 to the gateway device 100, where the second routing request packet carries a DNSSL option, and the domain name list with the changed DNSSL option (i.e., a first new domain name list) is recorded in the DNSSL option, and when receiving the second routing request packet sent by the domain name server 200, the gateway device 100 updates the cached domain name list, which is originally cached, to a first new domain name list recorded in the DNSSL option carried by the second routing request packet.
Step S205, when the domain name server address is a global unicast address, receiving a second unicast routing notification packet sent every second preset time by the gateway device 100, where the second unicast routing notification packet carries the cache domain name list.
In this embodiment, when the address of the domain name server configured in the gateway device 100 is a global unicast address, the domain name server 200 cannot receive the multicast routing notification packet sent by the gateway device 100, and the gateway device 100 needs to periodically send a second unicast routing notification packet to the domain name server 200, so that the domain name server 200 compares the cache domain name list in the gateway device 100 with the domain name list in the domain name server 200.
Step S206, when the domain name list in the domain name server 200 changes relative to the cached domain name list, sending a third routing request message to the gateway device 100, where the third routing request message carries a second new domain name list in the domain name server 200, so that the gateway device 100 updates the cached domain name list to the second new domain name list.
In this embodiment, when the domain name list in the domain name server 200 changes relative to the cached domain name list, the domain name server 200 sends a third routing request message to the gateway device 100, where the third routing request message carries a DNSSL option, and the domain name list with the changed destination address (i.e., a second new domain name list) is recorded in the DNSSL option, and when receiving the third routing request message sent by the domain name server 200, the gateway device 100 updates the cached domain name list, which is originally cached, to the second new domain name list recorded in the DNSSL option carried by the third routing request message.
It should be noted that, in this embodiment, when the domain name list in the domain name server 200 changes, the domain name server 200 may also actively send the routing request packet to the gateway device 100, and record the changed domain name list in the DNSSL option of the routing request packet.
Fig. 8 is a functional block diagram of a first domain name list obtaining apparatus 400 according to the present disclosure. It should be noted that the basic principle and the generated technical effect of the first domain name list obtaining apparatus 400 provided in this embodiment are the same as those of the foregoing method embodiment, and for a brief description, no mention part in this embodiment may refer to the corresponding contents in the foregoing domain name list obtaining method embodiment applied to the gateway device 100. The first domain name list obtaining device 400 is a domain name list obtaining device applied to the gateway apparatus 100, and includes at least one software functional module that can be stored in the first memory 110 in a form of software or firmware (firmware) or solidified in an Operating System (OS) of the gateway apparatus 100. The first domain name list obtaining apparatus 400 includes a routing advertisement message sending module 410, a routing request message receiving module 420, a domain name list caching module 430, and a determining module 440.
The routing advertisement packet sending module 410 is configured to send a first unicast routing advertisement packet to the domain name server 200 corresponding to the domain name server address when the cached domain name list does not exist in the gateway device 100.
It is understood that the route advertisement message sending module 410 may execute the step S101.
The routing request packet receiving module 420 is configured to receive a first routing request packet sent by the domain name server 200, where the domain name server 200 sends the first routing request packet when the first unicast routing notification packet does not carry the cached domain name list, and the first routing request packet carries the domain name list in the domain name server 200.
It is understood that the routing request message receiving module 420 may execute the step S102.
The domain name list caching module 430 is configured to cache the domain name list in the domain name server 200 and use the domain name list in the domain name server 200 as the cached domain name list.
It is understood that the domain name list caching module 430 may perform the step S103.
Further, in this embodiment, the routing advertisement message sending module 410 is further configured to send a multicast routing advertisement message at intervals of a first preset time, where the multicast routing advertisement message carries the domain name server address and the cache domain name list.
It is understood that the route advertisement message sending module 410 may also perform the step S104.
The determining module 440 is configured to determine whether the domain name server address is a local link address or a global unicast address.
It is understood that the determining module 440 can execute the above step S105.
The routing request packet receiving module 420 is further configured to receive a second routing request packet sent by the domain name server 200, where the domain name server 200 sends the second routing request packet when the domain name server address is a local link address and a domain name list in the domain name server 200 changes relative to the cache domain name list, and the second routing request packet carries a first new domain name list in the domain name server 200.
It is understood that the routing request message receiving module 420 may also execute the step S106.
The domain name list caching module 430 is further configured to update the cached domain name list to the first new domain name list.
It is understood that the domain name list caching module 430 may also perform the step S107.
The routing advertisement message sending module 410 is further configured to send a second unicast routing advertisement message to the domain name server 200 every second preset time when the domain name server address is the global unicast address, where the second unicast routing advertisement message carries the cached domain name list.
It is understood that the route advertisement message sending module 410 may also execute the step S108.
The routing request message receiving module 420 is further configured to receive a third routing request message sent by the domain name server 200, where the domain name server 200 sends the third routing request message when a domain name list in the domain name server 200 changes relative to the cache domain name list, and the third routing request message carries a second new domain name list in the domain name server 200.
It is understood that the routing request message receiving module 420 may also execute the step S109.
The domain name list caching module 430 is further configured to update the cached domain name list to the second new domain name list.
It is understood that the domain name list caching module 430 can also perform the step S110.
Fig. 9 is a schematic functional block diagram of a second domain name list obtaining apparatus 500 provided in the present disclosure. It should be noted that the basic principle and the technical effect of the second domain name list obtaining apparatus 500 provided in the present embodiment are the same as those of the foregoing method embodiment, and for a brief description, no mention part in the present embodiment may refer to the corresponding contents in the foregoing domain name list obtaining method embodiment applied to the domain name server 200. The second domain name list acquiring apparatus 500 is a domain name list acquiring apparatus applied to the domain name server 200, and includes at least one software function module which can be stored in the second memory 210 in the form of software or firmware (firmware) or is solidified in an Operating System (OS) of the domain name server 200. The second domain name list obtaining apparatus 500 includes a routing advertisement message receiving module 510 and a routing request message sending module 520.
The route notification packet receiving module 510 is configured to receive a first unicast route notification packet sent by the gateway device 100 according to a preconfigured domain name server address, where the domain name server address corresponds to the domain name server 200.
It is understood that the route advertisement message receiving module 510 may execute the step S201.
The routing request packet sending module 520 is configured to send a first routing request packet to the gateway device 100 when the first unicast routing advertisement packet does not carry a cached domain name list, where the first routing request packet carries the domain name list in the domain name server 200, so that the gateway device 100 caches the domain name list in the domain name server 200 and uses the domain name list in the domain name server 200 as the cached domain name list.
It is understood that the routing request message sending module 520 may execute the step S202.
Further, in this embodiment, the route notification message receiving module 510 is further configured to receive, when the domain name server address is a local link address, a multicast route notification message sent every first preset time by the gateway device 100, where the multicast route notification message carries the domain name server address and the cache domain name list.
It is understood that the route advertisement message receiving module 510 may also execute the step S203.
The routing request packet sending module 520 is further configured to send a second routing request packet to the gateway device 100 when the domain name list in the domain name server 200 changes from the cached domain name list, where the second routing request packet carries the first new domain name list in the domain name server 200, so that the gateway device 100 updates the cached domain name list to the first new domain name list.
It is understood that the routing request message sending module 520 may also execute the step S204.
In this embodiment, the routing advertisement message receiving module 510 is further configured to receive, when the domain name server address is a global unicast address, a second unicast routing advertisement message sent every second preset time by the gateway device 100, where the second unicast routing advertisement message carries the cached domain name list.
It is understood that the route advertisement message receiving module 510 may also execute the step S205.
The routing request packet sending module 520 is further configured to send a third routing request packet to the gateway device 100 when the domain name list in the domain name server 200 changes from the cached domain name list, where the third routing request packet carries a second new domain name list in the domain name server 200, so that the gateway device 100 updates the cached domain name list into the second new domain name list.
It is understood that the routing request message sending module 520 may also execute the step S206.
In summary, according to the method and the related apparatus for obtaining a domain name list provided by the present disclosure, a domain name server address is preconfigured on a gateway device, and when a cached domain name list does not exist in the gateway device, a first unicast routing notification message is sent to a domain name server corresponding to the domain name server address, and a first routing request message sent by the domain name server is received, where the domain name server sends the first routing request message when the first unicast routing notification message does not carry the cached domain name list, and the first routing request message carries a domain name list in the domain name server, caches the domain name list in the domain name server, and takes the domain name list in the domain name server as the cached domain name list. In the application, the gateway device can dynamically acquire and cache the domain name list in the domain name server through interaction with the domain name server, so that manual configuration of a large number of domain name lists is reduced, and configuration efficiency of the domain name lists is improved. In addition, the gateway device sends a multicast routing notification message periodically or sends a second unicast routing notification message periodically to the domain name server, the domain name server judges whether a domain name list in the domain name server changes relative to a cache domain name list carried by the multicast routing notification message or the second unicast routing notification message, and when the domain name list changes, a new domain name list is carried in a routing request message and sent to the gateway device, so that the gateway device can dynamically update the cache domain name list when the domain name list in the domain name server changes.
As will be appreciated by one skilled in the art, the present disclosure may be provided as a method, apparatus, device or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, devices and computer program products according to the present disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In the several embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus and method embodiments described above are illustrative only, as the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules 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 disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several 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 disclosure. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing is illustrative of only alternative embodiments of the present disclosure and is not intended to limit the disclosure, which may be modified and varied by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Claims (12)
1. A method for obtaining a domain name list is applied to gateway equipment, and a domain name server address is configured on the gateway equipment in advance, and the method is characterized by comprising the following steps:
when a cache domain name list does not exist in the gateway equipment, sending a first unicast routing notification message to a domain name server corresponding to the domain name server address;
receiving a first routing request message sent by the domain name server, wherein the domain name server sends the first routing request message when the first unicast routing notification message does not carry the cache domain name list, and the first routing request message carries the domain name list in the domain name server;
caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list.
2. The method of claim 1, wherein after the step of caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list, the method further comprises:
sending a multicast routing notification message at intervals of a first preset time, wherein the multicast routing notification message carries the domain name server address and the cache domain name list;
receiving a second routing request message sent by the domain name server, wherein the domain name server sends the second routing request message when the address of the domain name server is a local link address and a domain name list in the domain name server changes relative to the cache domain name list, and the second routing request message carries a first new domain name list in the domain name server;
and updating the cache domain name list into the first new domain name list.
3. The method of claim 1, wherein after the step of caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list, the method further comprises:
when the address of the domain name server is a global unicast address, sending a second unicast routing notification message to the domain name server at intervals of second preset time, wherein the second unicast routing notification message carries the cache domain name list;
receiving a third routing request message sent by the domain name server, wherein the domain name server sends the third routing request message when a domain name list in the domain name server changes relative to the cache domain name list, and the third routing request message carries a second new domain name list in the domain name server;
and updating the cache domain name list into the second new domain name list.
4. A domain name list acquisition method is applied to a domain name server, and is characterized by comprising the following steps:
receiving a first unicast routing notification message sent by gateway equipment according to a pre-configured domain name server address, wherein the domain name server address corresponds to the domain name server;
and when the first unicast routing notification message does not carry a cached domain name list, sending a first routing request message to the gateway device, wherein the first routing request message carries the domain name list in the domain name server, so that the gateway device caches the domain name list in the domain name server and takes the domain name list in the domain name server as the cached domain name list.
5. The method of obtaining a list of domain names according to claim 4, wherein the method further comprises:
when the domain name server address is a local link address, receiving a multicast routing notification message sent by the gateway device every other first preset time, wherein the multicast routing notification message carries the domain name server address and the cache domain name list;
when the domain name list in the domain name server changes relative to the cache domain name list, sending a second routing request message to the gateway device, wherein the second routing request message carries a first new domain name list in the domain name server, so that the gateway device updates the cache domain name list into the first new domain name list.
6. The method of obtaining a list of domain names according to claim 4, wherein the method further comprises:
when the domain name server address is a global unicast address, receiving a second unicast routing notification message sent by the gateway device every second preset time, wherein the second unicast routing notification message carries the cache domain name list;
when the domain name list in the domain name server changes relative to the cache domain name list, sending a third routing request message to the gateway device, where the third routing request message carries a second new domain name list in the domain name server, so that the gateway device updates the cache domain name list into the second new domain name list.
7. A domain name list acquisition device is applied to gateway equipment, and a domain name server address is configured on the gateway equipment in advance, and the device is characterized by comprising:
a routing advertisement message sending module, configured to send a first unicast routing advertisement message to a domain name server corresponding to the domain name server address when a cached domain name list does not exist in the gateway device;
a routing request message receiving module, configured to receive a first routing request message sent by the domain name server, where the domain name server sends the first routing request message when the first unicast routing notification message does not carry the cached domain name list, and the first routing request message carries a domain name list in the domain name server;
and the domain name list caching module is used for caching the domain name list in the domain name server and taking the domain name list in the domain name server as the cached domain name list.
8. A domain name list acquiring apparatus, applied to a domain name server, the apparatus comprising:
a routing notification message receiving module, configured to receive a first unicast routing notification message sent by a gateway device according to a preconfigured domain name server address, where the domain name server address corresponds to a domain name server;
a routing request packet sending module, configured to send a first routing request packet to the gateway device when the first unicast routing advertisement packet does not carry a cached domain name list, where the first routing request packet carries a domain name list in the domain name server, so that the gateway device caches the domain name list in the domain name server and takes the domain name list in the domain name server as the cached domain name list.
9. A computer-readable storage medium, on which a computer program is stored which, when read and executed by a first processor, implements the method according to any one of claims 1-3.
10. A computer-readable storage medium, on which a computer program is stored, which, when read and executed by a second processor, carries out the method according to any one of claims 4-6.
11. A gateway device, comprising a computer readable storage medium storing a computer program and a first processor, the computer program being read and executed by the first processor for implementing the method according to any one of claims 1-3.
12. A domain name server, comprising a computer readable storage medium storing a computer program and a second processor, the computer program being read and executed by the second processor for implementing the method according to any one of claims 4-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811237871.XA CN109462667B (en) | 2018-10-23 | 2018-10-23 | Domain name list acquisition method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811237871.XA CN109462667B (en) | 2018-10-23 | 2018-10-23 | Domain name list acquisition method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109462667A CN109462667A (en) | 2019-03-12 |
| CN109462667B true CN109462667B (en) | 2021-07-06 |
Family
ID=65608245
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811237871.XA Active CN109462667B (en) | 2018-10-23 | 2018-10-23 | Domain name list acquisition method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109462667B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764855A (en) * | 2009-12-30 | 2010-06-30 | 福建星网锐捷网络有限公司 | Method, device and system for providing domain name resolution services |
| CN102333131A (en) * | 2010-07-13 | 2012-01-25 | 中国电信股份有限公司 | Method for providing domain name service, system and agent DNS |
| US8280946B1 (en) * | 2003-09-10 | 2012-10-02 | Google Inc. | Reduction of perceived DNS lookup latency |
| CN103166937A (en) * | 2011-12-16 | 2013-06-19 | 中国移动通信集团公司 | Device visiting method and home gateway device inside home network |
-
2018
- 2018-10-23 CN CN201811237871.XA patent/CN109462667B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8280946B1 (en) * | 2003-09-10 | 2012-10-02 | Google Inc. | Reduction of perceived DNS lookup latency |
| CN101764855A (en) * | 2009-12-30 | 2010-06-30 | 福建星网锐捷网络有限公司 | Method, device and system for providing domain name resolution services |
| CN102333131A (en) * | 2010-07-13 | 2012-01-25 | 中国电信股份有限公司 | Method for providing domain name service, system and agent DNS |
| CN103166937A (en) * | 2011-12-16 | 2013-06-19 | 中国移动通信集团公司 | Device visiting method and home gateway device inside home network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109462667A (en) | 2019-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107733670B (en) | Forwarding strategy configuration method and device | |
| CN110784562B (en) | Message forwarding method, domain name address query method, device, equipment and medium | |
| CN111182089B (en) | Container cluster system, method and device for accessing big data assembly and server | |
| CN103534993A (en) | Label switched routing to connect low power network domains | |
| CN106210155B (en) | Method and device for connecting application server | |
| CN104093118A (en) | Resource notification method, machine-to-machine nodes and system | |
| US8989182B2 (en) | Providing a virtual domain name system (DNS) in a local area network (LAN) | |
| EP2347561A1 (en) | Methods, apparatuses, and computer program products for determining a network interface to access a network resource | |
| JP4699530B2 (en) | Methods, systems, and applications for service addressing | |
| CN109076082A (en) | Anonymous Identity in network and agreement towards identity | |
| EP2928117A1 (en) | System and method for device registration and discovery in content-centric networks | |
| US20100217655A1 (en) | Services advertisement in a wireless mesh | |
| EP2928118A1 (en) | System and method for dynamic name configuration in content-centric networks | |
| CN102035899B (en) | Method and device for determining addresses in IPv6 (internet protocol version 6) based LAN (local area network) | |
| US20230276218A1 (en) | Systems and methods for roaming configuration management | |
| CN112235408A (en) | Network system, reverse proxy method and reverse proxy server | |
| US9913074B2 (en) | Identifying resources from a device in a communications network | |
| US10298672B2 (en) | Global contact-point registry for peer network devices | |
| CN109462667B (en) | Domain name list acquisition method and related device | |
| CN102137172A (en) | Access method and access device for DNS (Domain Name Server) | |
| JP2000332813A (en) | Selection method for start point address in communication network system, selector and storage medium recording this method | |
| CN111064798A (en) | Node network access method, device, client node and storage medium | |
| EP3306899B1 (en) | Methods circuits devices systems and functionally associated computer executable code to support location based services to a wireless devices communicatively coupled to a communication network | |
| CN114124893A (en) | Domain name caching method, device, system, storage medium and computer equipment | |
| CN115004657B (en) | Addressing method, addressing system and addressing device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |