@DustinB3403 If it is not DNS, firewall is always a problem lol. Nice find.

I find it to not be of concern. I would never have it happen, because it's a bizarre and problematic way to handle internal DNS. But anyone who can exploit private IP mapping can figure it out without DNS in the first place. So I see no reason to want to hide it.

@Pete-S said in What subdomain for web conference/meetings?:

Thanks!

meet.example.com looks more generic so I'll use that.

I agree. Seems potentially less confusing for users.

@johnhooks said:

semanage port -m -t http_port_t -p tcp 4567

I had to add semanage first but then it worked.