the advertising?
--
*From:* David Klein r...@nachtmaus.us
*To:* ju wusuo juwu...@yahoo.com
*Cc:* bind-users@lists.isc.org bind-users@lists.isc.org
*Sent:* Wednesday, March 7, 2012 11:18 PM
*Subject:* Re: Anycast DNS
You would need to create a custom script to use as your
You would need to create a custom script to use as your monitor, which does
a lookup of an address that you know will always be in your domain. If that
fails, force-down/inactive the node, and tie this script as a monitor to
the pool holding the DNS server nodes.
You can advertise the /32
With stock DNS, no; all you can do is recommend by ordering the responses.
But there are solutions. There are load-balancing DNS servers (they have a
pool of responses, and hand out an answer of that pool, based on rules, and
can even remove an answer from the pool if a watchdog/monitor fails). F5
I don't know from Power DNS, but BIND expects to have one master where all
changes are initiated, and all other servers receive replication from the
single master, via incremental zone transfers. This is how conflicts and
race conditions are prevented. You would do better to designate one of the
There are tools which do this, such as F5's GTM or Cisco's GSS;
essentially, you have multiple servers in a pool/answer group, and
during normal operations, they are handed out in either RR or WRR. If
one server fails his health-check, he is taken out of the mix. I
believe under the covers, it is
It's a little less novice-friendly than Men Mice, but it has price
going for it. Take a look at GADMIN Tools for BIND
(http://gadmintools.flippedweb.com/index.php?option=com_contenttask=viewid=14Itemid=33).
Even better, take a look at Infoblox NIOS-based IPAM appliance; you
could easily set one
:34 AM, david klein r...@nachtmaus.us wrote:
5 files in a single directory will make difficult for any
filesystem. I would recommend breaking that out into groups of less
than 1 per directory. For better performance, separate them onto
directories that are on different spindles
5 files in a single directory will make difficult for any
filesystem. I would recommend breaking that out into groups of less
than 1 per directory. For better performance, separate them onto
directories that are on different spindles; the parallelization of
seek (and with thousands of
One solution that was floated recently around here was to use dynamically
loaded zones (http://bind-dlz.sourceforge.net/) with an underlying storage
mechanism that does bidirectional replication (a directory service like LDAP
or a database) for the masters, this way, whichever one gets the update,
9 matches
Mail list logo
