Short version ...
Setup a CentOS 6 test server without DNS just for testing for a rather large corp using Moodle remotely hosted (outside the confines of corp network - apparently the person training cannot get internal technical support). Purpose to test webservices. Yes, without DNS ... access via host file 'trick'. Test server had self-signed certificate and running https:// ... Moodle configured to use https:// ... all that worked just fine. Person doing the webservices part was successful in testing.
The 'next phase' in the 'plan' (not mine) was to use a valid CA and test with that. So embarked on setting up a valid CA (company doesn't matter). Result ... regardless of what I did/tried, couldn't get this stealthy Apache to use certificate acquired. Finally, an expert says ... 'No. Can't be done. Server *must* have a valid DNS".
Lesson learned ... the hard way - have spent 10 hours learning that lesson. :|
On another note, couple of related question ... if anyone knows:
Certificates are not issued for life (as we all know) and from time to time, they require renewal. So let's say that happens to a Moodle server - expired and new certificates have not been acquired yet.
How does the remote server/whatever running some app/script to do some action on the Moodle server affect re-acquire the new certs? Or does that matter (networking comes before application).
If that doesn't matter ... what does? The token assigned to the user using webservices?
Yep, if I sound confused it's cause I am!!!