Hello,
I have installed bind9 using the make install procedure.
It works but I did not find any startup script to could put in my /etc/init.d/
directory.
I know that if bind is installed via apt-get install (I am using debian linux
version), there is automatically a bind9 startup script in /
> From: hugo hugoo
> Date: Thu, 14 Apr 2011 14:23:56 +
> Sender: bind-users-bounces+oberman=es@lists.isc.org
>
>
> Hello,
>
> I have installed bind9 using the make install procedure. It works but
> I did not find any startup script to could put in my /etc/init.d/
> directory.
>
> I
On 4/14/2011 10:23 AM, hugo hugoo wrote:
> I know that if bind is installed via apt-get install (I am using debian
> linux version), there is automatically a bind9 startup script in
> /etc/init.d/ directory.
Since named "just works" and I do everything else using rndc, I have the
following line i
Sorry, was a long day (for other reasons) here is a maybe an easier to
follow summary.
When the SOA RNAME value does not include the final dot at the end you
append the zone automatically. The zone in this case contains a forward
slash character "/" which is not a valid email address in the domain
On Apr 10, 2011, at 2:42 PM, Parashar Singh wrote:
> We want to be able to point the wild card (*.domain.com) and the root domain
> (domain.com) to the GLB’s while not breaking the other custom prefixes within
> that domain’s record (stage.domain.com, foo.domain.com, etc.).
> Except some 10-20 A
On Thu, 14 Apr 2011, Alan Clegg wrote:
On 4/14/2011 10:23 AM, hugo hugoo wrote:
I know that if bind is installed via apt-get install (I am using debian
linux version), there is automatically a bind9 startup script in
/etc/init.d/ directory.
Since named "just works" and I do everything else u
Justin Krejci wrote:
>
> So I am wondering if this is normal/expected behavior for BIND and if so
> should debug logging or named-checkzone with debugging be able to
> identify this as the problem. Or am I missing something else altogether?
With bind-9.7.3, I get the following log messages with t
YMMV wrt "just works". Yes, running the latest ISC bind can be worthwhile
after the OS distribution stops updating (or before it gets around to
packaging the latest ISC version.)
People considering the approach suggested by David & Alan should be aware
that the OS startup files often do more than
Hi,
I would figure this is a FAQ, but I can't find it. My apologies if I
somehow missed searching properly.
Where can I find a description of what the variables at the end of the
line in the query log mean? For example:
14-Apr-2011 17:27:54.277 queries: client 67.210.0.112#17930: query:
ns1.colo.
> Where can I find a description of what the variables at the end of the
> line in the query log mean? For example:
The full set is +SETDC
+ recursion requested (- no recursion)
S request is signed
E EDNS0 enabled
T TCP (else UDP)
D
On Thu, 14 Apr 2011, Alex wrote:
Hi,
I would figure this is a FAQ, but I can't find it. My apologies if I
somehow missed searching properly.
Where can I find a description of what the variables at the end of the
line in the query log mean? For example:
14-Apr-2011 17:27:54.277 queries: client
It is in the ARM.
http://ftp.isc.org/isc/bind9/cur/9.8/doc/arm/Bv9ARM.ch06.html#id2575842
(search for "queries" or "querylog")
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
12 matches
Mail list logo