Replying to own post ... how sick is that? :\
One more reason to use FQDN ... it's probably a good idea to run any web service under https rather than http. While one could use a self-generated certificate all browsers and devices will complain about that as the cert is not from a Certificate of Authority (CA). One cannot acquire a valid cert from a CA using private IP addresses ... must use FQDN of the server when submitting a certificate request to a CA - ie, the server's hostname/domain must be found in public DNS.
While one could acquire a wildcard cert to supposedly get around that, it still makes using both private IP and public IP still a bad choice ... there would have to be a cert for the private IP and a cert for public IP, me thinks by the same host name/TLD. Would a browser/device get confused about that?
Anyway ... additional 2 cents ...
'spirit of sharing', Ken