Reconciling internet DNS zone file changes with origin change requests

US9531603B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9531603-B2
Application numberUS-201414209783-A
CountryUS
Kind codeB2
Filing dateMar 13, 2014
Priority dateMar 14, 2013
Publication dateDec 27, 2016
Grant dateDec 27, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques for monitoring zone file changes are presented. The techniques may include obtaining at least one zone change request and parsing the at least one zone change request to obtain at least one change request unit. The techniques may include obtaining a last published zone file, obtaining a new zone file, and comparing the last published zone file to the new zone file to obtain at least one difference object. The techniques may include matching the at least one difference object to the at least one change request unit to identify at least one unmatched difference object. The techniques may include providing a human readable report comprising an indication of the at least one unmatched difference object.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for monitoring Domain Name System (DNS) zone file changes, the method comprising: obtaining at least one zone change request; parsing the at least one zone change request to obtain at least one change request unit, wherein each change request unit constitutes a single executable instruction; obtaining a last published zone file; obtaining an unpublished new zone file; comparing the last published zone file to the new zone file to obtain at least one difference object, wherein the at least one difference object identifies a DNS record type, a DNS record, and a difference type; matching the at least one difference object to the at least one change request unit to identify at least one unmatched difference object; providing a human readable report comprising an indication of the at least one unmatched difference object. 2. The method of claim 1 , wherein each change request unit is a smallest possible unit that can be executed on a domain or a host. 3. The method of claim 1 , wherein each change request unit is of the form of one of: DomainCreateHostAdd, DomainCreateDSAdd, DomainDelete, DomainUpdateHostAdd, DomainUpdateHostRemove, DomainUpdateDSAdd, DomainUpdateDSRemove, DomainUpdateDSChange, HostUpdatelPAdd, HostUpdatelPRemove, and HostUpdateHostNameChange. 4. The method of claim 1 , wherein each difference object comprises a DNSJAVA object. 5. The method of claim 4 , wherein each difference object comprises an org.xbill.DNS.record object. 6. The method of claim 1 , wherein each difference object is of the form of one of: AddNameServer, DeleteNameServer, AddA/AAAA, DeleteA/AAAA, AddDelegationSigner, and DeleteDelegationSigner. 7. The method of claim 1 , wherein the matching comprises, for each difference object, searching for a corresponding change request unit. 8. The method of claim 1 , further comprising filtering the at least one difference object to remove DNSSEC records. 9. The method of claim 1 , further comprising: altering the new zone file to account for the at least one unmatched difference object, whereby a corrected new zone file is produced; and providing the corrected new zone file for publishing. 10. The method of claim 1 , wherein: the at least one zone change request comprises at least one root zone change request; the last published zone file comprises a last published root zone file; and the new zone file comprises a new root zone file. 11. A system for monitoring zone file changes, the system comprising: at least one processor configured to obtain at least one zone change request; at least one processor configured to parse the at least one zone change request to obtain at least one change request unit, wherein each change request unit constitutes a single executable instruction; at least one processor configured to obtain a last published zone file; at least one processor configured to obtain an unpublished new zone file; at least one processor configured to compare the last published zone file to the new zone file to obtain at least one difference object, wherein the at least one difference object identifies a domain name system (DNS) record type, a DNS record, and a difference type; at least one processor configured to match the at least one difference object to the at least one change request unit to identify at least one unmatched difference object; at least one processor configured to generate a human readable report comprising an indication of the at least one unmatched difference object. 12. The system of claim 11 , wherein each change request unit is a smallest possible unit that can be executed on a domain or a host. 13. The system of claim 11 , wherein each change request unit is of the form of one of: DomainCreateHostAdd, DomainCreateDSAdd, DomainDelete, DomainUpdateHostAdd, DomainUpdateHostRemove, DomainUpdateDSAdd, DomainUpdateDSRemove, DomainUpdateDSChange, HostUpdatelPAdd, HostUpdatelPRemove, and HostUpdateHostNameChange. 14. The system of claim 11 , wherein each difference object comprises a DNSJAVA object. 15. The system of claim 11 , wherein each difference object comprises an org.xbill.DNS.record object. 16. The system of claim 11 , wherein each difference object is of the form of one of: AddNameServer, DeleteNameServer, AddA/AAAA, DeleteA/AAAA, AddDelegationSigner, and DeleteDelegationSigner. 17. The system of claim 11 , wherein the at least one processor configured to match is further configured to, for each difference object, search for a corresponding change request unit. 18. The system of claim 11 , further comprising at least one processor configured to filter the at least one difference object to remove DNSSEC records. 19. The system of claim 11 , further comprising: at least one processor configured to alter the new zone file to account for the at least one unmatched item, whereby a corrected new zone file is produced; and at least one processor configured to provide the corrected new zone file for publishing. 20. The system of claim 11 , wherein: the at least one zone change request comprises at least one root zone change request; the last published zone file comprises a last published root zone file; and the new zone file comprises a new root zone file.

Assignees

Inventors

Classifications

  • Electricity · mapped topic

  • H04L43/04Primary

    Processing captured monitoring data, e.g. for logfile generation · CPC title

  • using domain name system [DNS] · CPC title

  • Generation of reports · CPC title

  • H04L61/457Primary

    containing identifiers of data entities on a computer, e.g. file names · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9531603B2 cover?
Techniques for monitoring zone file changes are presented. The techniques may include obtaining at least one zone change request and parsing the at least one zone change request to obtain at least one change request unit. The techniques may include obtaining a last published zone file, obtaining a new zone file, and comparing the last published zone file to the new zone file to obtain at least …
Who is the assignee on this patent?
Verisign Inc
What technology area does this patent fall under?
Primary CPC classification H04L43/04. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Dec 27 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).