-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
co.az is not exist in the list #1903
Comments
If somebody from the registry of Azerbaijan requests it we would be happy to add it. Could you maybe reach out to them? |
I've sent an email to see if they can comment in public. |
Via the IANA Contact?
The ccTLD contacts get so much spam to those addresses, that it is typical
to not get responses.
I have found it has been more productive to do outreach in the tech day at
ICANN meetings every year or so.
…On Wed, Nov 22, 2023, 12:59 AM Frederik Braun ***@***.***> wrote:
I've sent an email to see if they can comment in public.
—
Reply to this email directly, view it on GitHub
<#1903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQTJJVHIC7H73UH5X7GGDYFW5FLAVCNFSM6AAAAAA7VB4AWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSGM2TIOBUGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I'm sure it would be 1000 times easier to reach someone in person when at the same event. In this case, I read through their regulatory government documents and ended up writing to [email protected]. I'm not really expecting someone to answer. The document above, btw, does list all second level domains explicitly, albeit in prose text. @dnsguru Has that been enough in the past or would we rather wait? |
We typically have (with ccTLD) let the registry speak for cookie etc
affectation through the addition of the DNS validation record being added
in-zone (or in TLD Apex).
Largely, because the change would impact their customers and potentially
trigger customer service calls - thus the desire is to have the inclusion
be intentional.
…On Wed, Nov 22, 2023, 5:35 AM Frederik Braun ***@***.***> wrote:
Via the IANA Contact? The ccTLD contacts get so much spam to those
addresses, that it is typical to not get responses. I have found it has
been more productive to do outreach in the tech day at ICANN meetings every
year or so.
I'm sure it would be 1000 times easier to reach someone in person when at
the same event. In this case, I read through their regulatory government
documents <https://whois.az/?page_id=10> and ended up writing to
***@***.***
I'm not really expecting someone to answer. The document above, btw, does
list all second level domains explicitly, albeit in prose text. @dnsguru
<https://github.com/dnsguru> Has that been enough in the past or would we
rather wait?
—
Reply to this email directly, view it on GitHub
<#1903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQTJKCPJOIWBSQYDGU7CTYFX5SBAVCNFSM6AAAAAA7VB4AWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSG44DGNJQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dnsguru <https://github.com/dnsguru> Has that been enough in the past or
would we rather wait?
where one of us has had some form of interaction with the cctld or the
cctld has directly participated in the creation or comments on a pull
request have made changes but not with third party submissions.
We will see 1-2 requests directly from ccTLDs after an event I present at -
where they have spoken with me directly to help them review their
section(s)
We have a couple of ccTLD pull requests currently open which merit review
or commentary from the ccTLD - i add a label for these where ICANN section
entries are affected
…On Wed, Nov 22, 2023, 6:46 AM Jothan Frakes ***@***.***> wrote:
We typically have (with ccTLD) let the registry speak for cookie etc
affectation through the addition of the DNS validation record being added
in-zone (or in TLD Apex).
Largely, because the change would impact their customers and potentially
trigger customer service calls - thus the desire is to have the inclusion
be intentional.
On Wed, Nov 22, 2023, 5:35 AM Frederik Braun ***@***.***>
wrote:
> Via the IANA Contact? The ccTLD contacts get so much spam to those
> addresses, that it is typical to not get responses. I have found it has
> been more productive to do outreach in the tech day at ICANN meetings every
> year or so.
>
> I'm sure it would be 1000 times easier to reach someone in person when at
> the same event. In this case, I read through their regulatory government
> documents <https://whois.az/?page_id=10> and ended up writing to
> ***@***.***
>
> I'm not really expecting someone to answer. The document above, btw, does
> list all second level domains explicitly, albeit in prose text. @dnsguru
> <https://github.com/dnsguru> Has that been enough in the past or would
> we rather wait?
>
> —
> Reply to this email directly, view it on GitHub
> <#1903 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AACQTJKCPJOIWBSQYDGU7CTYFX5SBAVCNFSM6AAAAAA7VB4AWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSG44DGNJQGM>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I can contact the registry. Our friends in Azerbaijan can guide us. Let me see what I can do. I will inform |
outstanding - that follows #1439 which is pinned to the issues list |
@rserit I'll close this. Feel free to re-open if you get any new information but this should eventually be a PR anyway. |
Hi. az domains working well except co.az.
When you parse "xyz.co.az", TLD name is "az", registrable domain is "co.az". It's wrong because list file is not include "co.az".
Could you update?
The text was updated successfully, but these errors were encountered: