Update .jm SLD enumeration #1437

brian-peter-dickson · 2021-09-28T08:13:19Z

Description of Organization
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 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:

Individual, not representing my employer.
DNS architect at GoDaddy.
No relationship with domain owner (jm CCTLD).
Contribution is enumeration of actual second-level domains, to augment the wildcard record '*.jm'.
No policy change is proposed, and the changes do not change policy.
(Several similar contributions for other wildcard-only CCTLDs have been submitted by me).

Reason for PSL Inclusion

Addition of second level domains facilitates use of PSL as input to producing DNS RPZ files.
The current entry consists only of a wildcard.
RPZ zones behave the same as regular DNS zone files, and interior wildcard labels do not work.
Thus, the only alternative is to add the actual SLDs so that RPZ entries can be created.
E.g. instead of 'foo.*.jm', there would be several similar domains like 'foo.edu.jm' etc.

DNS Verification via dig

Since I am not affiliated with the 'jm' domain, I cannot add the TXT records requested.
However, I have been able to do 'dig' commands to demonstrate that the SLDs themselves exist (as ENTs).
(NOERROR responses confirm the name exists.)

; <<>> DiG 9.16.13 <<>> @ns.jm. com.jm. NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10342
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;com.jm. IN NS