Thanks but that was not the question.
I read your answer as: No, opalstack dns management only dickers with records related to the local VPN/shared-host you have
The question was:
Can I manage actual, real, proper DNS records?
I just pointed my WHOLE domain to OS' NS servers. Why can't I add "static.joesdomain.com" CNAME pointing to my AWS buckets? or "stream.joesdomain.com" CNAME to "joes.streamingvideo.com" ?
Solution = don't point your DNS records/mgmt to opalstack. Manually configure an external DNS provider to deal with the MX, SRV, TXT, CNAME records ... and ? also mirror the needed records at opalstack? ro its reverse proxy knows how to point the name to the VPN you're paying for ?? <--- thats a question