System and method for managing domain name system records
US-2024111749-A1 · Apr 4, 2024 · US
US12554698B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12554698-B2 |
| Application number | US-202418785599-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 26, 2024 |
| Priority date | Oct 3, 2022 |
| Publication date | Feb 17, 2026 |
| Grant date | Feb 17, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Aspects of the subject disclosure may include, for example, a device including a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations of: receiving domain name system (DNS) record changes; identifying errors from the DNS record changes; discarding the DNS record changes responsive to the errors identified; scheduling the DNS record changes responsive to a lack of errors identified; translating the DNS record changes into protocol specific formats; and provisioning the protocol specific formats of the translated DNS record changes. Other embodiments are disclosed.
Opening claim text (preview).
What is claimed is: 1 . A device, comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: receiving from equipment of an administrator, at a domain name system (DNS) provisioning gateway (DPG), DNS record changes in a human-readable format; identifying, by the DPG, a lack of errors in the DNS record changes received from the equipment of the administrator; scheduling, by the DPG, the DNS record changes responsive to the lack of errors identified; translating, responsive to the scheduling, by the DPG, the DNS record changes from the human-readable format into a plurality of protocol specific formats, each protocol specific format of the plurality of protocol specific formats corresponding to each respective DNS server software of a plurality of DNS server softwares implemented by a respective DNS server within a heterogeneous DNS server complex comprising a plurality of DNS servers, wherein each DNS server of the plurality of DNS servers operates one DNS server software of the plurality of DNS softwares to support a plurality of different DNS server softwares; provisioning, by the DPG, the DNS record changes and the protocol specific formats of the DNS record changes to the respective DNS servers within the heterogeneous DNS server complex over a network, wherein the provisioning comprises identifying DNS servers responsible for name services affected by the DNS record changes, and sending the protocol specific formats to the DNS servers identified; verifying, by the DPG, that the DNS record changes were properly implemented, wherein the verifying includes creating a script to verify that the DNS record changes were properly implemented; and receiving, responsive to the verifying, by the DPG, a verification that the DNS record changes have been received and implemented correctly. 2 . The device of claim 1 , wherein the identifying the lack of errors comprises pulling existing DNS records from DNS authoritative servers, and checking the DNS record changes against the existing DNS records from the DNS authoritative servers. 3 . The device of claim 2 , wherein the lack of errors comprises a lack of syntax errors. 4 . The device of claim 2 , wherein the identifying the lack of errors further comprises converting, by the DPG, the existing DNS records into the human-readable format. 5 . The device of claim 1 , wherein the DPG is configured to issue a warning when a duplicate record is detected among the DNS record changes. 6 . The device of claim 1 , wherein the operations further comprise generating, by the DPG, a log file. 7 . The device of claim 1 , wherein the verifying further comprises executing, by the DPG, the script to verify that changed DNS records are functioning correctly. 8 . The device of claim 1 , wherein the processing system comprises a plurality of processors operating in a distributed computing environment. 9 . A non-transitory, machine-readable medium, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, the operations comprising: receiving from equipment of an administrator, at a domain name system (DNS) provisioning gateway (DPG), DNS record changes in a human-readable format; identifying, by the DPG, a lack of errors in the DNS record changes received from the equipment of the administrator; scheduling, by the DPG, the DNS record changes responsive to the lack of errors identified; translating, responsive to the scheduling, by the DPG, the DNS record changes from the human-readable format into a plurality of protocol specific formats, each protocol specific format of the plurality of protocol specific formats corresponding to each respective DNS server software of a plurality of DNS server softwares implemented by a respective DNS server within a heterogeneous DNS server complex comprising a plurality of DNS servers, wherein each DNS server of the plurality of DNS servers operates one DNS server software of the plurality of DNS softwares to support a plurality of different DNS server softwares; provisioning, by the DPG, the DNS record changes and the protocol specific formats of the DNS record changes to the respective DNS servers within the heterogeneous DNS server complex over a network, wherein the provisioning comprises identifying DNS servers responsible for name services affected by the DNS record changes, and sending the protocol specific formats to the DNS servers identified; verifying, by the DPG, that the DNS record changes were properly implemented, wherein the verifying includes creating, by the DPG, a script to verify that the DNS record changes were properly implemented; and receiving, responsive to the verifying, by the DPG, a verification that the DNS record changes have been received and implemented correctly. 10 . The non-transitory, machine-readable medium of claim 9 , wherein the identifying the lack of errors comprises pulling existing DNS records from DNS authoritative servers, and checking the DNS record changes against the existing DNS records from the DNS authoritative servers. 11 . The non-transitory, machine-readable medium of claim 10 , wherein the lack of errors comprises a lack of syntax errors. 12 . The non-transitory, machine-readable medium of claim 11 , wherein the identifying the lack of errors further comprises converting, by the DPG, the existing DNS records into the human-readable format. 13 . The non-transitory, machine-readable medium of claim 9 , wherein the DPG is configured to issue a warning when a duplicate record is detected among the DNS record changes. 14 . The non-transitory, machine-readable medium of claim 9 , wherein the operations further comprise: generating, by the DPG, a log file. 15 . The non-transitory, machine-readable medium of claim 9 , wherein the script implements dig commands to query DNS authoritative servers and check results. 16 . The non-transitory, machine-readable medium of claim 9 , wherein the processing system comprises a plurality of processors operating in a distributed computing environment. 17 . A method, comprising: receiving from equipment of an administrator, by a processing system including a processor in a domain name system (DNS) provisioning gateway (DPG), DNS record changes in a human-readable format; identifying, by the processing system, a lack of errors in the DNS record changes received from the equipment of the administrator; scheduling, by the processing system, the DNS record changes responsive to a lack of errors identified; translating, responsive to the scheduling, by the processing system, the DNS record changes from the human-readable format into a plurality of protocol specific formats, each protocol specific format of the plurality of protocol specific formats corresponding to each respective DNS server software of a plurality of DNS server softwares implemented by a respective DNS server within a heterogeneous DNS server complex comprising a plurality of DNS servers, wherein each DNS server of the plurality of DNS servers operates one DNS server software of the plurality of DNS softwares to support a plurality of different DNS server softwares; provisioning, by the DPG, the DNS record changes and the protocol specific formats of the DNS record changes to the respective DNS servers within the heterogeneous DNS server complex over a network, wherein the provisioning comprises
Updating · CPC title
using domain name system [DNS] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.