Set and forget debris -cleanup of nymnom expired names (see #1354) #1383
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PSL Maintainer Volunteer submitted patch. NymNom appears to have gone kablooey, or at least they have not renewed a very significant quantity of the domains in their section. I am removing names that were non-resolvable, and this may set a precedent to just pull entire sections where a majority of names within it are abandoned to expire like this without pulling PSL entries. Non-exhaustive list of fail; appears that folks have picked up other nymnom names and have re-purposed them. This PR nom.ae SOA : ** server can't find nom.ae: SERVFAIL nom.af SOA : ** server can't find nom.af: NXDOMAIN nom.ai : ;; connection timed out; no servers could be reached nom.al : *** Can't find nom.al: No answer nym.by SOA : ** server can't find nym.by: NXDOMAIN nom.cl : ;; connection timed out; no servers could be reached nym.ec SOA : ** server can't find nym.ec: NXDOMAIN nom.gd : ;; connection timed out; no servers could be reached nom.gl SOA : ** server can't find nom.gl: NXDOMAIN nym.gr : ;; connection timed out; no servers could be reached nom.gt : ;; connection timed out; no servers could be reached nym.gy SOA : ** server can't find nym.gy: NXDOMAIN nom.hn SOA : ** server can't find nom.hn: NXDOMAIN nym.hk : ;; connection timed out; no servers could be reached nym.ie : ;; connection timed out; no servers could be reached nom.ke SOA : ** server can't find nom.ke: NXDOMAIN nym.kz SOA : ** server can't find nym.kz: SERVFAIL nym.me SOA : ** server can't find nym.me: SERVFAIL nom.mk SOA : ** server can't find nom.mk: NXDOMAIN nym.mx : *** Can't find nym.mx: No answer nym.pe : *** Can't find nym.pe: No answer nym.pt SOA : ** server can't find nym.pt: NXDOMAIN nom.pw SOA : ** server can't find nom.pw: SERVFAIL nom.qa SOA : ** server can't find nom.qa: SERVFAIL nym.ro : ;; connection timed out; no servers could be reached nym.su : ;; connection timed out; no servers could be reached nom.tj SOA : ** server can't find nom.tj: SERVFAIL nom.ug SOA : ** server can't find nom.ug: NXDOMAIN nom.uy SOA : ** server can't find nom.uy: NXDOMAIN
dnsguru
added
the
h=sleevi
dnsguru
added a commit
that referenced
this pull request
Aug 6, 2021
|
Addressed by #1392; closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PSL Maintainer Volunteer submitted patch addresses some of (but not all of) #1354
[ Seeking other volunteer (@sleevi) to review and approve this PR so I can merge it ]
NymNom appears to have gone kablooey, or at least they have not renewed a very significant quantity of the domains in their section.
I am removing names that were non-resolvable, and this may set a precedent to just pull entire sections where a majority of names within it are abandoned to expire like this without pulling PSL entries.
The entire list in the section was not entirely lost, and rather than be punative and remove the entire section due to the high level of extra work the situation
Non-exhaustive list of fail; appears that folks have picked up other nymnom names and have re-purposed them.
This PR removed the following domoains that had hard DNS errors:
nom.ae SOA : ** server can't find nom.ae: SERVFAIL
nom.af SOA : ** server can't find nom.af: NXDOMAIN
nom.ai : ;; connection timed out; no servers could be reached
nom.al : *** Can't find nom.al: No answer
nym.by SOA : ** server can't find nym.by: NXDOMAIN
nom.cl : ;; connection timed out; no servers could be reached
nym.ec SOA : ** server can't find nym.ec: NXDOMAIN
nom.gd : ;; connection timed out; no servers could be reached
nom.gl SOA : ** server can't find nom.gl: NXDOMAIN
nym.gr : ;; connection timed out; no servers could be reached
nom.gt : ;; connection timed out; no servers could be reached
nym.gy SOA : ** server can't find nym.gy: NXDOMAIN
nom.hn SOA : ** server can't find nom.hn: NXDOMAIN
nym.hk : ;; connection timed out; no servers could be reached
nym.ie : ;; connection timed out; no servers could be reached
nom.ke SOA : ** server can't find nom.ke: NXDOMAIN
nym.kz SOA : ** server can't find nym.kz: SERVFAIL
nym.me SOA : ** server can't find nym.me: SERVFAIL
nom.mk SOA : ** server can't find nom.mk: NXDOMAIN
nym.mx : *** Can't find nym.mx: No answer
nym.pe : *** Can't find nym.pe: No answer
nym.pt SOA : ** server can't find nym.pt: NXDOMAIN
nom.pw SOA : ** server can't find nom.pw: SERVFAIL
nom.qa SOA : ** server can't find nom.qa: SERVFAIL
nym.ro : ;; connection timed out; no servers could be reached
nym.su : ;; connection timed out; no servers could be reached
nom.tj SOA : ** server can't find nom.tj: SERVFAIL
nom.ug SOA : ** server can't find nom.ug: NXDOMAIN
nom.uy SOA : ** server can't find nom.uy: NXDOMAIN