DNS for 3cx hosted PBX resolves to 0.0.0.0

[trurooms]

We were on a trial and just purchased the upgraded pro license with hosting from 3cx.

The issue being that our domain from 3cx XXXX.LOCALE.3cx.us is resolving to 0.0.0.0 both on local network and using a DNS Checker.

In my portal, I see the option to "switch to hosted" and the install is listed as self-managed.

During our trial period, this did not exist.

 

[SteveITS]

Just to ask, you've successfully entered the new license key into the server?

 

[NikosT_3CX]

@trurooms I have checked your FQDN and it resolves correclty.
Validate always with Google DNS, " https://dns.google/ "

 

[myitbrainHQ]

A 3CX-hosted PBX resolving to 0.0.0.0 almost always points to one of two things: the DNS record has not propagated yet after provisioning, or the 3CX cloud instance is in a failed/suspended state.

Here is how to diagnose:

1. Log into your 3CX management console (portal.3cx.com) and check if the instance shows as Running. If it shows Stopped or Error, restart it from the portal first.
2. Check DNS propagation using a tool like dnschecker.org - look up your FQDN (e.g. yourname.3cx.us) and see what resolves globally. If most nodes show 0.0.0.0 or NXDOMAIN, the record is either not set yet or was cleared.
3. If the instance is running but DNS is bad, go into the 3CX portal, find your instance, and look for the option to re-apply or regenerate the DNS record. Sometimes a reprovisioning cycle fixes it.
4. Also check whether you recently changed hosting plans or regions - a migration can temporarily break DNS assignment until the new IP is propagated.

If the instance is running and DNS still resolves to 0.0.0.0 after 24 hours, open a support ticket with 3CX directly via the partner portal - this is a backend provisioning issue they need to fix on their end.