In addition to my pvt email Evan
The dev link page still shows 9.7.3 as current production, no 9.8.0, but
going to all downloads shows 9.8.0 as current production, and as things
happen in three's ...
bind-9.8.0.tar.gz clicking on this yields a file called
bind-980targzno
I got my logging setup but named-checkconf is spitting out an error.
$named-checkconf /home/nate/named.conf.local
/home/nate/named.conf.local:11: missing ';' before '3'
/home/nate/named.conf.local:11: unknown option '3'
I'm pretty sure we don't put an ; after version. I can't see anything
wrong
Change:
file /var/log/query.log version; 3 size 5m;
to:
file /var/log/query.log versions 3 size 5m;
-Original Message-
From: bind-users-bounces+tsnyder=rim@lists.isc.org
[mailto:bind-users-bounces+tsnyder=rim@lists.isc.org] On Behalf Of Nate
Homier
Sent: Thursday, March 03,
On Mar 3, 2011, at 3:30 PM, Nate Homier wrote:
I got my logging setup but named-checkconf is spitting out an error.
$named-checkconf /home/nate/named.conf.local
/home/nate/named.conf.local:11: missing ';' before '3'
/home/nate/named.conf.local:11: unknown option '3'
I'm pretty sure we don't
Dnia 2011-03-03 13:30 Nate Homier napisał(a):
I got my logging setup but named-checkconf is spitting out an error.
$named-checkconf /home/nate/named.conf.local
/home/nate/named.conf.local:11: missing ';' before '3'
/home/nate/named.conf.local:11: unknown option '3'
I'm pretty sure we don't put
On Thu, 2011-03-03 at 21:56 +0100, Torinthiel wrote:
Dnia 2011-03-03 13:30 Nate Homier napisał(a):
I got my logging setup but named-checkconf is spitting out an error.
$named-checkconf /home/nate/named.conf.local
/home/nate/named.conf.local:11: missing ';' before '3'
It should work too, it was fixed within in a few minutes :)
On Thu, 2011-03-03 at 04:47 -0500, Dennis Clarke wrote:
In addition to my pvt email Evan
The dev link page still shows 9.7.3 as current production, no 9.8.0, but
going to all downloads shows 9.8.0 as current production, and
When doing a recursive query for MX supernet.com against a caching BIND
server, the BIND server responds back with the answer. The TTL is 300.
After the TTL expires the following recursive query for the same record
returns a SERVFAIL from the caching server.
If I do a +trace on the same query
Forgot to additionally add that the only thing that showed up in the
logs was the query log entry, nothing else pertaining the below query. I
also checked with tcpdump on the caching server that it was not sending
any queries towards the Earthlink IP addresses which makes sense given
that the
It's because the NS RRSet returned by the authoritative name servers lists
servers that are not authoritative. Classic DNS mistake.
The com zone says that the authoritative servers for supernet.com are
ns{2,3}.earthlink.net (delegation).
But supernet.com as hosted on ns{2,3}.earthlink.net says
10 matches
Mail list logo