IP Library Granted Patent US 10,243,795
Granted Patent B2
US 10,243,795 · App. 15/469,335 · Granted Mar 26, 2019

DNS file settings deferral

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,243,795
App. No.
15/469,335
Granted
Mar 26, 2019
Kind
B2
Abstract

Systems and methods of the present invention provide for one or more server computers configured to: receive data encoding an update to a configuration setting in a DNS and an indication of an event deferring the update. After receiving the data and indication, the server(s) may: download, from a DNS server, a zone file comprising the configuration setting; modify the zone file using the update to generate a modified zone file comprising the update; determine, in accordance with the indication, whether the event has occurred; and if so, cause the DNS server to modify the zone file comprising the configuration setting in accordance with the modified zone file.

Claims (63)

1. A system, comprising a hardware server computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory that, when executed, cause the system to:

decode, from a graphical user interface (GUI) displayed on a client hardware computing device coupled to the network:

a configuration update to be applied to a domain name system (DNS); and

an event data defining an event after which to activate the configuration update;

access a zone file stored on a DNS server within the DNS;

modify the zone file to include the configuration update; and

responsive to an occurrence of the event, activate the configuration update within the DNS server.

2. The system of claim 1 wherein the event comprises:

a current date and time matching a date and time input into the GUI;

an approval decoded from a second client hardware computing device operated by a user whose contact data is decoded from the GUI and stored in a database coupled to the network.

3. The system of claim 1 , wherein the specific computer-executable instructions further cause the system to decode a selection from the GUI to:

immediately activate the configuration update; or

defer activation of the configuration update until after the occurrence of the event.

4. The system of claim 1 , wherein the GUI displays at least one event definition GUI control receiving user input defining the event.

5. The system of claim 1 , wherein the GUI displays at least one configuration update GUI control receiving user input defining the configuration update.

6. The system of claim 1 , wherein the specific computer-executable instructions further cause the system to:

run a diff utility identifying a difference between an original zone file and the zone file modified to include the configuration update; and

generate a user interface comprising:

a first display of the original zone file;

a second display comprising the zone file modified to include and highlight the configuration update; and

a status of the event.

7. The system of claim 1 , wherein the specific computer-executable instructions further cause the system to store in association, in a database coupled to the network:

a copy of the zone file downloaded from the DNS server;

the configuration update; and

the event data.

8. The system of claim 1 , wherein the specific computer-executable instructions further cause the system to:

generate and store a queue of at least one ready process comprising the configuration update; and

automatically schedule the at least one ready process to run and execute after the event.

9. The system of claim 1 , wherein the specific computer-executable instructions further cause the system to:

decode, from the GUI, an additional configuration update; and

activate the additional update responsive to the occurrence of the event.

10. A system, comprising at least one hardware server computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory that, when executed, cause the system to:

detect the occurrence of an event defined within an event data decoded from a graphical user interface (GUI) displayed on a client hardware computing device coupled to the network;

modify a zone file stored on a domain name system (DNS) server within a DNS to include a configuration update decoded from the GUI; and

activate the configuration update.

11. A method, comprising:

detecting, by a server hardware computing device coupled to a network and comprising at least one processor executing specific computer-executable instructions within a memory, the occurrence of an event defined within an event data decoded from a graphical user interface (GUI) displayed on a client hardware computing device coupled to the network;

modifying, by the server hardware computing device, a zone file stored on a domain name system (DNS) server within a DNS to include a configuration update decoded from the GUI; and

activating, by the server hardware computing device, the configuration update.

12. The method of claim 11 wherein the event comprises:

a current date and time matching a date and time input into the GUI;

an approval decoded from a second client hardware computing device operated by a user whose contact data is decoded from the GUI and stored in a database coupled to the network.

13. The method of claim 11 , further comprising the step of decoding a selection from the GUI to:

immediately activate the configuration update; or

defer activation of the configuration update until after the occurrence of the event.

14. The method of claim 11 , further comprising the step of displaying, by the GUI, at least one event definition GUI control receiving user input defining the event.

15. The method of claim 11 , further comprising the step of displaying, by the GUI, at least one configuration update GUI control receiving user input defining the configuration update.

16. The method of claim 11 , further comprising the steps of:

running, by the server hardware computing device, a diff utility identifying a difference between an original zone file and the zone file modified to include the configuration update; and

generating, by the server hardware computing device, a user interface comprising:

a first display of the original zone file;

a second display comprising the zone file modified to include and highlight the configuration update; and

a status of the event.

17. The method of claim 11 , further comprising the step of storing, by the server hardware computing device, in association, in a database coupled to the network:

a copy of the zone file downloaded from the DNS server;

the configuration update; and

the event data.

18. The method of claim 11 , further comprising the steps of:

generating and storing, by the server hardware computing device, a queue of at least one ready process comprising the configuration update; and

automatically scheduling, by the server hardware computing device, the at least one ready process to run and execute after the event.

19. The method of claim 11 , further comprising the steps of:

decoding, by the server hardware computing device, from the GUI, an additional configuration update; and

activating, by the server hardware computing device, the additional update responsive to the occurrence of the event.

Assignments (3)
SECURITY AGREEMENT Recorded Feb 17, 2023
From: GO DADDY OPERATING COMPANY, LLC; GD FINANCE CO, LLC; GODADDY MEDIA TEMPLE INC.; GODADDY.COM, LLC; LANTIRN INCORPORATED; POYNT, LLC
To: ROYAL BANK OF CANADA
Reel/Frame 062782/0489 →
SECURITY AGREEMENT Recorded Oct 12, 2020
From: GO DADDY OPERATING COMPANY, LLC; GD FINANCE CO., INC.
To: BARCLAYS BANK PLC
Reel/Frame 054045/0829 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 24, 2017
From: GUPTA, NITIN
To: GO DADDY OPERATING COMPANY, LLC
Reel/Frame 041734/0860 →