Updating software utilizing domain name system (DNS)

• US 9,977,667 B2
• Filed: 09/09/2015
• Issued: 05/22/2018
• Est. Priority Date: 09/09/2015
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Berrange, Daniel
• Primary Examiner(s): Chen, Qing
• Assistant Examiner(s): HUDA, MOHAMMED NURUL
• Application Number:
  US14/849,272
• Publication Number:
  US 20170068530A1
• Time in Patent Office: 986 Days
• Field of Search: 717170
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Examples described herein are directed to systems and methods for updating software. An update system may generate a first Domain Name System (DNS) record comprising first version data indicating a version of an update to the software. The update system may send the DNS record to a DNS server with an indication of a domain name associated with the software.

Claims

1. A system for updating a database, the system comprising:

a Domain Name System (DNS) server;

an update system separate from and in communication with the DNS server; and

a client system separate from and in communication with the update system and the DNS server, the client system storing version data indicating a current client update to the database,

wherein the update system comprises at least one processor and operatively associated memory, and wherein the update system is programmed to;

generate a resource record comprising new version data indicating a new version of an update to the database is available at the update system;

write the resource record to a zone file corresponding to a domain name;

write, to the zone file, time-to-live data for the resource record before sending the zone file to the DNS server, wherein the time-to-live data indicates a valid time period for the resource record; and

send the zone file to the DNS server; and

wherein the client system comprises at least one processor and operatively associated memory, and wherein the client system is programmed to;

send, to the DNS server, a DNS query comprising domain name data indicating the domain name;

in response to the DNS query, receive the zone file from the DNS server after the zone file was sent from the update system to the DNS server;

in response to receiving the zone file, determine that the valid time period indicated by the time-to-live data from the zone file has not expired;

in response to the determination that the valid time period has not expired, determine that the new version data does not match the client version data;

in response to the determination that the new version data does not match the client version data, send to the update system a request for the new version of the update to the database; and

in response to the request for the new version of the update, receive, from the update system, the new version of the update to the database.

2. The system of claim 1, wherein the client system includes a DNS client programmed to:

receive the DNS query;

determine that a memory location associated with the DNS client does not comprise a valid copy of the zone file corresponding to the domain name; and

send the DNS query to the DNS server; and

wherein the DNS server is programmed to;

receive the DNS query from the DNS client;

determine that a memory location associated with the DNS server comprises the zone file;

determine that the valid time period indicated by the time-to-live data from the zone file has not expired; and

send the zone file to the DNS client.

3. The system of claim 1, wherein the database comprises a plurality of records, and wherein the update comprises database replacement data to replace at least one of the plurality of records.

4. The system of claim 1, wherein the resource record is a TXT resource record.

5. The system of claim 1, wherein the client system periodically determines whether the new version data indicating a new version of an update to the database that is different from the client version data stored at the client system is available at the update system by sending a periodic DNS query to the DNS server.

6. The system of claim 1, wherein the database is not the DNS database itself.

7. The system of claim 1, wherein the database is database of operating system metadata.

8. The system of claim 1, wherein the database is an anti-virus database.

9. A method for updating software, the method comprising:

sending, by a client system and to a domain name system (DNS) server, a DNS query, the DNS query comprising domain data indicating a domain name associated with a new software update;

receiving, by the client system, in response to the DNS query, a DNS record comprising new version data indicating a version of a new update to the software, wherein the DNS record is associated with data indicating a valid time period for the new update to the software;

in response to receiving the DNS record, determining, by the client system, that the valid time period for the new update to the software has not expired;

in response to the determination that the valid time period has not expired, determining, by the client system, that the new version data is not equivalent to client version data stored at the client system, the client version data indicating a version of a current update to the software at the client system;

in response to the determination that the new version data is not equivalent to the client version data, sending, by the client system and to an update system, separate from and in communication with the client system and the DNS server, a request for the new update to the software; and

in response to the request for the new update to the software, receiving, by the client system and from the update system, the new update to the software,

wherein the client system sends the DNS query to the DNS server after the DNS record was sent from the update system to the DNS server.

10. The method of claim 9, wherein the client system sends the DNS query to a DNS client executing at the client system before sending the DNS query to the DNS server.

11. The method of claim 10, further comprising:

determining, by the DNS client, that no valid copy of the DNS record is stored at the client system;

sending, by the DNS client, the DNS query to the DNS server;

receiving, by the DNS client and from the DNS server, the DNS record; and

returning, by the DNS client, the DNS record.

12. The method of claim 9, further comprising determining that a digital signature of the DNS record matches a public key of the update system.

13. The method of claim 9, wherein the software comprises a database, the database comprising a plurality of records, and wherein the new update comprises a modification to a first record of the plurality of records.

14. The method of claim 9, wherein the DNS record comprises a zone file, further comprising:

identifying in the zone file a resource record corresponding to the new update;

and reading the new version data from the resource record.