Domains with routable IPs cannot access their own forwarded ports

[KevinLai]

Domains that have been allocated a routable (non-NAT) IP address cannot access forwarded ports on the physical machine. Packets leave the interface with the routable IP address and are NAT-ed through the physical machine and back to the domain. However, the source address of these packets is the routable IP address, which is used by the destination machine. I'm not exactly sure what the logic is, but it probably sees that the packet is from its own interface and drops it.

One way to fix this is to add a route to direct traffic to the physical machine through the NAT-ed interface.