1. A lot of names can point to the same IP address [shared hosting; the response given, for example, by an Apache sever would depend on the site's name passed]. 2. The same name can be resolved into different IP addresses [allowing things like load balancing]. 3. The same name address can be pointed to different sets of IPs depending on what name server you are using [I mean each name server can resolve the different name to different sets of IPs]. For example: you connect and recieve ns1.a_in_isp.com as your name server. Then try to resolve proxy.someisp.com it will give you a set of addresses [nslookup proxy.ispname.com ns1.a_in_isp.com]. Connecting from other city with the same ISP could get some other name server, let's call it ns1.b_in_isp.com, getting a different set of IPs for the same proxy.ispname.com [ nslookup proxy.ispname.com ns1.b_in_isp.com].
Slashdot Mirror
Just for starters:
1. A lot of names can point to the same IP address [shared hosting; the response given, for example, by an Apache sever would depend on the site's name passed].
2. The same name can be resolved into different IP addresses [allowing things like load balancing].
3. The same name address can be pointed to different sets of IPs depending on what name server you are using [I mean each name server can resolve the different name to different sets of IPs]. For example: you connect and recieve ns1.a_in_isp.com as your name server. Then try to resolve proxy.someisp.com it will give you a set of addresses [nslookup proxy.ispname.com ns1.a_in_isp.com]. Connecting from other city with the same ISP could get some other name server, let's call it ns1.b_in_isp.com, getting a different set of IPs for the same proxy.ispname.com [
nslookup proxy.ispname.com ns1.b_in_isp.com].
And I am sure there's a lot more to it.