Fun with DNS:
Example 1: How to join the party?
party.com resolves to an externally hosted web site, but fun.party.com needs to be able to reach a different server, this one is local at 10.0.2.50, when it is resolved from within the local DNS.
Example 2: Port of no return:
externalwebsite.com forwards to a webserver within the LAN, 10.0.2.9. However, externalwebsite.com:85 needs to resolve to 10.0.2.10, a server running a web-app-based service. Port 85 is forwarded from the NAT router, so that incoming (extenal) traffic goes to the correct place (10.0.2.10:85), and this works, but when precisely "externalwebsite.com:85" is querried from within the LAN, it does not work, because the DNS already points it to 10.0.2.9 (for example for port 80 web traffic).
Are either of these examples possible, and what other configuration needs to take place, other than with DNS, to meet best practices.
Neither example can be done with the Gui front end of this particular server to the best of my current knowledge. I tried to manually update the BIND configuration files, but can not find examples of what exactly I am looking for online, and when I made the changes I expected to work, nothing happened (plus this needs to not result in breaking the DNS.)
This is on OSX Server (Bind 9.10.3), and I am not sure of the relationship of the files for example in '/Library/Server/named' and the GUI front-end of OSX Server.
I'm assuming that working answers would be useful across lots of other *nix and *BSD systems though.