dns error resolving fqdn

  1. Solved FQDN Seems Broken?

    I have a 3cx PBX V20 hosted on a lightsail VM. The VM rebooted, public IP changed. I've adjusted in the SIP trunk and can access the seemingly functional PBX via IP address, but we are unable for over 24 hours at this point to access via FQDN thus rendering the phone system at the client down...
  2. Anthony - Sedcom

    Solved DNS issues with SIP Trunks on Host 3cx System

    Hi I have a new client we are going to help manage and having some issues They are moving there SIP lines to my business I have had zero issues with my lines on any of my 3CX systems But this one This System is a 3CX hosted system (we dont use 3CX Hosted systems normally) I have completed...
  3. FQDN not accessible after IPV4 change

    Our google instance recently was reset and picked up a new public IP address. However, the 3CX FQDN is still pointed to the old IP address. How do I update the DNS for the FQDN? I have tried accessing the support page, but keep running into errors and am unable to even open a ticket. Who/what do...
  4. Solved Hosted by 3CX - TLS not connecting with valid settings

    Hi, I have followed the guide here and have been working with Brightstar, and we've hit a brick wall with enabling TLS on the trunk. https://www.3cx.com/docs/brightstar-uk-sip-trunk/ I have double checked the settings so they match the guide but the trunk won't register and I'm currently...
  5. Solved 3CX.co.uk FQDN deleted and license deactivated in portal - due to server inactivity?

    I'm a 3CX Partner and have an NFR license of 3CX Enterprise installed. This was all active and working for a period of months. For security I won't advertise what the FQDN is, but the sake of this query let's say it was contoso.3cx.co.uk. I currently use my NFR for testing new concepts...
  6. SIP trunk registration failure caused by querying wrong DNS record (A record instead of SRV record)

    Hello, Yesterday I upgraded from 3CX 15.5 to 16.0.5.619. After the 3CX service started up, it was repeatedly failing to register with our SIP provider. Note that our SIP provider address is entered as a FQDN and we're using Google (8.8.8.8 and 8.8.4.4) as our DNS servers. I did a packet...
  7. Domain name is not registered

    Hello, I started my instance of 3CX system hosted in Amazon after some months of inactivity. The 3CX domain name (datasur.3cx.com.br) now is not registered, ping displays it cannot resolve the name. I changed the fix IP address, because AWS gave me a different one. How can I do to reassign...
  8. ECOM GROUP (Mauritius)

    Enterprise License 3CX dns Fqdn not resolving in 5 minutes

    Before , the enterprise license was to a customer fqdn, Now i have another installation on premise and the license on it was a Pro with 3cx fqdn I have released the Enterprise license and upgrade the Pro license i just mentioned while keeping the Pro pbx 3cx's fqdn Does the pro fqdn will...
  9. Solved Nexvortex DNS failure after update to 16.0.3.676

    Within minutes of the update to 16.0.3.676, my NexVortex truck failed with this error every few minutes: Registration at Nexvortex has failed. Destination (sip:000.000.000.000:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available. When attempting to...
  10. 3CX: not reachable, DNS error resolving FQDN, or service is not available

    I've made a change to the network with access to WAN and adjusted services accordingly. However, with 3CX (Windows installation, and then replaced with a Debian installation) I'm having such a difficult time getting 3CX working again. I'm receiving the following log messages when registering...