In message 20100225123134.gb2...@fantomas.sk, Matus UHLAR - fantomas writes:
On 25.02.10 12:01, Matus UHLAR - fantomas wrote:
I see that hosts that are not allowed to recurse are often generating
check-named errors.
check-names it is.
I apparently too often use named so I do
Jonathan de Boyne Pollard wrote:
That's also nothing to do with DNSCurve. You weren't making a DNSCurve
query there. You were simply querying, with an ordinary DNS query, a
proxy DNS server that is under someone else's control and getting the
view of the DNS namespace that that someone else
Thanks Stephane!!! Adding ::1 in the ACL did the trick.
Linh Khuu
-Original Message-
From: Stephane Bortzmeyer [mailto:bortzme...@nic.fr]
Sent: Thursday, February 25, 2010 11:09 AM
To: Khuu, Linh MicroTech
Cc: 'bind-users@lists.isc.org'
Subject: Re: Question about dig command
On Thu,
Hi!
Sorry for the delay.
It was very useful for me. Thanks!
In our nameserver we do not apply the bogon filter to the bogus
addresses because it will change with time and we not know how update
them automatically.
My question is that if it is useful to blacklist the private address
Hi!
I am trying to rotate my named logfile with logrotate and I
configured it as I show:
#
# Logrotate fragment for bind.
#
/var/log/named.log {
daily
ifempty
compress
delaycompress
dateext
rotate 14
missingok
nocreate
}
H
i!
I am trying to rotate my named logfile with logrotate and I
configured it as I show:
#
# Logrotate fragment for bind.
#
/var/log/named.log {
daily
ifempty
compress
delaycompress
dateext
rotate 14
missingok
nocreate
}
Diosney Sarmiento Herrera wrote:
I am trying to rotate my named logfile with logrotate and I
configured it as I show:
[...]
This is much more a question for a list that discusses the logrotate
application than it is to bind-users. I would recommend, however, that
you look into the
On Fri, 26 Feb 2010, Diosney Sarmiento Herrera wrote:
H
i!
I am trying to rotate my named logfile with logrotate and I
configured it as I show:
#
# Logrotate fragment for bind.
#
/var/log/named.log {
daily
ifempty
compress
delaycompress
dateext
Hi Alan!
I think that you are right. Sorry for that :(
Thanks for the tip, but I want to save the logs using the syslog
facilities and with the date in the the log name. I looked into the
logging statement syntax and I think that the file and the syslog
options are mutually exclusive.
--
Diosney Sarmiento Herrera diosne...@gmail.com said:
In our nameserver we do not apply the bogon filter to the bogus
addresses because it will change with time and we not know how update
them automatically.
My question is that if it is useful to blacklist the private address
range(this
On Feb 26, 2010, at 9:54 AM, Diosney Sarmiento Herrera wrote:
Hi!
Sorry for the delay.
It was very useful for me. Thanks!
In our nameserver we do not apply the bogon filter to the bogus
addresses because it will change with time and we not know how update
them automatically.
My question
Hi, Bill!
Actually, we have the same point of view of the term Internet,
because I'm in the same situation than you: I'm in a private network
that is conected to Internet trough NAT. I just misused the term, I had
to have used the term public newtork and not Internet.
In my private network
As Mark explained, the server is marked as bad because it returned an
illegal response.
If *all* of the nameservers which would be used to answer a particular
query are marked as bad, then the query fails. This is as it should be.
The fact that you see some residue in the cache that _could_,
On 02/23/10 23:01, sasa sasa wrote:
Hello,
for a 192.168.199.64/26 in zone file to delegate to a customer;
should i put subnet number:
64/26 IN NS ns1.example.com.
64/26 IN NS ns2.example.com.
or host ranges:
64-126 IN NS ns1.example.com.
64-126 IN NS ns2.example.com.
.
.
14 matches
Mail list logo
