Allow FQDN's in Security Console Restrictions, please

[uptime1]

Hello, we prudently use Security, Console Restrictions to limit who can access the management interface.
We also leverage FQDN's to dynamically and securely recognize authorized console users.
Now or in the near future, is there any way FQDN's can be added to the Console Restrictions, please?
Adding a note field for an entry will also be help us easily remember why IP's and FQDN's were added.
Thanks!

 

[Alphabetic]

3CX has always said it shouldnt be the first line of defense. I would recommend getting a router that can support the feature youre looking for, maybe a sonicwall? Also, with the implimentaton of 2FA in v20 this will add another layer of security you can use.

 

[uptime1]

Indeed, firewall already in place but firewalls can't discern between a 3CX console admin login vs a user login.

My request for FQDN based Console Access still stands. FQDN also gives our support staff additional flexibility to access the 3CX server remotely, including when they're outside the office, just as I was onsite with a customer and needed to reach the 3CX server to make adjustments for them. If the 3CX server was empowered to support FQDN-based Console Access, I could have gotten in immediately and wouldn't have been delayed and impeded in helping my customer, thereby freeing up more time to sell more 3CX licenses! This situation is even more pronounced when on a mobile Internet connection which always changes IP addresses. FQDN will help maintain console security while allowing those who need go get in.

 

[SteveITS]

I can see the usefulness. Not all routers/firewalls can do this but we’ve used it. The device does a DNS lookup for each name every 5 minutes or so.