Urgently help needed- FQDN to wrong IP

[Mathijs]

We used our existing FQDN to setup a new server next to existing one. The finalizing of the installation of the new server did not go well so the end result is a FQDN bound to a new IP adress and the old server is not reachable anymore. FQDN resolves to new IP adress. I found the steps change to dynamic ip and restart services but im not sure if this will work for my situation?

Question: How do i get my fqdn to resolve back to my old server? Thanks!

 

[eddv123]

old server is not reachable anymore

Are you talking about the server itself (Windows or Debian instance) or the 3CX System.

If you can get to the server itself I would recommend a complete re-install reallocating the FQDN on installation of the system. FYI in the case of Public IP I normally always allocate this as dynamic just in the event of such issues.

 

[Mathijs]

Are you talking about the server itself (Windows or Debian instance) or the 3CX System.

If you can get to the server itself I would recommend a complete re-install reallocating the FQDN on installation of the system. FYI in the case of Public IP I normally always allocate this as dynamic just in the event of such issues.

no the 3CX server cannot be reached externally anymore, however i can reach it locally. Ok so basically you are saying

- re install
- re allocate FQDN
- do i need to release the FQDN from customer portal or can i just use it?

 

[StefanW]

just restart the system service of 3CX on the old install to re-set the IP to this install.
However due to DNS ttl this might take some time until all DNS server update the IP for this DNS record.

 

[Mathijs]

ok so i restarted all services and set dynamic ip, now im able to reach management console via external ip adress, but via FQDN still not work. Should i change dynamic back to the static IP and then wait unitl the FQDN resolves to correct IP? Then everything should be fine?

 

[eddv123]

Good to hear you can now get access. I am assuming your are using and FQDN and SSL certificate provided by 3CX and not provided/hosted by yourself ?

If you do an nslookup to that FQDN does it resolve ? as @StefanW mentioned this may take some time to propagate around the internet.

 

[Mathijs]

yes if i do a nslookup it resolves to a different ip adress then it should. So now i just wait? Do i need to set 3cx server back to static again?

altough im not sure if i do it right, i get this output:

> *.3cx.nl
Server: UnKnown
Address: 192.168.1.1

Non-authoritative answer:
Name: *.3cx.nl
Address: **.***.***.**

 

[StefanW]

*.3cx.nl cannot be your FQDN of the PBX, mathijs.3cx.nl would be a correct form in this case, can you remember what you set for "Mathijs" in your case?

nslookup [3cx-fqdn] 8.8.8.8

is the syntax to be used, the 8.8.8.8 at the end is optional and will show what google DNS server know about it.

 

[Mathijs]

*.3cx.nl cannot be your FQDN of the PBX, mathijs.3cx.nl would be a correct form in this case, can you remember what you set for "Mathijs" in your case?

nslookup [3cx-fqdn] 8.8.8.8

is the syntax to be used, the 8.8.8.8 at the end is optional and will show what google DNS server know about it.

i know it cannot be *, i just removed the original fqdn just to be safe. i get this output

nslookup itfirst3cx.3cx.nl 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: itfirst3cx.3cx.nl.AD.ITFIRST.nl
Address: 62.221.207.73