Solved WebMeeting QoS

[Evolute IT]

Hi 3CX Team,

We had set in our firewall the QOS rules for mcu.3cx.net which had all the server IPs for easy QOS shaping.

However, it seems that FQDN doesn't resolve anymore.

Is there a new one we can use for this?

 

[SteveITS]

It looks like those are still changing over time. The last I read (here, somewhere, I think) was:

https://www.3cx.com/3cxacademy/videos/basic/nat-port-forwarding/
slide 11
"Check the TXT DNS Records for each of the FQDNs listed there, and you will find the IPs.
This is an ever changing list of IPs so if it is for routing purposes, I'd check it regularly."

Prior to that I had found info on using zone-a.3cx.net for A-F, and I, though I see G and H do exist now. However north-america.3cx.net isn't any of those IPs. At one point 3CX had a blog post on Webmeeting QoS but it has been removed.

Overall it doesn't appear there's a great way to maintain a list for traffic prioritization other than manually check the TXT records.

 

[StefanW]

You can use

nslookup qos.3cx.net

when you are checking for v18 processing services. To note, those service IPs are ephemeral and might change rapetly.

 

[Evolute IT]

You can use

nslookup qos.3cx.net

when you are checking for v18 processing services. To note, those service IPs are ephemeral and might change rapetly.

No worries, I use the FQDN as target in my firewall.

Thanks!