List of PSDs maintained by their TLD's registry

[Ruurtjan Pul]

Hi,

For my project Nslookup, I'm interested in a list of public suffix domains whose subdomains are handed out by their respective TLD registries (e.g. `.co.uk.` and `com.ac`). But not `s3.af-south-1.amazonaws.com`, as those domains are handed out by Amazon, and not Verisign.

Is there any way to distinguish between those? Or are there efforts to maintain such a list?

Best,

Ruurtjan

[Simon Friedberger]

That is pretty much the distinction between the private and the public section. However, the distinction is very lose and separating those might not make a lot of sense. What are you trying to do?

--
You received this message because you are subscribed to the Google Groups "psl-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to publicsuffix-dis...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/publicsuffix-discuss/834cf6f9-81aa-4e13-8979-cfe56d7b5979n%40googlegroups.com.

[dnsguru]

Simon is right, that the #ICANN section is likely your "Gold Zone" and then you'll find some flecks here and there in the #PRIVATE section.

 It seems that you are looking for entries that offer 'registry-esque' situation where a third party might have their own nameservers   There are a few, like for example IT.COM or CentralNic who offer domain registrations to third parties.

Still a little confusing to me if you're after "Resolution" or "Registration" side of the equation.

Most of the areas where hosting companies or projects are doling out addresses for host access addresses are generally opaque and would not generally want to have people 'help' map their namespace for reasons of security.

[Ruurtjan Pul]

Ah, thanks! I didn't know about these sections in the PSL. That probably gets me most of the way there.

> What are you trying to do?

You're right that I might have an "XY problem". I'll go back to the start.

I'm rebuilding Nslookup's DNS propagation checker. I noticed that registries tend to be slow in updating NS records in their authoritative name servers. When querying them directly without any caching, they generally return stale records for a while after moving domains to another registrar or otherwise changing NS records.

Therefore, it may be helpful to point people to the NS records of a domain they're checking on Nslookup when they indicate that records aren't what they expect. More specifically, the apex of the DNS zone, i.e. 'example.com' when they're checking A records of 'www.example.com'.

However, this is not helpful for subdomains of "s3.af-south-1.amazonaws.com", for example. In that case, AWS hands out CNAMEs instead of NS records, and their authoritative servers immediately return updated records.

Long story short, I'd like to show a helpful message for domains registered at registries.