Hi Experts,
After bind upgradation from 9.4.3p3 to 9.7.1p2 ,I am unable to check rndc
status. Error Message:
rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not authorized to connect,
* the clock
Hi Anand.
It sounds like when did the upgrade that either you didn't install the
new rndc utility, or it installed somewhere else rather than replacing
the old one that you encounter first from your path variable?
If you did a make install, did you give configure the same parameters
that you
In article ,
David Miller wrote:
> You can have a different TTL for each and every record, if you like, in
> the same zone file with no includes (the $TTL directive can appear
> multiple times).
>
> e.g. :
>
> $TTL 300; 5 mins
> *PTRhost-no-spec.example.com.
> $TTL 3600; 1 ho
hello everybody..
I was playing on my gentoo box: a couple of virtual machines, client and
dhcp/bind server.
both services do their job - separately. I tried to configure the dynamic
update, but my log said (weird things *highlighted):
named[17833]: starting BIND 9.4.3-P5 -u named -n 1
named[17
On 10/07/2010 05:40 PM, Eivind Olsen wrote:
--On 7. oktober 2010 16.55.54 -0500 groups wrote:
One party thinks that disabling query logging will give enormous
performance gains, while 30% is a lot.. IMHO it is very negligible in CPU
cycles when the named process only is taking up > 10% CPU..
an
You are telling dhcp to talk to your DNS server at ip address
192.168.1.250 and it's not listening on that ip address. According to
your named.conf, it's only listening on 127.0.0.1.
Plus you need an A record for ns.localzone.local.
Lyle Giese
LCR Computer Services, Inc.
tangonig...@yahoo.it wro
GREAT!
it works like a charm now, thanks!
On Friday 8 October 2010 15:32:25 Lyle Giese wrote:
> You are telling dhcp to talk to your DNS server at ip address
> 192.168.1.250 and it's not listening on that ip address. According to
> your named.conf, it's only listening on 127.0.0.1.
>
> Plus you n
On BIND 9.7.1-P2 I have in named.conf:
channel query-errors-log {
file "/var/log/named.query-errors.log" versions 3 size 200k;
print-category yes;
print-severity yes;
print-time yes;
severity info;
};
category query-e
You have to set a debug level of at least 1 to capture SERVFAIL errors
in your logfile.
Ciao
Torsten
Am Fri, 8 Oct 2010 09:09:16 -0500 (CDT)
schrieb b19...@anl.gov (Barry Finkel):
> On BIND 9.7.1-P2 I have in named.conf:
>
> channel query-errors-log {
> file "/var/log/named
Am Fri, 8 Oct 2010 09:09:16 -0500 (CDT)
schrieb b19...@anl.gov (Barry Finkel):
>> On BIND 9.7.1-P2 I have in named.conf:
>>
>> channel query-errors-log {
>> file "/var/log/named.query-errors.log" versions 3 size
>> 200k; print-category yes;
>> print-severity yes;
>
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
All..
We have 2008 M$ dns servers (running M$ DNS ) and bind servers on Linux
We are looking to tweak the M$ servers down to the same "level" as
the bind servers.. if possible..
the bind logging statement
-
category lame-servers { null; };
category resolver { null; };
categor
In message <20101008163912.378754d...@britaine.cis.anl.gov>, Barry Finkel write
s:
> Am Fri, 8 Oct 2010 09:09:16 -0500 (CDT)
> schrieb b19...@anl.gov (Barry Finkel):
>
> >> On BIND 9.7.1-P2 I have in named.conf:
> >>
> >> channel query-errors-log {
> >> file "/var/log/named.qu
13 matches
Mail list logo