FQDN new static ip

[nicholas.talisma]

Guys, I had a question about the time it takes for the FQDN to be provisioned after a new static IP is set in the system, as I was forced to change my provider's IP and now I've been waiting for a few hours.
Does anyone know more or less how long it takes for this to happen?

 

[SteveITS]

Pro licenses have a 6 hour TTL, Enterprise is 5 minutes.

If you query 3CX's name servers directly and still get the old IP ensure it's been picked up...try restarting your server, or changing your Network settings in the 3CX admin panel to Dynamic, then back to static.

 

[nicholas.talisma]

Thanks Steve, now we just have to wait and see what happens. The new IP has been pinging for a few hours now. I'll see if there's anything else tomorrow if it's not online yet. I bet my money that the provider's firewall is blocking something.

 

[bitn2]

Just switch to dynamic ip in 3cx, wait for some minutes and switch back.

 

[nicholas.talisma]

Things got a little more complicated, outside the company it works and inside the company it doesn't open for anything. What luck, right? =]

 

[NicholasP_3CX]

Ensure your machines can resolve the correct IP address INTERNALLY. Or, alternatively, that your firewall allows for hairpin NAT to allow you to communicate with it based on the external IP Address.

This is a network misconfiguration that you will need to resolve.

 

[bitn2]

Did you configured split dns correctly?

 

[nicholas.talisma]

I'm testing it here, because it's very strange that it's working without this before changing the fixed IP, my firewall is an RB 3011 routerOS 6.
But let's get this thing working =]
I did the hairpin and now it's working inside the company, but outside it's not working anymore '-'

 

[SteveITS]

Typically hairpin NAT doesn't affect normal NAT rules, at least on any router I've used. Do you have a local DNS server on the network? (e.g. Windows Server)

 

[nicholas.talisma]

Yes, I have one, but it does not affect my company's wifi, its DNS is in the RB. The Windows Server DNS only affects the machines that are on the cable redirected to it directly, but I'm going to do a configuration there too since my WiFi and my wired network are on different networks set to prevent access from unauthorized points, so the network that holds the WiFi, say 192.168.1.0, does not talk to the network where the Windows Server DNS runs 192.168.2.0.

 

[SteveITS]

Hmm, well split DNS would work for the Windows network but then you're left with the wireless and external. Sounds like in your setup wireless would need the NAT hairpin/reflection but external access needs that off...seems to be a router issue to sort out.

 

[nicholas.talisma]

Guys, I found out the reason for everything. The hairpin was working, the FQDN was working too. After a lot of research and testing, I discovered that it was a firewall on my provider's routerboard that was active with the redirection rules to go back to itself.
The problem was solved. Thank you very much for your help and your time. You guys are awesome.