On Mon, Nov 21, 2011 at 17:02, Jos Houtman <j...@hyves.nl> wrote: > Hi, > Why don't you create a short lived (say 5 minutes) A record for > target.example.com. > Under normal circumstances both ns1 and ns2 will return 11.22.33.44 >
Indeed, it must be short-lived. > You can then create a script that monitors the internet connection of isp A. > If that is down, it will update the A records for target.example.com to the > secondary IP adress. Yes, but I'd like something more... elegant than having to mess up the configuration and forcing the DNS server to reload. That said, I just happened to find PowerDNS, whose "PipeBackend" looks mighty interesting: http://doc.powerdns.com/pipebackend-dynamic-resolution.html http://doc.powerdns.com/backends-detail.html#pipebackend > Because your A record has a short timeout, downstream clients should pick up > the new ip address relatively quickly. > However you have to be aware that some ISP ignore such short lived A records > and cache the resolved address for a longer period of time. > I am aware of that. At least that won't be my fault ;-) > Depending on your internet connection, I might consider offloading this > burden to a hosting company. > The BoD will clamor for my neck if after incessantly harassing them to approve my request for a cloud hosting (among others, to implement an authoritative nameserver) I suddenly do an about face and request for a 3rd party DNS hosting ;-) Rgds, -- FdS Pandu E Poluan ~ IT Optimizer ~ • LOPSA Member #15248 • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
