Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Tell HN: Google won't let us get control of our own domain on Google
21 points by 0xbadcafebee on Oct 27, 2022 | hide | past | favorite | 7 comments
Startup is founded. Domain is registered in a 3rd party. Somebody creates a Google Workspace with our domain name. That person leaves... and we don't know who created it, what their email was, etc.

Time passes. DNS for the domain is now managed in our Google Cloud account, in a project with no Organization. In our Google Cloud account, we want to use the domain as a Cloud Identity / Workspace, to create an Organization, to manage our GCP resources hierarchically.

But the domain is being used by the aforementioned Workspace (that we are locked out of). So we can't add it as an Organization to our GCP account. So, we fill out a form to ask Google to give us access to the old Workspace.

Google asks us to create a DNS record to prove we control the domain, and we do so. I get a call at 5am Eastern Time (I guess did say "the morning" was a good time to call...) from Google confirming this, and that they need to check back with their team. Google then sends us challenge questions which only the person who created the original Workspace knows, and that person left and is incommunicado. They say unless we can answer the questions, we can't get access to the account, or have the domain removed from the account.

Meanwhile... we have control of the registrar account, and the DNS for the domain is literally managed in our GCP account. But Google support says we cannot prove we own the domain. So they won't let us use our own domain name for an Organization in our own GCP account, regardless of how we explain the situation.

So we humbly turn to HN in the hopes that somebody from Google will see this and just let us use (& pay for) their own products with the domain that we already own, control, and use in Google Cloud.



If you have access to the registrar, you can point the domain at a different dns provider that you do have access to, and update the details there.


No no, we have access to both the registrar and DNS provider, and have already updated DNS as instructed by Google. (We're doing the DNS in Google Cloud) They don't seem to care that we control the domain...


Time to lawyer up, either to the person that left or to Google themselves.


I'm curious what the legal obligations are for the person that left. AFAIK, there aren't any requirements that they continue supporting the systems they maintained after their employment ends.


Google has criteria for domain hostage situations, so I'd say it depends on whether an employee used company funds to register it on behalf of the org.

It seems like a simple matter of providing internal communication about the domain that includes the approval to purchase to prove ownership.

If that doesn't exist, OP needs to mend some bridges, ask very nicely for a transfer, and be prepared to offer to buy the domain off its "owner".


I’d start with offering the ex employee $1000 to resolve the issue before getting a lawyer involved. Not sure what legal standing you’d have.


That's a good way to lose money in a countersuit. The former employee had no obligation to do anything right now.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: