@ajstringham said:
@JaredBusch said:
@ajstringham said:
@thecreativeone91 said:
@ajstringham What is it currently doing/what's your error?
The site currently loads my site correctly but not the other website. Everything appears to be setup correctly. I can't figure out what the issue is.
Assuming this is still hosted internally, is your hairpin NAT rules picking up the second DNS name and rerouting appropriately? I cannot think of a scenario that wouldn't since it should all revolve around the IP, but just another thing to check.
Hairpin NAT rules?
When you host stuff at home, you will have a problem with NAT.
daerma.com resolves publicly my current IP.
but the internal server is on a local IP of course.
By default that means daerma.com should not be reachable from inside my network. because a DNS lookup will return the public IP. A router running standard NAT masquerade rules will not route it correctly because it is targeting the WAN port of the router from the LAN.
So there were special NAT rules called hairpining designed to handle it.
http://en.wikipedia.org/wiki/Hairpinning
Almost every home router has it enabled by defualt. I have no idea how dd-wrt handles it, other than to know it has the functionality.
