forward-zones recursor option takes multiple IPs for a domain.

Bind does this:

zone "some.rbl." {

type forward; forward first; forwarders { 10.0.0.1; 10.0.0.2; };

};

Which would make bind forward requests to the two listed forwards and fall back to standard recursion if neither where available.

Keep a good job up! http://quick-adult-links.com

another option would be to use a syntax similar to auth-zones where forward-zones=foozone.com=/var/foozone.com

/var/foozone.com would contain IP's one per line 10.0.0.1 10.0.0.2 and pdns-recursor would randomly send queries to each IP's. This is similar in approach to what dnscache uses for split-horizon DNS

wholesale designer perfume modern sofa bed canopy bed accessory lalique perfume electric adjustable bed chanel chance perfume chair converts to bed wicker dog bed jennifer sofa bed little tikes sports car twin bed canopy day bed adjustable bed electric uk discontinued coty perfume kid canopy bed twin sleigh bed discount bed linens full size canopy bed discontinued perfume hawaiian print bed sheets hospital bed matress designer perfume oil discount bed linens cool water perfume sealy chair bed adjustable bed sheets

buy motorcycle boots swim dress dress up dolls games pink motorcycle boots little black dress womens harley davidson boots furniture twin bed tanning bed bulbs fossil watches discount flower girl dress diehard work boots summer dresses tempurpedic adjustable bed italian motorcycle boots dress prom canopy bed metal italian hiking boots san francisco mother of bride dresses 1 futon with bunk bed winter hiking boots

At the risk of being a "me too", this feature is singlehandedly preventing us from replacing our internal BIND forwarders with PowerDNS. Being able to forward to multiple servers in case of failure is a requirement for any HA infastructure.

Same here, we have a setup of two recursors used for the mailclusters which are configured to forward to rbldnsd on the same box (another port) or, if not reachable, to the rbldnsd running on the sibling.

The ability to configure not only several IP(v4|v6) addresses but also port numbers would be greatly appreciated.

Thanks for the great work.

Bert, it looks like your r963 fixes this:

http://wiki.powerdns.com/cgi-bin/trac.fcgi/changeset/963

Replying to anon:

Bert, it looks like your r963 fixes this: http://wiki.powerdns.com/cgi-bin/trac.fcgi/changeset/963

I don't think so, that allows you to move the definition of forward zones to an external file, but it still only allows exactly one IP per zone. You cannot specify multiple zones according to the sample config, and reading the code in the changeset I'm pretty sure that is not possible yet.

Path that allows multiple IPs per forward zone

I've attached a patch to allow multiple IPs for each forwarded zone, separated by semi-colons. This works with both the forward-zones and forward-zones-file options.

Since the recursor is already capable of using multiple nameservers for a domain, this was just a matter of passing a vector along instead of a single string. The built-in health/performance tracking of the servers also automatically applies.

-- Aaron Thompson acthompson@gmail.com

Bert, any chance of getting this patch in before the release of 3.1.5? For cleanliness, forward-zones-file should probably also be fixed to support several forwarders per zone..

Updated patch for snapshot4, also has support for forward-zones-file (separate forwarders with comma)

Implemented in commit 1168, and documented as well, thanks!