My apologies again, you are correct. I ran a named -v on the boxes,
forgetting that we were directly calling bind in a non-path. We are
in fact using 9.4.2-P2 on everything, patched to protect against
kaminsky. We will look at an upgrade program to get these boxes
(about 80 servers,
Hello,
I have an issue with 9.5.3 on which I see that bind does a reload of the
named.conf but does not reload the include files which are in named.conf
Situation:
I do an add or change of name / ip in Plesk, plesk nicely rsyncs the
zone files to our two name servers.
nameserver 2 reloads
Jeff Lightner wrote:
And of course you can legitimately say it is a Standard even if it
isn't enforced by the software. Your argument would be that people
implementing new servers or attempting to access the systems wouldn't be
able to do so because they wouldn't have added the exception to
On Wed, 25 Feb 2009, Martin Moerman wrote:
Hello,
I have an issue with 9.5.3 on which I see that bind does a reload of the
named.conf but does not reload the include files which are in named.conf
9.5.3 doesn't exist.
Situation:
I do an add or change of name / ip in Plesk, plesk nicely
Certainly, several large organizations (Google, Yahoo and CNN, to name 3)
are using at least 1: m
Not to mention all the root-server operators. So the rule clearly
isn't being enforced very well. :)
Actually, to be lawyerly about it, while RFC952 says you can't have
a single-character name,
At Wed, 25 Feb 2009 14:17:27 -0600,
Timothy Holtzen t...@nebrwesleyan.edu wrote:
I applied the patch on my test system and ran my little test using wget
and this is the output I got in the log
Feb 25 13:51:12 arthur named[17030]: libxml2 Error: Input is not proper
UTF-8, indicate encoding !
On 25-Feb-2009, at 16:46, Mike Bernhardt wrote:
So what is the accepted view on this currently? Is there another RFC
that
has made it OK now?
I'm not going to say this definitively, because I'm not certain, but I
think 952 may have been updated by a later RFC. Certainly there are
7 matches
Mail list logo
