Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nameserver record validation #2202

Closed
vohmar opened this issue Oct 27, 2021 · 1 comment · Fixed by #2233
Closed

Nameserver record validation #2202

vohmar opened this issue Oct 27, 2021 · 1 comment · Fixed by #2233

Comments

@vohmar
Copy link
Contributor

vohmar commented Oct 27, 2021

We are scanning the registry daily for cdnskey record changes (csync). This enables us to also detect invalid ns records in the registry.

we should register nameserver records that

  • do not respond
  • have no record about the domain it's queried about (is registered to server in the TLD registry)

when such a ns record is detected we should wait for at least 2 additional confirmations by the next scans (identically to csync scans). If three consecutive scans detect the same issue we should flag the record as invalid and notify tech contact via email and registrar via poll message about the issue.

If the issue is still there after a month - notify again

@ratM1n
Copy link

ratM1n commented Dec 28, 2021

i was able to create domain with DNS servers which don't have this domain's zone and then add a new nameserver to this domain with non-existing name and without glue IP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants