Date: Mon, 15 Jan 2001 21:10:13 -0800 From: "jl" <tech@scsr.com> To: "Jason Fesler" <jfesler@gigo.com>, "Dave Wilson" <davew@sai.co.za> Cc: "Matthew Horoschun" <matthew@actweb.net>, <freebsd-isp@FreeBSD.ORG> Subject: Re: DNS redundancy & load balancing Message-ID: <002b01c07f7a$9b6a8180$6503c23f@XGforce.com> References: <Pine.BSF.4.30.0101150754390.909-100000@heaven.gigo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You may check out www.xgforce.com ----- Original Message ----- From: Jason Fesler <jfesler@gigo.com> To: Dave Wilson <davew@sai.co.za> Cc: Matthew Horoschun <matthew@actweb.net>; <freebsd-isp@FreeBSD.ORG> Sent: Monday, January 15, 2001 7:58 AM Subject: RE: DNS redundancy & load balancing > > Indeed but clients have their primary DNS server set to our primary, thus if > > our primary goes down no resolution takes place. > > Clients have a their seconday DNS set to our secondary DNS, but we've found > > that often M$ machines never even try looking at their secondary DNS server. > > Any ideas ? > > Move your DNS servers to different IP addresses, ones that are not > published. Assign virtual IP addresses (the published ones). If you have > a DNS failure or host failure, you can remove (if needed) the published > virtual IP, and put it on as a second virtual IP on the remaining host. > If you're good, you can even automate this with creative use of a third > host for monitoring and administering the IP changes. > > OF course, you can also just solve this with hardware, ala Alteons and > their like, but most ISP's are too cheap. [Been there, done that, got > screwed on the tshirt. ;-)] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002b01c07f7a$9b6a8180$6503c23f>