On 17 Jan 2013, at 20:58, Mike Hoskins (michoski) wrote:
Syslog as the default is perfectly fine with us.
Please keep that as the default, following the
principle of least astonishment.
I do also use the rotated file method a few places, so hoping that doesn't
disappear.
On 18 Jan 2013, at 06:27, Jan-Piet Mens wrote:
Could CLI utility be man(1) and info(1)? :-)
It could, yes, but `b10-msg NNN` isn't going to break BIND 10's
development budget (I hope),
+1
and I feel it to be more practical than
scrolling through a man page with 900+
On 17 Jan 2013, at 18:33, Jeremy C. Reed wrote:
BIND 9 by default has logging using syslog, using its daemon facility,
and logging of info or higher.
Is using syslog a sane default for new installations or when using
official vendor packages with their startup scripts?
All,
On Friday, 2013-01-18 10:01:49 +,
Niall O'Reilly niall.orei...@ucd.ie wrote:
On 18 Jan 2013, at 06:27, Jan-Piet Mens wrote:
Could CLI utility be man(1) and info(1)? :-)
It could, yes, but `b10-msg NNN` isn't going to break BIND 10's
development budget (I hope),
These are the outputs. I also attach the file containing them.
; DiG 9.8.1-P1 ns . +norec +noedns @198.41.0.4
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 25625
;; flags: qr ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14
;; QUESTION SECTION:
On Jan 18, 2013, at 9:44 AM, Daniele d.imbrog...@gmail.com wrote:
These are the outputs. I also attach the file containing them.
[ SNIP ]
Weird….
Do things work well enough for:
dig +short rs.dns-oarc.net txt
?
Can you also do:
the following queries starting with the
slightly less
Hi,
I have an issue with domain forwarding.
I'm managing public DNS servers for, say, mydomain.com.
We're currently setting a storage system which relies on DNS for load
balancing. The system is made of 4 nodes with IP addresses 10.0.0.1, 2, 3, 4.
The vendor recommands a stub zone to be
What do you have against Internet clients querying the storage device?
It's obvious that the storage device wants to serve that part of the DNS
namespace. If you don't want the clients to query the device directly
you could do it through a NAT, or proxy, or whatever. Anything other
than direct
nsupdate will use the MNAME regardless of whether it is matched by a
NS record. ISC dhcpd, as you indicated, does not unless overridden
manually via a zone statement.
-Tim
On Fri, Jan 18, 2013 at 9:35 AM, Chris Buxton cli...@buxtonfamily.us wrote:
On Jan 16, 2013, at 1:01 PM, Chuck Swiger
In message
cal_2sc1szstumpmfceuqrf87nqwe+5n30qvguds7q-4g6va...@mail.gmail.com, Daniele
writes:
These are the outputs. I also attach the file containing them.
; DiG 9.8.1-P1 ns . +norec +noedns @198.41.0.4
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status:
10 matches
Mail list logo
