Seeking IANA ccTLD contact
At some point during or after Neustar .us bits were assigned to GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess. If you're an authoritative person that can help get this sorted, or have contact information for that person or persons, please reach out to me. Thank you, Chad D
What does IANA have to do with it ? If you have any quarrels with the .us registry, its governing authority seems to be GAO (https://www.gao.gov). If it's not GAO, it will be someone else from Uncle Sam... Rubens On Fri, Sep 6, 2024 at 10:34 AM Chad Dailey <whammyster@gmail.com> wrote:
At some point during or after Neustar .us bits were assigned to GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess.
If you're an authoritative person that can help get this sorted, or have contact information for that person or persons, please reach out to me.
Thank you, Chad D
Not really an escalation point above the registrar level. https://www.icann.org/resources/pages/about-icann-faqs-2019-02-25-en Q: Does ICANN help with domain ownership or registration disputes?
A: *No*, ICANN does not get involved in disputes regarding domain ownership or registration. ICANN's role is at the policy level, in ensuring that registries and registrars comply with policies related to those issues, developed through a bottom-up, consensus-based multistakeholder process.
https://www.about.us/policies https://www.about.us/documents/policies/usTLD_Dispute_Resolution_Policy_(usD... On Fri, Sep 6, 2024 at 9:35 AM Chad Dailey <whammyster@gmail.com> wrote:
At some point during or after Neustar .us bits were assigned to GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess.
If you're an authoritative person that can help get this sorted, or have contact information for that person or persons, please reach out to me.
Thank you, Chad D
GoDaddy Registry is the .us registry operator so I assumed that the mention to GoDaddy was about the registry. But you are right, it could be about GoDaddy as the registrar for the domain. So the OP needs to clarify which one is the issue with, indeed. Rubens On Fri, Sep 6, 2024 at 7:18 PM Tom Beecher <beecher@beecher.cc> wrote:
Not really an escalation point above the registrar level.
https://www.icann.org/resources/pages/about-icann-faqs-2019-02-25-en
Q: Does ICANN help with domain ownership or registration disputes?
A: No, ICANN does not get involved in disputes regarding domain ownership or registration. ICANN's role is at the policy level, in ensuring that registries and registrars comply with policies related to those issues, developed through a bottom-up, consensus-based multistakeholder process.
https://www.about.us/documents/policies/usTLD_Dispute_Resolution_Policy_(usD...
On Fri, Sep 6, 2024 at 9:35 AM Chad Dailey <whammyster@gmail.com> wrote:
At some point during or after Neustar .us bits were assigned to GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess.
If you're an authoritative person that can help get this sorted, or have contact information for that person or persons, please reach out to me.
Thank you, Chad D
I'm just trying to figure out which intelligent human I can talk to, to get this sorted out. The original request to GoDaddy as the registrar was to update stale domain administrative data to resolve a technical issue, which is failing at this time, since they claim a registrar hold, whatever that means. I understand that we're all busy, I'm trying to stop this from becoming an expensive black hole. We ($govtdayjob administrative folks and myself) are trying to understand the relationship here in good faith, terse ticket messaging does not increase our understanding of the issues at hand, or point us to authoritative sources for timely resolution. My stamina and free time to resolve this is low, but the lawyer types seem oddly energized. Probably best just to let them chase it. On Fri, Sep 6, 2024 at 9:19 PM Rubens Kuhl <rubensk@gmail.com> wrote:
GoDaddy Registry is the .us registry operator so I assumed that the mention to GoDaddy was about the registry. But you are right, it could be about GoDaddy as the registrar for the domain. So the OP needs to clarify which one is the issue with, indeed.
Rubens
On Fri, Sep 6, 2024 at 7:18 PM Tom Beecher <beecher@beecher.cc> wrote:
Not really an escalation point above the registrar level.
https://www.icann.org/resources/pages/about-icann-faqs-2019-02-25-en
Q: Does ICANN help with domain ownership or registration disputes?
A: No, ICANN does not get involved in disputes regarding domain
ownership or registration. ICANN's role is at the policy level, in ensuring that registries and registrars comply with policies related to those issues, developed through a bottom-up, consensus-based multistakeholder process.
https://www.about.us/documents/policies/usTLD_Dispute_Resolution_Policy_(usD...
On Fri, Sep 6, 2024 at 9:35 AM Chad Dailey <whammyster@gmail.com> wrote:
At some point during or after Neustar .us bits were assigned to
GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess.
If you're an authoritative person that can help get this sorted, or
have contact information for that person or persons, please reach out to me.
Thank you, Chad D
In that case escalating to the registry is indeed a reasonable path at this point. Although they are both GoDaddy group companies, they operate with de facto separation between them. The links at https:/about.us were mentioned previously in the thread. Rubens On Sat, Sep 7, 2024 at 11:17 AM Chad Dailey <whammyster@gmail.com> wrote:
I'm just trying to figure out which intelligent human I can talk to, to get this sorted out. The original request to GoDaddy as the registrar was to update stale domain administrative data to resolve a technical issue, which is failing at this time, since they claim a registrar hold, whatever that means. I understand that we're all busy, I'm trying to stop this from becoming an expensive black hole. We ($govtdayjob administrative folks and myself) are trying to understand the relationship here in good faith, terse ticket messaging does not increase our understanding of the issues at hand, or point us to authoritative sources for timely resolution.
My stamina and free time to resolve this is low, but the lawyer types seem oddly energized. Probably best just to let them chase it.
On Fri, Sep 6, 2024 at 9:19 PM Rubens Kuhl <rubensk@gmail.com> wrote:
GoDaddy Registry is the .us registry operator so I assumed that the mention to GoDaddy was about the registry. But you are right, it could be about GoDaddy as the registrar for the domain. So the OP needs to clarify which one is the issue with, indeed.
Rubens
On Fri, Sep 6, 2024 at 7:18 PM Tom Beecher <beecher@beecher.cc> wrote:
Not really an escalation point above the registrar level.
https://www.icann.org/resources/pages/about-icann-faqs-2019-02-25-en
Q: Does ICANN help with domain ownership or registration disputes?
A: No, ICANN does not get involved in disputes regarding domain ownership or registration. ICANN's role is at the policy level, in ensuring that registries and registrars comply with policies related to those issues, developed through a bottom-up, consensus-based multistakeholder process.
https://www.about.us/documents/policies/usTLD_Dispute_Resolution_Policy_(usD...
On Fri, Sep 6, 2024 at 9:35 AM Chad Dailey <whammyster@gmail.com> wrote:
At some point during or after Neustar .us bits were assigned to GoDaddy, we lost administrative control over some $govtdayjob namespace, and it is claimed to now be held by the registry. Fast forward, we have a need to get things properly aligned. Have been trying to get things sorted out in good faith but the process is dragging on, and we are getting the side-eye from leadership because we're not getting a related issue resolved. I have a case number and supporting documentation, for what it's worth. Next step is legal, and I'd really like to avoid that mess.
If you're an authoritative person that can help get this sorted, or have contact information for that person or persons, please reach out to me.
Thank you, Chad D
participants (3)
-
Chad Dailey -
Rubens Kuhl -
Tom Beecher