CN107360274A - Domain name life span computational methods, device and domain name inquiry method and device - Google Patents
Domain name life span computational methods, device and domain name inquiry method and device Download PDFInfo
- Publication number
- CN107360274A CN107360274A CN201710813617.9A CN201710813617A CN107360274A CN 107360274 A CN107360274 A CN 107360274A CN 201710813617 A CN201710813617 A CN 201710813617A CN 107360274 A CN107360274 A CN 107360274A
- Authority
- CN
- China
- Prior art keywords
- domain name
- time
- ttl
- flex
- client
- 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.)
- Granted
Links
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
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/58—Caching of addresses or names
Abstract
The invention discloses a kind of domain name life span computational methods, device and a kind of domain name inquiry method and device, when to client feedback TTL, on the basis of the accurate out-of-service time, a flex time is chosen in default flex time window, and according to accurate out-of-service time and flex time and and to current time during client feedback, calculate elastic TTL.Therefore, the out-of-service time that client calculates is based on elastic TTL.So, when client is before domain name failure, when concentrating to domain name resolution server transmission domain name inquiry request, can be on the basis of the different out-of-service times, thus, can avoid client concentrate on a period of time in send domain name inquiry request, avoid server moment overload cause normal service interrupt or delay the problem of.
Description
Technical field
The present invention relates to internet arena, more particularly to a kind of domain name life span computational methods, device and a kind of domain name
Querying method and device.
Background technology
TTL (English full name：Time-To-Live, Chinese full name：Life span), it is that a domain name mapping is recorded in DNS
RT in server.The dns server of various regions understands the dns server that specified to domain name after analysis request is received
Analysis request is sent so as to obtain solution new record；After this record is obtained, when record can preserve one section in the dns server
Between, if being during this period of time connected to analysis request again, dns server will directly return to the record obtained just now；And this is remembered
The time retained on a dns is recorded, is exactly ttl value.
In some cases, domain name resolution server can be sent when receiving inquiry of the domain name request to forwarding server
Inquiry of the domain name is asked, and after forwarding server obtains Query Result, TTL and Query Result can be sent into domain name resolution service
Device, domain name resolution server can equally feed back to the TTL client, so will result in client the domain name out-of-service time it
Before concentrate to domain name resolution server and send domain name inquiry request, as shown in figure 1, domain name resolution server is inscribed in a period of time
The request received increases severely, and peak value occurs, and so may result in existing server moment overload causes normal service to interrupt or prolong
The problem of slow.
The content of the invention
In view of this, the embodiments of the invention provide a kind of domain name life span computational methods, device and a kind of domain name to look into
Method and device is ask, can when client is before domain name failure, concentrates to domain name resolution server transmission domain name inquiry request
To be on the basis of the different out-of-service times, thus, it is possible to which avoiding client from concentrating on sends inquiry of the domain name in a period of time
Request, avoid server moment overload cause normal service interrupt or delay the problem of.
A kind of domain name life span computational methods provided in an embodiment of the present invention, including:
When receiving inquiry of the domain name result and standard TTL, failure is calculated according to the standard TTL and the first current time
Time；
A flex time is randomly selected in default flex time window；
According to the flex time and out-of-service time and and the second current time, calculate elastic TTL.
A kind of domain name life span computing device provided in an embodiment of the present invention, including：
First out-of-service time computing unit, for when receiving inquiry of the domain name result and standard TTL, according to the standard
TTL and current time calculate the out-of-service time；
Flex time chooses unit, for randomly selecting a flex time in default flex time window；
Elastic TTL time calculating units, for the flex time of selection to be added with the out-of-service time, obtain elasticity
TTL。
A kind of domain name inquiry method provided in an embodiment of the present invention, including：
When resolution server receives the inquiry of the domain name result and standard TTL of forwarding server transmission, according to the mark
Quasi- TTL and current time calculate the out-of-service time；
When receiving the inquiry request of domain name of client transmission, randomly selected in default flex time window
One flex time, by the flex time of selection with it is described be to be added the out-of-service time, obtain elastic TTL；
The Query Result and the elastic TTL are sent to the client.
Optionally, in addition to：
The client sends domain name inquiry request to the resolution server again according to the elastic TTL.
Optionally, in addition to：
The resolution server sends domain name inquiry request to the forwarding server.
A kind of inquiry of the domain name device provided in an embodiment of the present invention, including：
Second out-of-service time computing unit, for receiving the inquiry of the domain name knot of forwarding server transmission when resolution server
Fruit and during standard TTL, the out-of-service time is calculated according to the standard TTL and current time；
Second flex time computing unit, when receiving the inquiry request of domain name of client transmission, default
Flex time window in randomly select a flex time, by the flex time of selection with it is described be to be added the out-of-service time, obtain
Elastic TTL；
Transmitting element, for the Query Result and the elastic TTL to be sent into the client.
Optionally, in addition to：
First query unit, for when the client is according to the elastic TTL, being sent again to the resolution server
Domain name inquiry request.
Optionally, in addition to：
Second query unit, domain name inquiry request is sent to the forwarding server for the resolution server.
In the embodiment of the present invention, when to client feedback TTL, on the basis of the accurate out-of-service time, in default bullet
Property time window in choose a flex time, and according to accurate out-of-service time and flex time and and to client feedback
When current time, calculate elastic TTL.Therefore, the out-of-service time that client calculates is based on elastic TTL.This
Sample, can be with difference when client is before domain name failure, concentrates to domain name resolution server transmission domain name inquiry request
Out-of-service time on the basis of, thus, it is possible to avoid client concentrate on a period of time in send domain name inquiry request, avoid taking
The problem of business device moment overload causes normal service to interrupt or postpone.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
The embodiment of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can also basis
The accompanying drawing of offer obtains other accompanying drawings.
Fig. 1 shows that client concentrates the schematic diagram that request is sent to domain name resolution server；
Fig. 2 shows a kind of schematic flow sheet of domain name life span computational methods provided in an embodiment of the present invention；
Fig. 3 shows the schematic diagram of flex time window；
Fig. 4 shows a kind of structural representation of domain name life span computing device provided in an embodiment of the present invention；
Fig. 5 shows a kind of schematic flow sheet of domain name inquiry method provided in an embodiment of the present invention；
Fig. 6 shows a kind of structural representation of inquiry of the domain name device provided in an embodiment of the present invention；
Fig. 7 shows a kind of test result schematic diagram provided in an embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, rather than whole embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained every other under the premise of creative work is not made
Embodiment, belong to the scope of protection of the invention.
With reference to figure 2, a kind of schematic flow sheet of domain name life span computational methods provided in an embodiment of the present invention is shown,
In the present embodiment, this method includes：
S201：When receiving inquiry of the domain name result and standard TTL, according to the standard TTL and the first current time count
Calculate the out-of-service time；
Illustrate：When client sends domain name inquiry request to domain name resolution server, if domain name resolution server
In can not inquire the domain name, domain name resolution server can send domain name inquiry request, transfer server to transfer server
Inquiry of the domain name result is sent to domain name resolution server, while TTL is sent to domain name resolution server, now domain name mapping
The TTL that server obtains is accurate TTL, is expressed as standard TTL in the present embodiment.Also, the domain name resolution server will
Obtained Query Result is cached.
Wherein, the Query Result cached in domain name resolution server is that having time limits, more than regular hour, caching
Inquiry of the domain name result will be deleted.Out-of-service time is equal to the sum of TTL and current time, wherein, the first current time is domain
Name resolution server receives the inquiry of the domain name result of forwarding server transmission and standard TTL time.
It should be noted that the out-of-service time obtained in S201 is the accurate out-of-service time.
S202：A flex time is randomly selected in default flex time window；
S203：According to the flex time and standard failure time and and the second current time, calculate elastic TTL.
As shown in figure 3, a flex time window can be added after the out-of-service time, the flex time window is default bullet
The property out-of-service time.A flex time is chosen in the flex time window, then elastic TTL computational methods are：Flex time adds
The upper out-of-service time subtracts the second current time.Wherein, the second current time is：It is somebody's turn to do when client is sent to domain name resolution server
During the inquiry request of domain name, domain name resolution server feeds back to the Query Result of caching the time of client.
In the present embodiment, when needing every time to client feedback elasticity TTL, flex time all randomly selects, i.e., not
Flex time corresponding to the TTL received with client may be different, due to when the domain name out-of-service time, which is equal to TTL, adds current
Between, therefore out-of-service time of domain name that different clients is calculated is different, but all clients are calculated
Out-of-service time of domain name be all between accurate out-of-service time and elastic failure time.Wherein the elastic failure time is equal to standard
The true out-of-service time adds the total time of flex time window.
Illustrate：When client sends domain name inquiry request to domain name resolution server, if domain name resolution server
In when being cached with the inquiry of the domain name result, the Query Result of the domain name and elastic TTL are sent to client.Afterwards, client
Domain name inquiry request may be sent to domain name resolution server according to elastic TTL again, generally, client may
Domain name analysis request can be sent to domain name resolution server again before the domain name reaches the out-of-service time, but due to difference
Client obtained out-of-service time of domain name it is different, therefore be not concentrated in a period of time and sent to domain name resolution server
Inquiry of the domain name is asked.
In the present embodiment, when to client feedback TTL, on the basis of the accurate out-of-service time, when default elastic
Between choose a flex time in window, and according to accurate out-of-service time and flex time and and to during client feedback
Current time, calculate elastic TTL.Therefore, the out-of-service time that client calculates be based on elastic TTL, so, when
Client can be with different mistakes when concentrating to domain name resolution server transmission domain name inquiry request before domain name failure
On the basis of imitating the time, thus, it is possible to which avoiding client from concentrating on sends domain name inquiry request in a period of time, server is avoided
The problem of moment overload causes normal service to interrupt or postpone.
With reference to figure 4, a kind of structural representation of domain name life span computing device provided in an embodiment of the present invention is shown,
In this embodiment, the device includes：
First out-of-service time computing unit 401, for when receiving inquiry of the domain name result and standard TTL, according to described
Standard TTL and current time calculate the out-of-service time；
Flex time chooses unit 402, for randomly selecting a flex time in default flex time window；
Elastic TTL time calculating units 403, for the flex time of selection to be added with the out-of-service time, obtain bullet
Property TTL.
By the device of the present embodiment, client can be avoided to concentrate on domain name inquiry request is sent in a period of time, kept away
Exempt from the problem of server moment overload causes normal service to interrupt or postpone.
With reference to figure 5, a kind of schematic flow sheet of domain name inquiry method provided in an embodiment of the present invention is shown, in this implementation
In example, this method includes：
S501：When resolution server receives the inquiry of the domain name result and standard TTL of forwarding server transmission, according to institute
State standard TTL and current time calculates the out-of-service time；
S502：When receive client transmission domain name inquiry request when, in default flex time window with
Machine chooses a flex time, and the flex time of selection is added with the out-of-service time, obtains elastic TTL；
S503：The Query Result and the elastic TTL are sent to the client.
In the present embodiment when client receives the elastic TTL of domain name resolution server transmission, the present embodiment also includes：
The client sends domain name inquiry request to the resolution server again according to the elastic TTL.
In the present embodiment, before S501 is performed, in addition to：
The resolution server sends domain name inquiry request to the forwarding server.
Illustrate：When client to domain name resolution server send domain name inquiry request, if can not again domain name mapping take
When inquiring the Query Result of the domain name in business device, the inquiry that domain name resolution server sends the domain name to forwarding server please
Ask, after inquiry of the domain name request is inquired, the Query Result of the domain name and standard TTL are sent to domain name mapping by forwarding server
Server, domain name resolution server calculate standard TTL and current time the out-of-service time of the domain name, when default elastic
Between randomly select a flex time in window, by the flex time of selection with it is described be to be added the out-of-service time, obtain elastic TTL,
And the Query Result and the elastic TTL are sent to client.Wherein, the client mentioned in the present embodiment is probably an end
Be also likely to be multiple client, when to multiple client feedback characteristics TTL, due to the selection of each elastic upper time be with
Machine, therefore, domain name resolution server is different in the TTL mutually fed back in the same time to different clients, and these clients obtain
To domain name out-of-service time be also it is different, when these clients again to client send domain name inquiry request when, will
Avoid concentrating in a period of time and occur.
In addition, when the buffered Query Result and standard TTL of domain name in domain name resolution server, if having again
When client is to domain name resolution server transmission domain name inquiry request, an elasticity is randomly selected in default flex time window
Time, by the flex time of selection with it is described be to be added the out-of-service time, obtain elastic TTL, and by the Query Result and the elasticity
TTL is sent to client.Because flex time obtains at random, when to different clients feedback characteristics TTL, the bullet of selection
The property time be probably it is different, out-of-service time of the domain name that these clients obtain be also it is different, when these clients again
When sending domain name inquiry request to client, it will avoid concentrating on generation in a period of time.
In the present embodiment, when client is before domain name failure, concentrating please to domain name resolution server transmission inquiry of the domain name
Can be on the basis of the different out-of-service times, thus, it is possible to avoid client from concentrating on sending domain in a period of time when asking
Name inquiry request, avoid server moment overload cause normal service interrupt or delay the problem of.
With reference to figure 6, a kind of structural representation of inquiry of the domain name device provided in an embodiment of the present invention is shown, in this implementation
In, the device includes：
Second out-of-service time computing unit 601, the domain name for receiving forwarding server transmission when resolution server are looked into
When asking result and standard TTL, the out-of-service time is calculated according to the standard TTL and current time；
Second flex time computing unit 602, when receiving the inquiry request of domain name of client transmission, pre-
If flex time window in randomly select a flex time, by the flex time of selection with it is described be to be added the out-of-service time, obtain
To elastic TTL；
Transmitting element 603, for the Query Result and the elastic TTL to be sent into the client.
Optionally, in addition to：
First query unit, for when the client is according to the elastic TTL, being sent again to the resolution server
Domain name inquiry request.
Optionally, in addition to：
Second query unit, domain name inquiry request is sent to the forwarding server for the resolution server.
By the device of the present embodiment, client can be avoided to concentrate on domain name inquiry request is sent in a period of time, kept away
Exempt from the problem of server moment overload causes normal service to interrupt or postpone.
With reference to figure 7, the method for being directed to the present invention, different clients are because the obtained out-of-service time is different, again to domain
The time of name resolution server request is also different, and the change of peak value may be referred to shown in Fig. 7, and as shown in Figure 7, peak value diminishes, peak
The existence time of value is also elongated, thus, it is possible to which avoiding client from concentrating on sends domain name inquiry request in a period of time, avoids taking
The problem of business device moment overload causes normal service to interrupt or postpone.
It should be noted that each embodiment in this specification is described by the way of progressive, each embodiment weight
Point explanation is all difference with other embodiment, between each embodiment identical similar part mutually referring to.
The foregoing description of the disclosed embodiments, professional and technical personnel in the field are enable to realize or using the present invention.
A variety of modifications to these embodiments will be apparent for those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, it is of the invention
The embodiments shown herein is not intended to be limited to, and is to fit to and principles disclosed herein and features of novelty phase one
The most wide scope caused.
Claims (8)
- A kind of 1. domain name life span computational methods, it is characterised in that including:When receiving inquiry of the domain name result and standard TTL, when calculating failure according to the standard TTL and the first current time Between；A flex time is randomly selected in default flex time window；According to the flex time and out-of-service time and and the second current time, calculate elastic TTL.
- A kind of 2. domain name life span computing device, it is characterised in that including：First out-of-service time computing unit, for when receiving inquiry of the domain name result and standard TTL, according to the standard TTL The out-of-service time is calculated with current time；Flex time chooses unit, for randomly selecting a flex time in default flex time window；Elastic TTL time calculating units, for the flex time of selection to be added with the out-of-service time, obtain elastic TTL.
- A kind of 3. domain name inquiry method, it is characterised in that including：When resolution server receives the inquiry of the domain name result and standard TTL of forwarding server transmission, according to the standard TTL The out-of-service time is calculated with current time；When receiving the inquiry request of domain name of client transmission, one is randomly selected in default flex time window Flex time, by the flex time of selection with it is described be to be added the out-of-service time, obtain elastic TTL；The Query Result and the elastic TTL are sent to the client.
- 4. according to the method for claim 3, it is characterised in that also include：The client sends domain name inquiry request to the resolution server again according to the elastic TTL.
- 5. according to the method for claim 3, it is characterised in that also include：The resolution server sends domain name inquiry request to the forwarding server.
- A kind of 6. inquiry of the domain name device, it is characterised in that including：Second out-of-service time computing unit, for when resolution server receive forwarding server transmission inquiry of the domain name result and During standard TTL, the out-of-service time is calculated according to the standard TTL and current time；Second flex time computing unit, when receiving the inquiry request of domain name of client transmission, in default bullet Randomly select a flex time in property time window, by the flex time of selection with it is described be to be added the out-of-service time, obtain elasticity TTL；Transmitting element, for the Query Result and the elastic TTL to be sent into the client.
- 7. device according to claim 6, it is characterised in that also include：First query unit, for when the client is according to the elastic TTL, send again to the resolution server described in Inquiry of the domain name is asked.
- 8. device according to claim 6, it is characterised in that also include：Second query unit, domain name inquiry request is sent to the forwarding server for the resolution server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710813617.9A CN107360274B (en) | 2017-09-11 | 2017-09-11 | Domain name survival time calculation method and device and domain name query method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710813617.9A CN107360274B (en) | 2017-09-11 | 2017-09-11 | Domain name survival time calculation method and device and domain name query method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107360274A true CN107360274A (en) | 2017-11-17 |
| CN107360274B CN107360274B (en) | 2021-02-09 |
Family
ID=60290989
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710813617.9A Active CN107360274B (en) | 2017-09-11 | 2017-09-11 | Domain name survival time calculation method and device and domain name query method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107360274B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101656753A (en) * | 2008-08-21 | 2010-02-24 | 中国移动通信集团公司 | Content synchronization method, equipment and system for dynamic content delivery |
| CN102025795A (en) * | 2010-01-22 | 2011-04-20 | 中国移动通信集团北京有限公司 | DNS response message processing method, DNS server and system |
| CN102469167A (en) * | 2010-11-01 | 2012-05-23 | 中国移动通信集团北京有限公司 | Domain name query implementing method and system |
| CN104598261A (en) * | 2013-10-30 | 2015-05-06 | 三星Sds株式会社 | Apparatus and method of executing update, recording medium using the same, and server and method of providing update |
| CN106790469A (en) * | 2016-12-09 | 2017-05-31 | 中国联合网络通信集团有限公司 | A kind of buffer control method, device and system |
-
2017
- 2017-09-11 CN CN201710813617.9A patent/CN107360274B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101656753A (en) * | 2008-08-21 | 2010-02-24 | 中国移动通信集团公司 | Content synchronization method, equipment and system for dynamic content delivery |
| CN102025795A (en) * | 2010-01-22 | 2011-04-20 | 中国移动通信集团北京有限公司 | DNS response message processing method, DNS server and system |
| CN102469167A (en) * | 2010-11-01 | 2012-05-23 | 中国移动通信集团北京有限公司 | Domain name query implementing method and system |
| CN104598261A (en) * | 2013-10-30 | 2015-05-06 | 三星Sds株式会社 | Apparatus and method of executing update, recording medium using the same, and server and method of providing update |
| CN106790469A (en) * | 2016-12-09 | 2017-05-31 | 中国联合网络通信集团有限公司 | A kind of buffer control method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107360274B (en) | 2021-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Shaikh et al. | On the effectiveness of DNS-based server selection | |
| US9794216B2 (en) | Request routing in a networked environment | |
| US7877510B2 (en) | Domain name resolution making IP address selections in response to connection status when multiple connections are present | |
| US9083743B1 (en) | Managing request routing information utilizing performance information | |
| CN105516391B (en) | A kind of DNS name resolution method based on CNAME | |
| US9106701B2 (en) | Request routing management based on network components | |
| US9712484B1 (en) | Managing request routing information utilizing client identifiers | |
| US8862740B2 (en) | Host-level policies for global server load balancing | |
| US8938526B1 (en) | Request routing management based on network components | |
| CN109155793B (en) | Method and system for network mapping in content distribution networks | |
| US6996616B1 (en) | HTML delivery from edge-of-network servers in a content delivery network (CDN) | |
| US20150098333A1 (en) | An Iterative Optimization Method for Site Selection in Global Load Balance | |
| US10958501B1 (en) | Request routing information based on client IP groupings | |
| US20120072600A1 (en) | Managing content delivery network service providers | |
| US20090006531A1 (en) | Client request based load balancing | |
| CN103825975A (en) | Cdn node distribution server and system | |
| EP1814283A1 (en) | Accessing distributed services in a network | |
| WO2011040947A1 (en) | Content delivery utilizing multiple content delivery networks | |
| WO2009085465A1 (en) | System and method for selecting an optimal authoritative name server | |
| CN102244613A (en) | DNS (domain name system)-based multilink traffic balancing method, gateway and network | |
| US20100121914A1 (en) | Contents delivery system and method based on content delivery network provider and replication server thereof | |
| US8719216B2 (en) | Caching of web form post-query requests | |
| CN104144223B (en) | A kind of data capture method and device | |
| CN106487807A (en) | A kind of means of defence of domain name mapping and device | |
| US11750521B2 (en) | System and method for determining capacity of a telecommunications network |
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 |