FWIW, you're in a bad IP netblock for potential future use of VPNs. Get out of 192.168.0.0/24 and 192.168.1.0/24 and into some other subnet in 192.168.0.0/16, or a subnet somewhere within the 172.16.0.0/12 or 10.0.0.0/8 private blocks. FWIW, VPNs are based on IP routing and IP routing usually gets confused when the same subnet is found on both ends of the route, and the VPN tends to get tangled — and 192.168.0.0/24 and 192.168.1.0/24 are two of the most common subnets used for home networks and coffee shop networks.
The local DNS is offline or is somehow misconfigured, or the first two commands would have returned responses — that 72.9.2.40 was entered on that third (-x, DNS reverse translation) command implies an unfamiliarity with what's going on here and what's required to happen within DNS — this given that there was no address from the second command, there would be nothing to enter as an IP address for the third (-x, reverse) command.
Establishing local (private) DNS is necessary when using a private IP address space. Neither ISP nor Google DNS can provide the necessary (reverse) translations. Configuring DNS services (somewhere) cannot be skipped.
Get the local DNS configured per the directions I've linked to earlier.
I'd discourage using the same domain inside and out, as that can and usually will lead to more confusion and grief over time. Use either a subdomain of your registered domain (private.persistence-technologies.com or some such), or use a different domain you've registered. Leave your persistence-technologies.com to your public DNS servers. (I usually use a second domain, as using a subdomain leads to more typing of a longer domain over time.)
The server host name is set in Server.app. In the image below, you'll have foo.example.com or mail.example.com next to the upper green ball and foo or mail in the second green ball (where example.com is the domain or the subdomain you're going to use inside your network firewall and on your private, NAT'd network, and foo or mail is the name of the server you're using), and you'll have that name to IP address translation in your local DNS (preferrably not in the 192.168.0.0/24 and 192.168.1.0/24 subnets), and (if you're using a different domain or subdomain inside your network) you'll have persistence-technologies.com as a virtual domain name in the Mail settings for the Provide mail for... settings (press the Edit button to get to the Virtual Domain stuff) in Server.app settings for Mail.
Here is the location for the general host name settings in Server.app; select the name of the server at the top of the left column to see this:

If all else fails here and if you've started various other services within Server.app before getting DNS going (this tends to get the old name embedded in the various services, and can sometimes lead to problems after a host name change), then things are going to be more difficult; if there's not a great deal of accumulated settings yet, I'd encourage a complete system backup or two, and would then probably either remove and clobber the saved settings from Server.app and then reload Server.app here, establish IP and then DNS first, then get the other services configured and going. Here's the closest Apple support article to a Server.app delete and reset and reload restart sequence for performing a Mavericks Server Server.app reset. Once Server.app is redownloaded and reset, then get IP and DNS configured.