On Mon, Apr 28, 2014 at 03:30:40AM +, houguanghua wrote:
Does bind support backup nameserver? This nameserver isn't
regeristered and not accessed in normal situation. Only when
all authority NSs is down, this backup nameserver will be
accessed by Local DNS server.
I guess what you want
We have a remote site that we are providing a bind package for. They want a
targeted build and sent us the compile options as
-xtarget=T3 -xarch=sparcvis3 -xchip=ultraT3 -xcache=8/16/4:6144/64/24
The build system is using Sun Studio 12.3 cc on T5140 (UtltraSPARC-T2+
hardware running Solaris
You are cross compiling. You need to set BUILD_* so that the host tools
are properly built.
% grep BUILD README
BUILD_CC
BUILD_CFLAGS (optional)
BUILD_CPPFLAGS (optional)
BUILD_LDFLAGS (optional)
BUILD_LIBS (optional)
%
Mark
In
I'm not sure this makes sense from an architectural standpoint. If all
of the authoritative NSes are down, where is this backup nameserver
getting its data from, and how current is that data?
If slightly *stale* data is acceptable, in the absence of all
authoritative NSes, then why not just
Hi,
We currently use the Men Mice DNS/IPAM/DHCP suite which is essentially a
front-end wrapper for BIND. We deploy our own BIND boxes and simply install
the Men Mice agent on them which allows us to centrally manage the zones from
a GUI (or CLI) based interface.
I'm curious about the other
On Mon, Apr 28, 2014 at 04:31:28PM +, Baird, Josh wrote:
Hi,
We currently use the Men Mice DNS/IPAM/DHCP suite which is
essentially a front-end wrapper for BIND. We deploy our own BIND
boxes and simply install the Men Mice agent on them which allows us
to centrally manage the zones
Ray,
Overall, MM has worked quite nicely for us. The CLI leaves a lot to be
desired though and we have found several bugs in the application throughout the
past several years (who doesn't have bugs, though?). I have also had a hard
time getting someone on their Sales team to answer my
Josh,
In addition to the appliance-only vendor solutions you mention below, you may
wish look into the BT Diamond IP product line. This is an enterprise and
service provider IPAM solution with full support for DNS and DHCP. It is
available as software-only, with a centralized management
Cisco (apply liberal amounts of salt considering my FROM) has a product
suite called Prime, one piece of which is CNR (unless it's been renamed
again this week) -- Cisco Network Registrar, which handles the IPAM piece
and has DHCP and DNS components as well. CNR can integrate with BIND (as
well
Are you running *other*, non-network-service functions on these boxes
besides BIND/MM? If not, then you might find an appliance-based
solution like Bluecat or Infoblox might be more cost-effective than
adding a DNS-management layer to a generic server. Your security folks
should love you too,
Kevin,
No - our DNS servers do only one thing depending on their role - either to
serve internal clients (caching/recursive/override external authoritative) or
to serve authoritative external clients. I used to cringe at these appliance
based solutions because I want to be in control of BIND
I misspoke a bit about DNSSEC. That's not an OS-level thing (unless you
want to hook in an HSM or something like that), so there's no reason to
think that an appliance-based solution would be better at it than an
agent/wrapper-based solution.
- Kevin
On Apr 28, 2014, at 9:31 AM, Baird, Josh jba...@follett.com wrote:
Hi,
We currently use the Men Mice DNS/IPAM/DHCP suite which is essentially a
front-end wrapper for BIND. We deploy our own BIND boxes and simply
install the Men Mice agent on them which allows us to centrally manage the
13 matches
Mail list logo
