dns-violations

by dns-violations

dns-violations / dns-violations

List of DNS violations by implementations, software and/or systems

205 Stars 29 Forks Last release: Not found MIT License 117 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

DNS Violations

List of DNS violations by implementations, software and/or systems

About

This List consists of DNS Violation Entries (DVE's) that describes known violations to the DNS protocol by implementations, software and/or systems.

Purpose

The purpose of the List is to better understand how wrongfully the DNS protocol is used out in the wild in order to try and make it better. There is also a great gain for implementers to verify that they can handle wrong DNS correctly.

Community based

The List is driven by the community for the community, anyone can send in a violation and a team of community members will review and accept or reject the violation, this team in called Maintainers. Anyone can request to join the Maintainers team and <acceptance method TBD>.

Violation

An implementation, software and/or system is considered to be in violation to the DNS protocol when it does not strongly conform to the current DNS RFCs. Violations can also include updated or obsolete DNS RFCs.

Submission

Anyone can submit a DNS violation and request a DVE, this is done as a pull request or an issue. If submitted as a markdown file, add it under the year directory and with the full

DVE-YEAR-NUMBER.md
filename.

Format

The format is Markdown with the following suggested headers, which are not strict but should at least have short and long description. Metadata may be included at the end of headers, together under

Metadata
header or at the end of the file.
# DVE--: 

Description

Evidence

Proposed fix

Workaround

DNS Operator/Vendor Response

Files

(): <file within dve year directory> application/dns+dnstap: DVE-YEAR-NUMBER/example.dnstap application/dns+dnstap (segfault): DVE-YEAR-NUMBER/example_that_segfaults.dnstap

Metadata

Submitter: Submit-Date: Report-Date: Fixed-Date: Tags: :

Files

You may attach files to the DVE by using the

Files
section and add the files in a directory related to the DVE as (from repository root)
YEAR/DVE-YEAR-NUMBER/
.

DVE Allocation

DVE are allocated sequentially starting from the number 1 using the format

DVE--
. The number is allocated on a first-come-first-served bases via pull requests or by the Maintainers for an issue. The Maintainers may reserve a number for an issue by updated the title of the issue with the full DVE and also add a comment addressed to
@DNS-OARC/dve-maintainers
that it has been reserved. Collisions are rejected/asked to be updated.

Repository Directory Layout

  • In the root of the repository there should only be documentation
  • The DVE is placed under a year directory
  • The DVE is in markdown format and the filename is
    DVE-YEAR-NUMBER.md
  • Optional files attached to the DVE may be put under a directory with the full DVE name under the year directory, example
    YEAR/DVE-YEAR-NUMBER/file

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.