Re: monitoring BIND

Karl Auer wrote: More info to my question: dig and Nagios have been suggested as possible solutions. You can use any plugin targetting the plugin api to make that happen (http://docs.icinga.org/latest/en/pluginapi.html). While Icinga/Nagios will be doing regular active checks for single bind

master slave different site different resolution

Dear lists, I have an issue to resolve about 2 dns server Master/Slave. The Master is positioned in a site with public ip 1.1.1.1 and all the public dns resolutions point to 1.1.1.1 the Slave is positioned in a site whit public ip 2.2.2.2 and obviously all the public dns resolutions point t

Re: BIND 9.6.1-P3 Vulnerabilities

On 07/06/11 16:21, Borgia, Joe A CTR USAF AFMC AFRL/RIOS wrote: > BIND 9.6.1-P3 seems to be a somewhat old release of BIND, and yet, I can > find no vulnerabilities listed on the ISC Security Advisories pages. Am > I missing something? Yes. :-( https://www.isc.org/software/bind/security/matrix CV

Re: master slave different site different resolution

2011/7/14 Gabriele Gabriele : > Dear lists, > > I have an issue to resolve about 2 dns server Master/Slave. > > > The Master is positioned in a site with public ip 1.1.1.1 and all the public > dns resolutions point to 1.1.1.1 > the Slave is positioned in a site whit public ip 2.2.2.2  and obviously

RE: master slave different site different resolution

Ok, may be I was not so clear to explain.. for example I have in my Master work site the our webmail "webmail.mydomain.com" that when Master work site in UP the resolution is 1.1.1.1 but if the master go down in My slave work site, my slave dns resolv "webmail.mydomain.com" with 1.1.1.1 but t

Re: master slave different site different resolution

2011/7/14 Gabriele Gabriele : > Ok, may be I was not so clear to explain.. > > > for example I have in my Master work site the our webmail > "webmail.mydomain.com" that when Master work site in UP the resolution is > 1.1.1.1 but if the master go down in My slave work site, my slave dns resolv > "we

Re: master slave different site different resolution

On 2011-07-14 11:53, Gabriele Gabriele wrote: Ok, may be I was not so clear to explain.. for example I have in my Master work site the our webmail "webmail.mydomain.com" that when Master work site in UP the resolution is 1.1.1.1 but if the master go down in My slave work site, my slave dns reso

RFC 6303 and automatic empty zones

Now that RFC 6303 has been published, and includes the fourteen RFC 1918 reverse zones (section 4.1), can we expect future versions of BIND to have them as automatic empty zones - i.e. the "#ifdef notyet" in bin/named/server.c to disappear? -- Chris Tho

Re: RFC 6303 and automatic empty zones

> Now that RFC 6303 has been > published, and includes the fourteen RFC 1918 reverse zones (section 4.1), > can we expect future versions of BIND to have them as automatic empty > zones - i.e. the "#ifdef notyet" in bin/named/server.c to disappear? Yes.

RE: RFC 6303 and automatic empty zones

Expecting the future - Planning your life around it is something sales folks like to do and most of the rest of us call vaporware - it's always "going to be available the 2nd quarter of next year". -Original Message- From: bind-users-bounces+jlightner=water@lists.isc.org [mailto

bind9.xsl vs. /bind9.xsl

BIND recognises just two URLs on the statistics channel, "/" and "/bind9.xsl". The XML it delivers in response to the first starts ^^ so that a web browser will fetch the second to render the result. I wonder whether it would be better for the hre

Re: bind9.xsl vs. /bind9.xsl

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-07-14 2:28 PM, Chris Thompson wrote: > So is there anything that could go wrong if the style sheet reference *was* > relative rather than absolute? Not that I can see. It's probably that we never considered that use case. Send in a bug repo

Re: Clients get DNS timeouts because ipv6 means more queries for each lookup

In message <4e1d3c05.7040...@kamens.us>, Jonathan Kamens writes: > You seem to have a really big chip on your shoulder about people who run = > broken DNS servers. I don't like them any more than you do. But I=20 > learned "Be generous in what you accept and conservative in what you=20 > generate"