[Ilugc] one host IP resolvable to two different hostname
- From: roshan@xxxxxxxxx (Roshan George)
- Date: Sun, 23 Oct 2011 13:35:02 +0530
On Sun, 2011-10-23 at 06:38 +0530, smal at ccmb.res.in wrote:
192.168.1.2 TO peter.alex.com
192.168.1.3 TO xavier.alex.com
127.242.116.226 TO both peter.alex.com& xavier.alex.com
Hello,
Unfortunately, we're having trouble understanding your question. Let us
see if we can work it out. First of all, resolution works in the
opposite way to what you seem to believe. You resolve a domain name to
an IP address.
I will attempt to restate your problem and you can say if that is right.
Then we can attempt to solve it.
You have a domain name (example.com) and two subdomains on it
(a.example.com and b.example.com). You want the following to happen:
1. When a user attempts to access a.example.com and b.example.com from a
LAN that you control, you want them to go to 192.168.1.2 and 192.168.1.3
respectively.
2. When a user attempts to access a.example.com or b.example.com from
outside your LAN, you want them to go to 203.0.113.1 (assume this to be
the WAN IP of your server)
Is this what you want to do? Well, the question is, where is the
nameserver for example.com? If you want the same nameserver to serve up
different records based on the origin network of the request, then using
split-horizon will work fine. However, if you have one nameserver on the
Internet (say your host provides one) that already resolves example.com
and subdomains to 203.0.113.1, then let that be. Run a nameserver on
your local network, add a zone to it each for a.example.com and
b.example.com and give them A records pointing to 192.168.1.2 and
192.168.1.3 respectively.
Also, you might want to check with the network admins at IITM. They have
some solution for the problem since ftp.iitm.ac.in resolves to different
addresses depending on the origin network of the request.
Regards,
--
Roshan George <roshan at arjie.com>
Other related posts: