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

Add vn.al #2190

Closed
wants to merge 4 commits into from
Closed

Add vn.al #2190

wants to merge 4 commits into from

Conversation

vnddns
Copy link

@vnddns vnddns commented Sep 26, 2024

Public Suffix List (PSL) Submission

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

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

For Private section requests that are submitting entries for domains that match their organization website's primary domain:

Seriously, carefully read the downline flow of the PSL and the guidelines.
Your request could very likely alter the cookie and certificate (as well as other) behaviours on your 
core domain name in ways that could be problematic for your business.
Rollback is really not predicatable, as those who use or incorporate the PSL do what they do, and when.
It is not within the PSL volunteers' control to do anything about that.  
The volunteers are busy with new requests, and rollbacks are lowest priority, so if something gets broken 
it will stay that way for an indefinitely long while.

(Link: about propogation/expectations)

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

Description of Organization

Organization Website: https://vn.al
This is a Dynamic DNS service provider. We provide dyndns with the vn.al subdomain to our users, allowing them to configure and self-host some services without the need of buying a personal domain. We only support ipv4 (A record).

Reason for PSL Inclusion

Pretty much the same rationale as in my original PR #1539.

This is dynamic dns service, which means subdomains are registered by independent 3rd parties.
We want to prevent setting cookies on the apex domains
We want the developers' apps to be isolated from one another (cookies, suffix highlighting, etc).
Also, the expiry date of the domain is more than two years away, and I will also keep the domain and _psl.

Number of users this request is being made to serve:

https://vn.al/ has over 2500+ users registered.

DNS Verification via dig

dig +short TXT _psl.vn.al
"https://github.com/publicsuffix/list/pull/2190"

make test

Test completed successfully.

@vnddns vnddns changed the title Add "vn.al" Add 'vn.al' Sep 26, 2024
@vnddns vnddns changed the title Add 'vn.al' Add vn.al Sep 26, 2024
@wdhdev
Copy link
Contributor

wdhdev commented Sep 26, 2024

What is the user count of your service?

@vnddns
Copy link
Author

vnddns commented Sep 26, 2024

What is the user count of your service?

https://vn.al has over 2500+ users registered.

@simon-friedberger
Copy link
Contributor

The PR template has changed. Please use the new template.

@vnddns
Copy link
Author

vnddns commented Sep 26, 2024

The PR template has changed. Please use the new template.

I have updated please check for me. Thanks !!!

@simon-friedberger
Copy link
Contributor

You seem to have a login form on a plain HTTP site!

@vnddns
Copy link
Author

vnddns commented Sep 27, 2024

You seem to have a login form on a plain HTTP site!

I fixed it. Thank !

@simon-friedberger
Copy link
Contributor

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

@simon-friedberger
Copy link
Contributor

Please provide

  • the expiration date for the domain
  • more information on your organization because the website doesn't really have any
  • information on how many of those 2500 users have sites
  • and some examples of such sites, you are hosting
  • an email address on a different domain so we can still contact you if this service goes down
  • a separate registration site, please have a look at this https://github.com/publicsuffix/list/wiki/Format#example

@vnddns
Copy link
Author

vnddns commented Sep 27, 2024

  • the expiration date for the domain : 9/20/2028
  • more information on your organization because the website doesn't really have any:
    vn.al is a dynamic dns service.
    You usually need it so your router (or other dyndns2-compatible client) can update a hostname, so you don't need to know or find out your current IP address.
    vn.al is simple, usable, free, friendly, secure and respects your privacy.
  • information on how many of those 2500 users have sites
    Each user will register with 1 domain name so there are at least 2500+ active domains. In the dashboard I can see this service mostly focuses on vpn or private connection ip like 10.0.0.xxx

@dnsguru
Copy link
Member

dnsguru commented Sep 29, 2024

The homepage was not reachable.

Please resubmit this to the project when it has more stability and larger user base.

@dnsguru dnsguru closed this Sep 29, 2024
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.

4 participants