CN103380607A - DNS client address and RR TTL updating method, device and system - Google Patents

DNS client address and RR TTL updating method, device and system Download PDF

Info

Publication number
CN103380607A
CN103380607A CN2011800031729A CN201180003172A CN103380607A CN 103380607 A CN103380607 A CN 103380607A CN 2011800031729 A CN2011800031729 A CN 2011800031729A CN 201180003172 A CN201180003172 A CN 201180003172A CN 103380607 A CN103380607 A CN 103380607A
Authority
CN
China
Prior art keywords
dns
ttl
client
update
ttl value
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
Application number
CN2011800031729A
Other languages
Chinese (zh)
Other versions
CN103380607B (en
Inventor
刘冰
蒋胜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN103380607A publication Critical patent/CN103380607A/en
Application granted granted Critical
Publication of CN103380607B publication Critical patent/CN103380607B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Provided in an embodiment of the present invention is a method for updating the TTL of a DNS RR, the method comprising: a DNS authoritative server receiving a request packet transmitted by a DNS client for updating the TTL value of the RR of the DNS client, the request packet being a DNS Update message containing a TTL Update field used for identifying the TTL value of the request packet; extracting the TTL value in the request packet and changing into the extracted TTL value the TTL stored on the DNS authoritative server, and corresponding to the DNS client RR. Also provided in the embodiment of the present invention are a device and system for updating the TTL of a DNS RR. When an IP address is reallocated to a DNS client due to network restructuring or an ISP switchover, the method, device and system provided in the embodiment of the present invention can shorten the time the DNS client is inaccessible to the querying users, thereby improving network reliability.

Description

DNS client address, the method for RR TTL renewals, apparatus and system
DNS client address, the method for RR TTL renewals, apparatus and system
Technical field
The present embodiments relate to communication technical field, more particularly to a kind of domain name system（Domain Name System, DNS) client address, the time-to-live of resource record (Resource Record, RR)（Time To Live, TTL) update method, apparatus and system.
Background technology
DNS is a kind of naming system being distributed with hierarchical structure, and in the TCP/IP of such as Internet etc, (view/IP(Internet Protocol) is done in Transmission Control Protocol/Internet Protocol, transmission control ten）In network, position computer is carried out there is provided the conversion between domain name and IP address using domain name, if inputs domain name in the application, it is possible to provide the information related to domain name including IP addresses by the database in DNS servers.The entry that these information are formed in the dns server is referred to as DNS RR, and the RR also includes TTL.Generally, dns server includes DNS authority server and DNS Slow deposit server（Or have other species, such as forwarding server, iterative query server, it is unrelated to the invention to repeat no more）DNS authority server provides the data of authority, store whole DNS clients RR information, DNS Slow deposit server from DNS authority server obtain RR information and meanwhile Slow store away, the RR that can be deposited when there is user to inquire about according to its Slow return to the user required for information.RR ttl value is in the generation of DNS authority server, the TLL values are to maintain constant in DNS authority server, it will not diminish over time, DNS Slow, which are deposited, includes TTL in the RR information that server is obtained from authoritative server, this ttl value can diminish with the time, when certain RR TTL is changed into 0, the failure of this RR information from DNS authority server, it is necessary to reacquire this RR information.
Network is due to re-organized, switching ISP（Internet Service Provider, DNS client IP address in the reason such as ISP), network can be redistributed, after the relation of DNS client domain name and IP address changes, corresponding RR information will also change therewith, and this process is referred to as DNS renewals.Dynamic-dns Update update methods allow the lateral DNS authority server of DNS client to send out New information is sent, DNS authority server receives and the RR therein corresponding to the DNS client is updated after message.Because DNS client more new domain name and IP corresponding relations can only be sent to DNS authoritative servers, DNS Slow deposit server only just can actively go DNS authority server lookup when the TTL of the RR information of its preservation is reduced to 0, like this, after the IP address change of some DNS client, DNS authority server can be perceived at once, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address information of the client, so, when the client-side information is searched when there is user, then the old address of the DNS client can also be returned to inquiry user, so as to cause communication failure, inquiry user can not access the domain name of the DNS client, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for this problem, current state of the art does not have effective solution.The content of the invention
The embodiments of the invention provide a kind of DNS client address, the method for RR TTL renewals, apparatus and system, when DNS client IP address changes after network reconfiguration or ISP switchings, inquiry user, which can be efficiently reduced, can not access the time of the DNS client, be conducive to improving network reliability, to reach above-mentioned purpose, the embodiments of the invention provide a kind of method that DNS client address updates, including：
The first DNS Update are sent to DNS authority server and update message, and the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
Timer is started according to the former ttl value；
After the timer expiry, send the 2nd DNS Update to the DNS authority server and update message, the 2nd DNS Update messages include the address information after DNS client renewal；
The address for updating the DNS client is the address information after the renewal. The embodiments of the invention provide a kind of method that DNS client RR TTL update, including：DNS authority server receives the first DNS Update renewal messages that DNS client is sent, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
The former ttl value of DNS client described in the DNS authority server update is the new TTL values.
The embodiments of the invention provide the device that a kind of DNS client address updates, including：First packet sending unit, message is updated for sending the first DNS Update to DNS authority server, the first DNS Update messages include the new TTL values of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
Timer units, for starting timer according to the former ttl value；
Second packet sending unit, for when the timer expiry after, sends the 2nd DNS Update to the DNS authority server and updates message, the 2nd DNS Update messages updated comprising the DNS client after address information；
Address updating block, the address for updating the DNS client is the address information after the renewal.
The device updated the embodiments of the invention provide a kind of TTL time-to-live of DNS domain name system client RR resource records, including：
Message receiving unit, the first DNS Update renewal messages that DNS client is sent are received for DNS authority server, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former TTL values for replacing the DNS client；
Message process unit, the former ttl value for DNS client described in the DNS authority server update is the new ttl value.
The embodiments of the invention provide the system that a kind of DNS domain name system resource record RR time-to-live TTL updates, including： DNS clients, update message, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client for sending the first DNS Update；
DNS authority server, the device that the TTL time-to-live comprising a kind of DNS domain name systems client RR resource records of the invention for implementing to provide updates.
To sum up, the embodiments of the invention provide a kind of DNS client address, the method that RR TTL update, apparatus and system, pass through a kind of DNS client RR TTL update methods provided in an embodiment of the present invention, DNS client Dynamic Customization TTL function can be realized, simultaneously, the technology for providing indispensability for a kind of DNS client address renewing method that the embodiment of the present invention is carried has section, further, DNS client address renewing method provided in an embodiment of the present invention, when network causes DNS client IP address to be redistributed due to the reason such as re-organized or switching ISP, inquiry user, which can be efficiently reduced, can not access the time of the DNS client, be conducive to improving network reliability.
Brief description of the drawings is in order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, cylinder will be made to the required accompanying drawing used in embodiment or description of the prior art below singly to introduce, apparently, drawings in the following description are some embodiments of the present invention, for those of ordinary skill in the art, on the premise of not paying creative work, other accompanying drawings can also be obtained according to these accompanying drawings.
Fig. 1 is a kind of schematic flow sheet of the method for the address renewal for DNS RR that first embodiment of the invention is provided；
Fig. 2 is that a kind of DNS RR that first embodiment of the invention is provided update schematic flow sheet；Fig. 3 is a kind of DNS Update message format schematic diagrames provided in an embodiment of the present invention；Fig. 4 is the DNS Update message format schematic diagrames after a kind of extension provided in an embodiment of the present invention；Fig. 5 is a kind of method flow schematic diagram of the TTL renewals for DNS RR that second embodiment of the invention is provided；
Fig. 6 is a kind of schematic device of the address renewal for DNS RR that third embodiment of the invention is provided； Figure is a kind of schematic device of the TTL renewals for DNS RR that fourth embodiment of the invention is provided；
Fig. 8 is a kind of schematic diagram of the system of the TTL renewals for DNS RR that fifth embodiment of the invention is provided.
Specific reality formula is to make the purpose, technical scheme and advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is a part of embodiment of the invention, rather than whole embodiments.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art are obtained under the premise of creative work is not made belongs to the scope of protection of the invention.
Embodiment one：
The embodiments of the invention provide a kind of method that DNS client address updates, referring to Fig. 1, Fig. 1 is the method flow diagram of the embodiment of the present invention, including：
102, send the first DNS Update to DNS authority server and update message, the first DNS Update messages include the new ttl value of the DNS client RR information, former ttl value of the new TTL values for replacing the DNS client；
In a network due to the reason such as re-organized or switching ISP, DNS client IP address in network can be redistributed, after the IP address change of some DNS client domain name, the new domain name of DNS authority server preservation and IP corresponding relations can be notified at once by DNS Update message, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address of the DNS client and domain name corresponding relation, so, when the DNS client information is searched when there is user, DNS Slow can be first inquired about first deposits server, DNS Slow, which deposit server, can return to the old address of the DNS client inquiry user, so as to cause inquiry user can not access the DNS client, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for example, as shown in Figure 2, DNS client A domain name is www.example.com, IP Location is 123.1.1.1, and the RR information that DNS authority server and DNS Slow deposit the DNS client A of server storage includes：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds.When network reconfiguration is knitted or switches ISP, DNS client A address is updated to 234.1.1.1, DNS customer end As give DNS authority server by DNS Update message the address notification after renewal, and DNS authority server is to the RR information updatings in its RR database corresponding to DNS client A：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 36000 seconds.Because the DNS Slow RR information corresponding to DNS customer end As for depositing server preservation is：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, assuming that now TTL is reduced to 30000 seconds, do not expired so because TTL appoints, DNS Slow, which deposit server, will not go DNS authority server to obtain the RR information after the DNS clients update, so as user's B access clients A domain name www.example.com, DNS Slow, which deposit server, can return to old IP address 123.1.1.1, user B will be unable to access DNS client A, and the time that can not be accessed will continue 30000 seconds, under some scenes, DNS TTL representative value is 2 days or so, the domain name that can then cause user's highest can not be accessed for 2 days, have a strong impact on user's communication.Occur above mentioned problem main reason is that when DNS client address changes, DNS Slow deposit server preservation to should DNS client RR original TTL do not expire, the DNS client RR information of the updated address information of DNS authority server lookup will not be gone, cause DNS Slow to deposit server to expire in this period in DNS client RR original TTL, user can not access the DNS client domain name.Because DNS authoritative servers safeguard numerous DNS clients, it can not possibly realize and carry out real-time TTL adjustment for each DNS client, inventor has found by research, before network reconfiguration is knitted or switches ISP, namely before the switching of DNS client IP address, DNS client can send the first DNS Update to DNS authority server and update message, first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client.After the DNS Slow TTL for depositing the old RR of server expire, to the RR information of the updated TTL of the DNS authority server lookup correspondence DNS client, so as to after network carries out re-organized or switching ISP, that is, after DNS client IP address switches, DNS Slow deposit server New DNS client RR information can be inquired about to dns server after less new TTL is overtime in the updated, now, user can not the method DNS client time up to DNS client less new ttl value corresponding time after updating, as long as being limited new ttl value is changed, can efficiently reduce inquiry user's visit can not access the time of the DNS client.
Dynamic-dns Update technologies allow DNS client to send DNS Update messages to dns server, DNS authority server receives the RR information corresponding to the DNS clients preserved after the DNS Update messages to it and is updated, and the DNS Update messages that current dynamic-dns Update standard agreements are defined can carry out following 4 kinds of action types（Reference can be made to（ RFC2136 ):
1), increase DNS RR set.
2) DNS RR set, is deleted.
3) all DNS RR set of designated domain name, is deleted.
4), a RR is deleted from a DNS RR set.
Inventor has found that the first DNS Update messages can be a kind of message of new action type after expanding existing DNS Update messages action type by research.The blunt texts of DNS Update 4 of the action type are a kind of 4 blunt texts of the action type that dynamic updates DNS RR TTL, the message of the action type can dynamically update the DNS client RR TTL values for being stored in DNS authority server, the 4 blunt text includes TTL Update more newer fields, for identifying the DNS client new TTL to be updated.Existing DNS Update messages form such as Fig. 3, the DNS Update message forms after expansion are as shown in Figure 4.The TTL Update field lengths can be 32 bytes.The TTL Update fields can also be put into the other positions of DNS Update message, and the embodiment of the present invention does not do pressure limitation, for example, being put into TTL Update additional data Additional Data TTL Update message.
Further, the message of the action type can include TTL Effective judgement fields, it is whether effective for identifying the new ttl value, the TTL Effective judgements field can be 1 bit, when the TTL effective fields are 0, the new ttl value is invalid, and when the TTL effective fields are non-zero, the new ttl value is effective. The DNS authority server is received after the first DNS Update messages, extract the new ttl value, when judging the new ttl value to be effective, DNS authority server finds the RR information corresponding to the DNS client by the DNS client domain-name information in DNS Update message in local RR databases, and then it is the new ttl value to update the former ttl value of the DNS client RR information.
104, timer is started according to the former ttl value；
106, after the timer expiry, the 2nd DNS Update, which are sent, to the DNS authoritative servers updates message, the 2nd DNS Update messages include the address information after DNS client renewal, meanwhile, the address for updating the DNS client is the address information after the renewal；108, the address for updating the DNS client is the address information after the renewal.
After transmission the first DNS Update renewal messages to DNS authority server, the DNS clients need to start a timer, the timer duration is equal to the former TTL values or some value for the former ttl value more than the DNS client of the DNS clients, correspondingly, it is described timer is started according to the former TTL before, the RR of the DNS client former ttl value can be obtained by sending DNS Query query messages to the DNS authority server, start for the timer, the DNS Query messages may refer to RFC1035.The DNS client sends the 2nd DNS Update to the DNS authority server after the timer expiry and updates message, the 2nd DNS Update messages include the address information after DNS client renewal, meanwhile, the address for updating the DNS client is the address information after the renewal.By start the purpose of the timer be to ensure that the DNS Slow deposit server preserve the former TTL corresponding to DNS client RR expire, and from DNS authority server got updated ttl value corresponding to the DNS client RR information.
The DNS authority server is received after the 2nd DNS Update messages, extract the address information after the renewal, DNS authority server finds the RR information corresponding to the DNS client by the DNS client domain names information in DNS Update message in local RR databases, and then it is the address after the renewal to update the address information of the DNS client RR information Information.
To further illustrate the embodiment of the present invention, it is now for example bright, as shown in Fig. 2 DNS client A domain name is www.example.com, IP address is 123.1.1.1, and the RR information that DNS authority server and DNS Slow deposit the DNS customer end As of server storage includes：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds, before network reconfiguration is knitted or switches ISP, DNS client A sends DNS Query messages to DNS authority server, the former TTL of the RR in DNS authority server corresponding to DNS client A is stored in for obtaining, further, DNS authority server sends the first DNS Update and updates message, the blunt texts of first DNS Update include the new ttl value of the DNS client RR information, the new ttl value is used for the former ttl value for replacing the DNS client, the renewal ttl value is a relative small value, as this example could be arranged to 30 seconds.Meanwhile, timer is started according to the former TTL, the timer when a length of DNS client RR former ttl value.DNS authority server is received and will be updated to after the first DNS Update messages in its RR database corresponding to DNS client A RR：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 30 seconds.Deposited in DNS Slow the DNS client A of server storage RR former TTL expire after, actively go DNS authority server lookup and update DNS client A RR information, be updated to：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 30 seconds.So, DNS Slow deposit server can inquire about the RR information of DSN customer end As every 30 seconds to DNS authoritative servers, after the timer expiry, DNS customer end As start address switches, the 2nd DNS Update, which are sent, to DNS authority server updates message, 2nd DNS Update messages include the address after DNS client A renewals, simultaneously, the address for switching DNS client A is 234.1.1.1, DNS authority server is received after the 2nd DNS Update messages, the DNS client A of DNS authority server storage RR is also updated to：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 30 seconds.Because the DNS Slow TTL for depositing the DNS client A of server preservation RR are 30 seconds, therefore, DNS Slow, which deposit server, i.e. renewable DNS client A RR to be in most long 30：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 30 seconds.Therefore, in network reconfiguration or switching ISP, user B is most long Also DNS client A domain name www.example.com can not be only accessed in 30 seconds, so that DNS client A time can not be accessed by substantially reducing user B, network reliability are improved.
It can be seen that, the method for implementing to provide by the present invention, when network causes DNS client IP address to be redistributed due to the reason such as re-organized or switching ISP, can efficiently reduce inquiry user can not access the time of the DNS client, be conducive to improving network reliability.
Embodiment two：
The embodiments of the invention provide the method that the TTL of DNS client RR a kind of updates, referring to Fig. 5, Fig. 5 is the method flow diagram of the embodiment of the present invention, including：
502, DNS authority server receives the first DNS Update renewal messages that DNS client is sent, the first DNS Update messages include the new TTL values of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
In a network due to the reason such as re-organized or switching ISP, DNS client IP address in network can be redistributed, after the IP address change of some DNS client domain name, the new domain name of DNS authority server preservation and IP corresponding relations can be notified at once by DNS Update message, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address of the DNS client and domain name corresponding relation, so, when the DNS client information is searched when there is user, DNS Slow can be first inquired about first deposits server, DNS Slow, which deposit server, can return to the old address of the DNS client inquiry user, so as to cause inquiry user can not access the DNS client, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for example, as shown in Figure 2, DNS client A domain name is www.example.com, IP address is 123.1.1.1, the RR information that DNS authority server and DNS Slow deposit the DNS client A of server storage includes：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds.When network reconfiguration is knitted or switches ISP, DNS client A address is updated to 234.1.1.1, DNS customer end As give DNS authority server by DNS Update message the address notification after renewal, and DNS authority server is to the RR information updatings in its RR database corresponding to DNS client A： Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 36000 seconds.Because the DNS Slow RR information corresponding to DNS customer end As for depositing server preservation is：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, assuming that now TTL is reduced to 30000 seconds, do not expired so because TTL appoints, DNS Slow, which deposit server, will not go DNS authority server to obtain the RR information after the DNS clients update, so as user's B access clients A domain name www.example.com, DNS Slow, which deposit server, can return to old IP address 123.1.1.1, user B will be unable to access DNS client A, and the time that can not be accessed will continue 30000 seconds, under some scenes, DNS TTL representative value is 2 days or so, the domain name that can then cause user's highest can not be accessed for 2 days, have a strong impact on user's communication.Occur above mentioned problem main reason is that when DNS client address changes, DNS Slow deposit server preservation to should DNS client RR original TTL do not expire, the DNS client RR information of the updated address information of DNS authority server lookup will not be gone, cause DNS Slow to deposit server to expire in this period in DNS client RR original TTL, user can not access the DNS client domain name.Because DNS authoritative servers safeguard numerous DNS clients, it can not possibly realize and carry out real-time TTL adjustment for each DNS client, inventor has found by research, before network reconfiguration is knitted or switches ISP, the first DNS Update that DNS authority server can be sent by receiving DNS client update message to update the former TTL values corresponding to the DNS client RR that DNS authority server is preserved, the first DNS Update messages include the new ttl value of the DNS client RR information, the new ttl value is used for the former ttl value for replacing the DNS client.The blunt texts of first DNS Update include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client.After the DNS Slow TTL for depositing the old RR of server expire, to the RR information of the updated TTL of the DNS authority server lookup correspondence DNS client, so as to after network carries out re-organized or switching ISP, after namely DNS client IP address switches, DNS Slow, which deposit server, new DNS client RR information is inquired about to dns server after less new TTL is overtime in the updated, now, user can not the method DNS client time up to DNS client less new ttl value corresponding time after updating, limited as long as 4 bars change new ttl value Good, can efficiently reduce inquiry user's visit can not access the time of the DNS client.
Dynamic-dns Update technologies allow DNS client to send DNS Update messages to dns server, DNS authority server receives the RR information corresponding to the DNS clients preserved after the DNS Update messages to it and is updated, and the DNS Update messages that current dynamic-dns Update standard agreements are defined can carry out following 4 kinds of action types（Reference can be made to（ RFC2136 ):
1), increase DNS RR set.
2) DNS RR set, is deleted.
3) all DNS RR set of designated domain name, is deleted.
4), a RR is deleted from a DNS RR set.
Inventor has found that the first DNS Update messages can be a kind of message of new action type after expanding existing DNS Update messages action type by research.The blunt texts of DNS Update 4 of the action type are a kind of 4 blunt texts of the action type that dynamic updates DNS RR TTL, the message of the action type can dynamically update the DNS client RR TTL values for being stored in DNS authority server, the 4 blunt text includes TTL Update more newer fields, for identifying the DNS client new TTL to be updated.Existing DNS Update messages form such as Fig. 3, the DNS Update message forms after expansion are as shown in Figure 4.The TTL Update field lengths can be 32 bytes.The TTL Update fields can also be put into the other positions of DNS Update message, and the embodiment of the present invention does not do pressure limitation, for example, being put into TTL Update additional data Additional Data TTL Update message.
Further, the message of the action type can include TTL Effective judgement fields, it is whether effective for identifying the new ttl value, the TTL Effective judgements field can be 1 bit, when the TTL effective fields are 0, the new ttl value is invalid, and when the TTL effective fields are non-zero, the new ttl value is effective.
504, the former ttl value of DNS client described in the DNS authority server update is the new ttl value.
The DNS authority server is received after the first DNS Update messages, extracts described New ttl value, when judging the new ttl value to be effective, DNS authority server finds the RR information corresponding to the DNS client by the DNS client domain-name information in DNS Update message in local RR databases, and then it is the new ttl value to update the former ttl value of the DNS client RR information.
It can be seen that, the method for implementing to provide by the present invention, it can realize that DNS client dynamically updates the ttl value that DNS Slow deposit the RR corresponding to the DNS client of server storage, realize the function of its ttl value of DNS client Dynamic Customization, especially, to realize that the embodiment of the present invention one provides indispensable technological means.
Embodiment three：
The embodiments of the invention provide the device that a kind of DNS client address updates, referring to Fig. 6, the schematic device that Fig. 6 is implemented for the present invention, the device includes：First packet sending unit 602, timer units 604, the second packet sending unit 606, address updating block 608.
First packet sending unit 602, message is updated for sending the first DNS Update to DNS authority server, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
In a network due to the reason such as re-organized or switching ISP, DNS client IP address in network can be redistributed, after the IP address change of some DNS client domain name, the new domain name of DNS authority server preservation and IP corresponding relations can be notified at once by DNS Update message, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address of the DNS client and domain name corresponding relation, so, when the DNS client information is searched when there is user, DNS Slow can be first inquired about first deposits server, DNS Slow, which deposit server, can return to the old address of the DNS client inquiry user, so as to cause inquiry user can not access the DNS client, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for example, as shown in Figure 2, DNS client A domain name is www.example.com, IP address is 123.1.1.1, DNS authority server and DNS Slow deposit the DNS client A of server storage RR information include：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds.When network reconfiguration is knitted or switches ISP, DNS client A address is updated to 234.1.1.1, DNS customer end As give DNS authority server by DNS Update message the address notification after renewal, and DNS authority server is to the RR information updatings in its RR database corresponding to DNS client A：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 36000 seconds.Because the DNS Slow RR information corresponding to DNS customer end As for depositing server preservation is：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, assuming that now TTL is reduced to 30000 seconds, do not expired so because TTL appoints, DNS Slow, which deposit server, will not go DNS authority server to obtain the RR information after the DNS clients update, so as user's B access clients A domain name www.example.com, DNS Slow, which deposit server, can return to old IP address 123.1.1.1, user B will be unable to access DNS client A, and the time that can not be accessed will continue 30000 seconds, under some scenes, DNS TTL representative value is 2 days or so, the domain name that can then cause user's highest can not be accessed for 2 days, have a strong impact on user's communication.Occur above mentioned problem main reason is that when DNS client address changes, DNS Slow deposit server preservation to should DNS client RR original TTL do not expire, the DNS client RR information of the updated address information of DNS authority server lookup will not be gone, cause DNS Slow to deposit server to expire in this period in DNS client RR original TTL, user can not access the DNS client domain name.Because DNS authoritative servers safeguard numerous DNS clients, it can not possibly realize and carry out real-time TTL adjustment for each DNS client, inventor has found by research, before network reconfiguration is knitted or switches ISP, namely before the switching of DNS client IP address, the blunt literary transmitting element 602 of DNS client the 1st can send the first DNS Update to DNS authoritative servers and update message, first DNS Update messages include the new ttl value of the DNS client RR information, the new ttl value is used for the former ttl value for replacing the DNS client.After the DNS Slow TTL for depositing the old RR of server expire, to the RR information of the updated TTL of the DNS authority server lookup correspondence DNS client, so as to after network carries out re-organized or switching ISP, after namely DNS client IP address switches, DNS Slow, which deposit server, to arrive DNS service after less new TTL is overtime in the updated Device inquires about new DNS client RR information, now, user can not the method DNS client time up to DNS client less new ttl value corresponding time after updating, as long as being limited new ttl value is changed, can efficiently reduce inquiry user's visit can not access the time of the DNS client.
Dynamic-dns Update technologies allow DNS client to send DNS Update messages to dns server, DNS authority server receives the RR information corresponding to the DNS clients preserved after the DNS Update messages to it and is updated, and the DNS Update messages that current dynamic-dns Update standard agreements are defined can carry out following 4 kinds of action types（Reference can be made to（ RFC2136 ):
1), increase DNS RR set.
2) DNS RR set, is deleted.
3) all DNS RR set of designated domain name, is deleted.
4), a RR is deleted from a DNS RR set.
Inventor has found that the first DNS Update messages can be a kind of message of new action type after expanding existing DNS Update messages action type by research.The blunt texts of DNS Update 4 of the action type are a kind of 4 blunt texts of the action type that dynamic updates DNS RR TTL, the message of the action type can dynamically update the DNS client RR TTL values for being stored in DNS authority server, the 4 blunt text includes TTL Update more newer fields, for identifying the DNS client new TTL to be updated.Existing DNS Update messages form such as Fig. 3, the DNS Update message forms after expansion are as shown in Figure 4.The TTL Update field lengths can be 32 bytes.The TTL Update fields can also be put into the other positions of DNS Update message, and the embodiment of the present invention does not do pressure limitation, for example, being put into TTL Update additional data Additional Data TTL Update message.
Further, the message of the action type can include TTL Effective judgement fields, it is whether effective for identifying the new ttl value, the TTL Effective judgements field can be 1 bit, when the TTL effective fields are 0, the new ttl value is invalid, and when the TTL effective fields are non-zero, the new ttl value is effective.
The DNS authority server is received after the first DNS Update messages, extracts described New ttl value, when judging the new ttl value to be effective, DNS authority server finds the RR information corresponding to the DNS client by the DNS client domain-name information in DNS Update message in local RR databases, and then it is the new ttl value to update the former ttl value of the DNS client RR information.
Timer units 604, for starting timer according to the former ttl value；
After the first packet sending unit 602 sends the first DNS Update renewal messages to DNS authority server, timer units 604 need to start a timer, the timer duration is equal to the former ttl value or some value for the former ttl value more than the DNS client of the DNS clients, correspondingly, one 4 blunt literary transmitting element 602 can obtain the RR of the DNS client former ttl value by sending DNS Query query messages to the DNS authority server, start for the timer, the DNS Query messages may refer to RFC 1035.
Second packet sending unit 606, for when the timer expiry after, sends the 2nd DNS Update to the DNS authority server and updates message, the 2nd DNS Update messages updated comprising the DNS client after address information；
The 2nd DNS Update being sent to the DNS authority server after the timer expiry that the timer units 604 start and updating message, the 2nd DNS Update messages include the address information after DNS client renewal.By start the purpose of the timer be to ensure that the DNS Slow deposit server preserve the former TTL corresponding to DNS client RR expire, and from DNS authority server got updated ttl value corresponding to the DNS client RR information.
The DNS authority server is received after the 2nd DNS Update messages, extract the address information after the renewal, DNS authority server finds the RR information corresponding to the DNS client by the DNS client domain names information in DNS Update message in local RR databases, and then it is the address information after the renewal to update the address information of the DNS client RR information.
Address updating block 608, the address for updating the DNS client is the address information after the renewal. While the 2nd DNS Update renewal messages being sent after the timer expiry that the timer units 604 start to the DNS authority server, the address that address updating block 608 updates the DNS client is the address information after the renewal, completes the address switching after the DNS client network reconfiguration or ISP switchings.
It can be seen that, the device for implementing to provide by the present invention, when network causes DNS client IP address to be redistributed due to the reason such as re-organized or switching ISP, can efficiently reduce inquiry user can not access the time of the DNS client, be conducive to improving network reliability.
Example IV：
The embodiments of the invention provide the device that the TTL of DNS client RR a kind of updates, referring to Fig. 7, the schematic device that Fig. 7 is implemented for the present invention, the device includes：Message receiving unit 702, message process unit 704.
Message receiving unit 702, the first DNS Update renewal messages that DNS client is sent are received for DNS authority server, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former TTL values for replacing the DNS client；
In a network due to the reason such as re-organized or switching ISP, DNS client IP address in network can be redistributed, after the IP address change of some DNS client domain name, the new domain name of DNS authority server preservation and IP corresponding relations can be notified at once by DNS Update message, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address of the DNS client and domain name corresponding relation, so, when the DNS client information is searched when there is user, DNS Slow can be first inquired about first deposits server, DNS Slow, which deposit server, can return to the old address of the DNS client inquiry user, so as to cause inquiry user can not access the DNS client, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for example, as shown in Figure 2, DNS client A domain name is www.example.com, IP address is 123.1.1.1, DNS authority server and DNS Slow deposit the DNS client A of server storage RR information include：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds.When network reconfiguration is knitted or switches ISP, DNS client A address is updated to 234.1.1.1, DNS customer end As give DNS authority server by DNS Update message the address notification after renewal, and DNS authority server is to the RR information updatings in its RR database corresponding to DNS client A：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 36000 seconds.Because the DNS Slow RR information corresponding to DNS customer end As for depositing server preservation is：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, assuming that now TTL is reduced to 30000 seconds, do not expired so because TTL appoints, DNS Slow, which deposit server, will not go DNS authority server to obtain the RR information after the DNS clients update, so as user's B access clients A domain name www.example.com, DNS Slow, which deposit server, can return to old IP address 123.1.1.1, user B will be unable to access DNS client A, and the time that can not be accessed will continue 30000 seconds, under some scenes, DNS TTL representative value is 2 days or so, the domain name that can then cause user's highest can not be accessed for 2 days, have a strong impact on user's communication.Occur above mentioned problem main reason is that when DNS client address changes, DNS Slow deposit server preservation to should DNS client RR original TTL do not expire, the DNS client RR information of the updated address information of DNS authority server lookup will not be gone, cause DNS Slow to deposit server to expire in this period in DNS client RR original TTL, user can not access the DNS client domain name.Because DNS authoritative servers safeguard numerous DNS clients, it can not possibly realize and carry out real-time TTL adjustment for each DNS client, inventor has found by research, before network reconfiguration is knitted or switches ISP, the first DNS Update that message receiving unit 702 can be sent by receiving DNS client update message to update the former TTL values corresponding to the DNS client RR that DNS authority server is preserved, the first DNS Update messages include the new ttl value of the DNS client RR information, the new ttl value is used for the former ttl value for replacing the DNS client.The blunt texts of first DNS Update include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client.After the DNS Slow TTL for depositing the old RR of server expire, the RR information of the updated TTL DNS client is corresponded to DNS authority server lookup, from And after network carries out re-organized or switching ISP, after namely DNS client IP address switches, DNS Slow, which deposit server, new DNS client RR information is inquired about to dns server after less new TTL is overtime in the updated, now, user can not the method DNS client time up to DNS client less new ttl value corresponding time after updating, limited as long as 4 bars change new ttl value, can efficiently reduce inquiry user's visit can not access the time of the DNS client.
Dynamic-dns Update technologies allow DNS client to send DNS Update messages to dns server, DNS authority server receives the RR information corresponding to the DNS clients preserved after the DNS Update messages to it and is updated, and the DNS Update messages that current dynamic-dns Update standard agreements are defined can carry out following 4 kinds of action types（Reference can be made to（ RFC2136 ):
1), increase DNS RR set.
2) DNS RR set, is deleted.
3) all DNS RR set of designated domain name, is deleted.
4), a RR is deleted from a DNS RR set.
Inventor has found that the first DNS Update messages can be a kind of message of new action type after expanding existing DNS Update messages action type by research.The blunt texts of DNS Update 4 of the action type are a kind of 4 blunt texts of the action type that dynamic updates DNS RR TTL, the message of the action type can dynamically update the DNS client RR TTL values for being stored in DNS authority server, the 4 blunt text includes TTL Update more newer fields, for identifying the DNS client new TTL to be updated.Existing DNS Update messages form such as Fig. 3, the DNS Update message forms after expansion are as shown in Figure 4.The TTL Update field lengths can be 32 bytes.The TTL Update fields can also be put into the other positions of DNS Update message, and the embodiment of the present invention does not do pressure limitation, for example, being put into TTL Update additional data Additional Data TTL Update message.
Further, the message of the action type can include TTL Effective judgement fields, it is whether effective for identifying the new ttl value, the TTL Effective judgements field can be 1 bit, when the TTL effective fields are 0, the new ttl value is invalid, when the TTL effective fields are non-zero, institute State new ttl value effective.
Message processing 704, the former ttl value for DNS client described in the DNS authority server update is the new ttl value
The Message processing 704 is parsed to the first DNS Update messages that message receiving unit 702 is received, extract the new ttl value, when judging the new ttl value to be effective, DNS authoritative servers find the RR information corresponding to the DNS client by the DNS client domain-name information in DNS Update message in local RR databases, and then it is the new ttl value to update the former ttl value of the DNS clients RR information.
It can be seen that, the device for implementing to provide by the present invention, it can realize that DNS client dynamically updates the ttl value that DNS Slow deposit the RR corresponding to the DNS client of server storage, realize the function of its ttl value of DNS client Dynamic Customization, especially, to realize that the embodiment of the present invention three provides indispensable technological means.
Embodiment five：
The embodiments of the invention provide the system that the TTL of DNS RR a kind of updates, referring to Fig. 8, the system schematic that Fig. 8 is implemented for the present invention, the system includes：DNS client 802, DNS authority server 804.
DNS client 802, updates message, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client for sending the first DNS Update；
In a network due to the reason such as re-organized or switching ISP, DNS client IP address in network can be redistributed, after the IP address change of some DNS client domain name, the new domain name of DNS authority server preservation and IP corresponding relations can be notified at once by DNS Update message, but DNS Slow deposit server because the RR of its Slow DNS clients deposited TTL does not expire also, DNS Slow deposit server and still save the old address of the DNS client and domain name corresponding relation, so, when the DNS client information is searched when there is user, DNS Slow can be first inquired about first deposits server, DNS Slow, which deposit server, can return to the old address of the DNS client inquiry user, so as to cause to inquire about user The DNS client can not be accessed, especially, when the TTL that DNS Slow deposit the DNS client RR information that server Slow is deposited is very big, inquiry user can be caused can not to access the DNS client for a long time, for example, as shown in Fig. 2 DNS client A domain name is www.example.com, IP address is 123.1.1.1, and the RR information that DNS authority server and DNS Slow deposit the DNS client A of server storage includes：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, 36000 seconds.When network reconfiguration is knitted or switches ISP, DNS client A address is updated to 234.1.1.1, DNS customer end As give DNS authority server by DNS Update message the address notification after renewal, and DNS authority server is to the RR information updatings in its RR database corresponding to DNS client A：Domain name, www.example.com; IP, 234.1.1.1 ;TTL, 36000 seconds.Because the DNS Slow RR information corresponding to DNS customer end As for depositing server preservation is：Domain name, www.example.com; IP, 123.1.1.1 ;TTL, assuming that now TTL is reduced to 30000 seconds, do not expired so because TTL appoints, DNS Slow, which deposit server, will not go DNS authority server to obtain the RR information after the DNS clients update, so as user's B access clients A domain name www.example.com, DNS Slow, which deposit server, can return to old IP address 123.1.1.1, user B will be unable to access DNS client A, and the time that can not be accessed will continue 30000 seconds, under some scenes, DNS TTL representative value is 2 days or so, the domain name that can then cause user's highest can not be accessed for 2 days, have a strong impact on user's communication.Occur above mentioned problem main reason is that when DNS client address changes, DNS Slow deposit server preservation to should DNS client RR original TTL do not expire, the DNS client RR information of the updated address information of DNS authority server lookup will not be gone, cause DNS Slow to deposit server to expire in this period in DNS client RR original TTL, user can not access the DNS client domain name.Because DNS authoritative servers safeguard numerous DNS clients, it can not possibly realize and carry out real-time TTL adjustment for each DNS client, inventor has found by research, before network reconfiguration is knitted or switches ISP, namely before the switching of DNS client IP address, DNS client can send the first DNS Update to DNS authority server and update message, first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the original for replacing the DNS client Ttl value.After the DNS Slow TTL for depositing the old RR of server expire, to the RR information of the updated TTL of the DNS authority server lookup correspondence DNS client, so as to after network carries out re-organized or switching ISP, after namely DNS client IP address switches, DNS Slow, which deposit server, new DNS client RR information is inquired about to dns server after less new TTL is overtime in the updated, now, user can not the method DNS client time up to DNS client less new ttl value corresponding time after updating, as long as being limited new ttl value is changed, inquiry user's visit, which can be efficiently reduced, can not access the time of the DNS client.
Dynamic-dns Update technologies allow DNS client to send DNS Update messages to dns server, DNS authority server receives the RR information corresponding to the DNS clients preserved after the DNS Update messages to it and is updated, and the DNS Update messages that current dynamic-dns Update standard agreements are defined can carry out following 4 kinds of action types（Reference can be made to（ RFC2136 ):
1), increase DNS RR set.
2) DNS RR set, is deleted.
3) all DNS RR set of designated domain name, is deleted.
4), a RR is deleted from a DNS RR set.
Inventor has found that the first DNS Update messages can be a kind of message of new action type after expanding existing DNS Update messages action type by research.The blunt texts of DNS Update 4 of the action type are a kind of 4 blunt texts of the action type that dynamic updates DNS RR TTL, the message of the action type can dynamically update the DNS client RR TTL values for being stored in DNS authority server, the 4 blunt text includes TTL Update more newer fields, for identifying the DNS client new TTL to be updated.Existing DNS Update messages form such as Fig. 3, the DNS Update message forms after expansion are as shown in Figure 4.The TTL Update field lengths can be 32 bytes.The TTL Update fields can also be put into the other positions of DNS Update message, and the embodiment of the present invention does not do pressure limitation, for example, being put into TTL Update additional data Additional Data TTL Update message.
Further, the message of the action type can include TTL Effective judgement fields, for identifying Whether the new ttl value is effective, and the TTL Effective judgements field can be 1 bit, when the TTL effective fields are 0, and the new ttl value is invalid, and when the TTL effective fields are non-zero, the new ttl value is effective.
DNS authority server 804, including the device that the embodiment of the present invention four is provided, can participate in the embodiment of the present invention four in detail.
One of ordinary skill in the art will appreciate that：Realizing all or part of step of above method embodiment can be completed by the related hardware of programmed instruction, and foregoing routine can be stored in a computer read/write memory medium, and the program upon execution, performs the step of including above method embodiment；And foregoing storage medium includes：ROM, RAM, magnetic disc or CD etc. are various can be with the medium of store program codes.
Finally it should be noted that：The above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations；Although the present invention is described in detail with reference to the foregoing embodiments, it will be understood by those within the art that：It can still modify to the technical scheme described in foregoing embodiments, or carry out equivalent substitution to which part technical characteristic；And these modifications or replacement, the essence of appropriate technical solution is departed from the spirit and scope of various embodiments of the present invention technical scheme.

Claims (11)

  1. Claim
    1st, a kind of method that DNS domain name system client address updates, it is characterised in that including：The first DNS Update are sent to DNS authority server and update message, and the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
    Timer is started according to the former ttl value；
    After the timer expiry, send the 2nd DNS Update to the DNS authority server and update message, the 2nd DNS Update messages include the address information after DNS client renewal；
    The address for updating the DNS client is the address information after the renewal.
    2nd, the method according to claim 1, it is characterised in that it is described timer is started according to the former TTL values before, further comprise：
    Former TTL values are obtained by sending DNS Query query messages to the DNS authority server.
    3rd, method according to claim 1 or 2, it is characterised in that the new ttl value is carried on the TTL Update more newer fields in the DNS Update messages.
    4th, the method according to Claim 1-3 any claim, it is characterised in that the duration of the timer is more than or equal to the former ttl value.
    5th, the method according to claim 1 to 4 any claim, it is characterised in that the first DNS Update messages further comprise TTL Effective judgement fields, whether the ttl value for identifying the request message is effective.
    6th, a kind of method that TTL time-to-live of DNS domain name system client RR resource records updates, it is characterised in that including：
    DNS authority server receives the first DNS Update renewal messages that DNS client is sent, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client； The former ttl value of DNS client described in the DNS authority server update is the new TTL values.
    7th, method according to claim 6, it is characterised in that including：The new ttl value is carried on the TTL Update more newer fields in the DNS Update messages.
    8th, the method according to claim 6 or 7, it is characterised in that the first DNS Update messages further comprise TTL Effective judgement fields, and the ttl value for identifying the request message is effective；Correspondingly, the former ttl value of DNS client described in the DNS authority server update is that the new ttl value is specifically included：When the TTL Effective judgements field is non-zero, the former ttl value that the DNS authoritative servers update the DNS client is the new ttl value.
    9th, the device that a kind of DNS domain name system client address updates, it is characterised in that including：First packet sending unit, message is updated for sending the first DNS Update to DNS authority server, the first DNS Update messages include the new TTL values of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client；
    Timer units, for starting timer according to the former ttl value；
    Second packet sending unit, for when the timer expiry after, sends the 2nd DNS Update to the DNS authority server and updates message, the 2nd DNS Update messages updated comprising the DNS client after address information；
    Address updating block, the address for updating the DNS client is the address information after the renewal.
    10th, the device according to claim 9, it is characterised in that first packet sending unit further comprises：
    Timer units are being triggered by being sent to the DNS authority server after DNS Query query messages obtain original TTL values.
    11st, the device that a kind of TTL time-to-live of DNS domain name system client RR resource records updates, it is characterised in that including：
    Message receiving unit, DNS client is sent first is received for DNS authority server DNS Update update message, and the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former TTL values for replacing the DNS client；
    Message process unit, the former ttl value for DNS client described in the DNS authority server update is the new ttl value.
    12nd, device according to claim 11, it is characterised in that the message receiving unit further comprises：When the TTL Effective judgements field is non-zero, the former ttl value of DNS client described in the DNS authority server update is the new ttl value.
    13rd, the system that a kind of DNS domain name system resource record RR time-to-live TTL updates, it is characterised in that the system includes：
    DNS clients, update message, the first DNS Update messages include the new ttl value of the DNS client RR information, and the new ttl value is used for the former ttl value for replacing the DNS client for sending the first DNS Update；
    DNS authority server, includes the device described in claim 11 or 12.
CN201180003172.9A 2011-12-08 2011-12-08 Method, Apparatus and system that DNS client address, RR TTL upgrade Active CN103380607B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/083717 WO2013082791A1 (en) 2011-12-08 2011-12-08 Dns client address and rr ttl updating method, device and system

Publications (2)

Publication Number Publication Date
CN103380607A true CN103380607A (en) 2013-10-30
CN103380607B CN103380607B (en) 2015-11-25

Family

ID=48573508

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201180003172.9A Active CN103380607B (en) 2011-12-08 2011-12-08 Method, Apparatus and system that DNS client address, RR TTL upgrade

Country Status (2)

Country Link
CN (1) CN103380607B (en)
WO (1) WO2013082791A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106612339A (en) * 2015-10-27 2017-05-03 中国电信股份有限公司 Domain name updating method, system and main DNS (Domain Name System) server
CN111901449A (en) * 2020-07-01 2020-11-06 四川速宝网络科技有限公司 Method and device for optimizing domain name access
CN114338604A (en) * 2021-12-31 2022-04-12 北京奇艺世纪科技有限公司 DNS configuration updating method and system

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331213B (en) * 2016-08-29 2017-11-24 广东欧珀移动通信有限公司 A kind of domain name system DNS processing method and processing device
CN110881064B (en) * 2018-09-06 2022-08-02 阿里巴巴集团控股有限公司 Domain name configuration method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030044526A (en) * 2001-11-30 2003-06-09 엘지전자 주식회사 Method for IP Address Assignment in DNS
US20050210150A1 (en) * 2004-03-19 2005-09-22 Microsoft Corporation Dynamic session maintenance for mobile computing devices
CN1694459A (en) * 2005-04-13 2005-11-09 北京交通大学 Method for updating dynamic field name in IPv6 network
CN101277257A (en) * 2007-03-26 2008-10-01 华为技术有限公司 Method, apparatus and system for dynamically updating DNS
WO2009019321A1 (en) * 2007-08-08 2009-02-12 Teliasonera Finland Oyj A method and a communications network for updating the routing data of a domain name server
CN101483648A (en) * 2009-02-20 2009-07-15 杭州华三通信技术有限公司 Method, system, apparatus and DNS server for DNS buffer probe

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030044526A (en) * 2001-11-30 2003-06-09 엘지전자 주식회사 Method for IP Address Assignment in DNS
US20050210150A1 (en) * 2004-03-19 2005-09-22 Microsoft Corporation Dynamic session maintenance for mobile computing devices
CN1694459A (en) * 2005-04-13 2005-11-09 北京交通大学 Method for updating dynamic field name in IPv6 network
CN101277257A (en) * 2007-03-26 2008-10-01 华为技术有限公司 Method, apparatus and system for dynamically updating DNS
WO2009019321A1 (en) * 2007-08-08 2009-02-12 Teliasonera Finland Oyj A method and a communications network for updating the routing data of a domain name server
CN101483648A (en) * 2009-02-20 2009-07-15 杭州华三通信技术有限公司 Method, system, apparatus and DNS server for DNS buffer probe

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106612339A (en) * 2015-10-27 2017-05-03 中国电信股份有限公司 Domain name updating method, system and main DNS (Domain Name System) server
CN111901449A (en) * 2020-07-01 2020-11-06 四川速宝网络科技有限公司 Method and device for optimizing domain name access
CN111901449B (en) * 2020-07-01 2022-07-22 四川速宝网络科技有限公司 Method and device for optimizing domain name access
CN114338604A (en) * 2021-12-31 2022-04-12 北京奇艺世纪科技有限公司 DNS configuration updating method and system
CN114338604B (en) * 2021-12-31 2024-04-12 北京奇艺世纪科技有限公司 DNS configuration updating method and system

Also Published As

Publication number Publication date
CN103380607B (en) 2015-11-25
WO2013082791A1 (en) 2013-06-13

Similar Documents

Publication Publication Date Title
US10148612B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
US6016512A (en) Enhanced domain name service using a most frequently used domain names table and a validity code table
CN101465889B (en) Network address translation equipment and request method of response address analysis protocol
CN112217916B (en) Novel caching method and system for industrial Internet identification resolution recursion server
JP3725376B2 (en) DNS inquiry apparatus, DNS inquiry method, and recording medium
CN102025794B (en) Domain name resolution method, DNS (Domain Name Server) server and system
CN101170585B (en) A domain name inquiry method
JPH0870299A (en) Target transmission in network and message target generationsystem
CN101087253A (en) Method, device, domain parsing method and device for saving domain system record
CN103380607A (en) DNS client address and RR TTL updating method, device and system
CN104717314A (en) IP management method and system, client-side and server
CN112235408A (en) Network system, reverse proxy method and reverse proxy server
CN102572011B (en) Method, device and system for processing data
Kangasharju et al. A replicated architecture for the domain name system
WO2017000561A1 (en) Domain name resource record caching control method and server
CN101237442B (en) Terminal identifier parsing and service transmission method, system and device in integrated network
CN106534390B (en) The storage and management method and system of authoritative domain name system server data
US20020199020A1 (en) Method and system for resolving names on a network gateway having multiple distinct network interfaces
US20020105954A1 (en) Dynamic update proxy
Suzuki et al. Domain Name System--Past, Present and Future
CN117692173A (en) Request message processing method, system and related equipment
Parwez et al. DNS propagation delay: An effective and robust solution using authoritative response from non-authoritative server
CN112188300A (en) Method for realizing efficient domain name resolution based on smart television local DNS service
CN103166928A (en) Method and system for providing information service and domain name server (DNS) authorization server
WO2000001112A1 (en) Decentralized name services

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant