DNS pointing a subdomain of ours to another's server
Posted on 2006-05-16
A user started a pilot site and hosted it with the web developer that created the site. In order to lend credibility to the site, they wanted to call it PILOT.OURDOMAIN.ORG, so I set up an A record on our authoritative DNS for that subdomain to point to their IP address. It works fine for people who aren't behind our firewall, but when we try to go there from within our network, we get a "site not found" error. Running 2003 server as our internal DNS server ( which is why I ask it in this area - If I'm wrong please let me know where ). I'm thinking I need to set up something on our internal DNS, but not really sure how to proceed. Maybe the fact that it is a "subdomain" of ours is messing with the resolution? I'm a little sketchy when it comes to specifics of DNS servers.... In looking at our internal DNS, I see some "forward lookup zones" and am wondering if I should add one for PILOT.OURDOMAIN.ORG? And how? Trouble is, if I simply point the subdomain name to an IP address, they might just get the default page of that server ( the guy at the web developer tells me they're using Apache to redirect ) When I just type in the IP in a browser, I get a different site than the one I should for the IP they gave me to enter into our authoritative DNS, and different from the one people get who are outside our firewall and type in PILOT.OURDOMAIN.ORG.
It's a confusing scenario....a bandaid on a workaround to make the marketing people happy.