Update .pg -- instantiate SLDs for pg #1442

brian-peter-dickson · 2021-09-28T23:44:32Z

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:

I do not represent my employer.
DNS architect at GoDaddy.
No affiliation with domain owner.
Voluntarily adding second level domain entries in addition to existing wildcard.

Reason for PSL Inclusion

I am not affiliated with the domain owner, and cannot add the TXT record(s) as a result.
The request is to add second-level domains for the CCTLD, in addition to the existing wildcard ".pg".
The PSL policy for "pg" is not affected by the change.
What this accomplishes is that it enables use of the PSL for generating an RPZ zone.
RPZ (response policy zone) zones are ordinary DNS zones.
Prepending PSL entries to create RPZ records works correctly if the PSL entry does not have any wildcards.
DNS zones cannot have interior wildcards, or at least interior wildcards will never match any query.
For example, if the PSL entry is ".pg", then prepending "foo" gives "foo.*.pg", which never matches any query.

Adding the SLDs for pg will ensure that the generated records will all be of the form "foo.bar.pg", where "bar" is a real SLD underneath "pg" (the CCTLD). RPZ matching then works as expected.

DNS Verification via dig

I am not affiliated with "pg", but am able to confirm that the SLDs in question exist, via "dig" output with NOERROR results:

; <<>> DiG 9.16.13 <<>> @ns.uu.net. ac.pg. NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39625
;; 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: 1232
; COOKIE: 101c368bab01c6d44cff0e076153a62eb40d5c381364966e (good)
;; QUESTION SECTION:
;ac.pg. IN NS