On Wed, Nov 20, 2002 at 03:21:07PM +0530, Sanjay Bhattacharya wrote: > >>You can use DNS round robin scheduling. For this your DNS records must > >>have multiple IP's assigned to a single host. If host name lookup fails > >>then the DNS supplies another IP. > > > >Huh?? How is that possible? > > > >Binand > > > You can have one host assigned multiple IP's by putting several A and > PTR records in the zone files. For instance, > > $ORIGIN testdom.com > test IN A 192.168.1.1 > test IN A 192.168.1.2 > > and > > $ORIGIN 1.168.192.in-addr.arpa > 1 IN PTR test.testdom.com. > 2 IN PTR test.testdom.com. > > Now if a query is made for test.testdom.com and 192.168.1.1 doesn't > respond, bind will supply 192.168.1.2 for the host. To answer your > query, I think thats how it's possible.
Thanks for all that info, but I already knew all this (its something I do to make a living). My question is: How is it possible to have the DNS supply another IP if the host name lookup itself fails for the name?? (Read again your initial post). BTW, bind will not check if an IP is up before serving a DNS record. Its upto the client to query again and again to get all the round robin IP addresses. To ensure that this happens in a transparent way, you need to set the TTL to a really low value (I keep mine at 300s). Binand -- If you found this helpful, please take some time off to rate it: http://svcs.affero.net/rm.php?r=binand ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
