You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2024. It is now read-only.
After going thru the Public Suffix List Pull Requests (where you can request to add your domain to the PSL), I have not found a PR for any of the domains - this includes dual.my, zc.al, xyz.wf or lag.tf.
The reason I am asking for this to be done so quick - I may or may not have locked myself out of my Zoho account...
I set up a custom email, but there were no MX records, so I just went to change the email - now it wants to send a code to my zc.al email, viewable by... you guessed it - logging into Zoho Mail. I can't even use services like ImprovMX to get in because, again... there is no MX records.
If you could get dual.my & it's domains registered ASAP, I would really appreciate it. I understand if it takes time, but the Zoho team has not responded to me, so...
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 publicsuffix/list#1245 as a well-documented example)
This request was not submitted with the objective of working around other third-party limits
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.
Hey, to get approved, we need more users on Dual.my. Currently, we only have around 400 users. I will initiate a PR once we reach the 700-800 user range to make it a safer approval process. Starting now might lead to early rejection, which isnt ideal.
Well, that would cause a huge inconvenience to users who want to use Dual.my for emails. Is there any way you could enable just MX? Leave out NS? Or maybe cut out MX & NS after around 500 users?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After going thru the Public Suffix List Pull Requests (where you can request to add your domain to the PSL), I have not found a PR for any of the domains - this includes dual.my, zc.al, xyz.wf or lag.tf.
The reason I am asking for this to be done so quick - I may or may not have locked myself out of my Zoho account...
I set up a custom email, but there were no MX records, so I just went to change the email - now it wants to send a code to my zc.al email, viewable by... you guessed it - logging into Zoho Mail. I can't even use services like ImprovMX to get in because, again... there is no MX records.
If you could get dual.my & it's domains registered ASAP, I would really appreciate it. I understand if it takes time, but the Zoho team has not responded to me, so...
Anyway, thanks!
PR 4 PSL: https://github.com/publicsuffix/list/pulls
Requirements Checklist:
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 publicsuffix/list#1245 as a well-documented example)
This request was not submitted with the objective of working around other third-party limits
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.
The text was updated successfully, but these errors were encountered: