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

Update contact information for nyc.mn #2125

Merged
merged 2 commits into from
Sep 4, 2024

Conversation

awsjulian
Copy link
Contributor

@awsjulian awsjulian commented Sep 3, 2024

Public Suffix List (PSL) Pull Request (PR) Template

Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.

Checklist of required steps

  • Description of Organization

  • Robust Reason for PSL Inclusion

  • DNS verification via dig

  • Run Syntax Checker (make test)

  • Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section

Submitter affirms the following:

  • We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
  • This request was not submitted with the objective of working around other third-party limits
  • The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
  • The Guidelines were carefully read and understood, and this request conforms
  • The submission follows the guidelines on formatting and sorting

For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.

To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.

PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.

(Link: about propagation/expectations)

  • Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

NYC.mn is more than just a subdomain registration service. Our goal is to build an online community where people who use .nyc.mn subdomains can show off their websites and share how they are using their domains. We want to bring together individuals and businesses who love New York City, giving them a place to connect, share their projects, and be part of a lively online network that celebrates the NYC spirit.

More: #2114 (comment)

Organization Website:

https://dot.nyc.mn/

Reason for PSL Inclusion

Cookie security in browsers.

Number of users this request is being made to serve:

We have 1800+ users who have registered subdomains. We conducted a random selection and checked for exposed ports (80 or 443). Here is an incomprehensive list of subdomains that are possibly hosting individual websites, available for review:

https://gist.github.com/awsjulian/6da06395c46ff23ad394344e7199b5f1#file-random-nyc-sites-md

DNS Verification via dig

dig +short TXT _psl.nyc.mn
"https://github.com/publicsuffix/list/pull/2125"

Results of Syntax Checker (make test)

Passed

@wdhdev
Copy link
Contributor

wdhdev commented Sep 3, 2024

  • Expiration (Note: Must STAY >2y at all times)
    • nyc.mn expires 2027-08-05
  • DNS _psl entries (Note: Must STAY in place)
    • _psl.nyc.mn
  • Tests pass
  • Sorting
  • Reasoning/Organization description
  • Non-personal email address

Notes:

  • When adding the TXT record at _psl.nyc.mn please removing any existing TXT records under that zone.
  • nyc.mn is not >2y, please renew the domain for up to 2 years or more. (If the .mn registry doesn't allow this just let us know and we can ignore this requirement)

@awsjulian
Copy link
Contributor Author

@wdhdev Thank you for the pre-review! This PR is still in "Draft" status as it's not ready for full review yet. Our admin, who handles domain renewal and DNS changes, is currently away this week. We'll make these updates soon, and once everything is in place, we'll mark this PR as ready for review. Thanks again!

@simon-friedberger
Copy link
Contributor

simon-friedberger commented Sep 3, 2024

I'll add that if you have an email for your organization that is not on the same domain, that would be preferable. Otherwise, if you lose access to the domain we cannot ask you if we can delete it. Yes, that sounds silly but we have few options of checking if a domain still needs to be on the PSL and being able to reach the original submitter is always easiest.

@awsjulian
Copy link
Contributor Author

  • Domain has been renewed until 2027-08-05.
  • _psl.nyc.mn TXT record updated to "https://github.com/publicsuffix/list/pull/2125"
  • Non-personal email address updated to a non-nyc.mn email address. What @simon-friedberger suggested is a good idea, and we are considering having backup communication channels, including this email address and a status page, in case of downtime with the main nameservers of nyc.mn.
  • Ran tests and passed.

Thank you for reviewing! I have opened the PR and it's ready for review.

@awsjulian awsjulian marked this pull request as ready for review September 3, 2024 20:18
@simon-friedberger simon-friedberger merged commit c80f273 into publicsuffix:master Sep 4, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants