Pinging that from a command line works fine, however the host does not respond to any pings. Going to that address in a web browser results in a nearly empty XML document, so obviously the host is up, responding, and I can get to it from our phone system. Not sure why that isn’t working.
Definitely nothing to do with DNS. If resolv.conf were having issues, I wouldn’t be able to ping that host from the CLI. That’s why this is a strange error being that katanafpbx.schmoozecom.com is undoubtedly resolvable.
I was able to get this to work by adding katanafpbx.schmoozecom.com and its IP address to the hosts file on the phone system. Very strange since I got the IP for katanafpbx.schmoozecom.com from the CLI on the phone system.