Felipe Gasper wrote:
>
> Is there any public code interface that exposes named-checkzone’s
> functionality?
> I’d specifically like to have numeric error codes rather than strings.
It isn't easy to do that, I'm afraid.
There are two places that don't do what you want. The sour
Hello,
Is there any public code interface that exposes named-checkzone’s
functionality?
I’d specifically like to have numeric error codes rather than strings.
Thank you!
-FG
___
Please visit
a
named-checkzone on any of the ones compiled straight from isc's source,
after every RRSIG line, we see a ; resign line that contains the date/time
of that resign. When we issue the same command on RedHat's default, we get
all of the same information, minus that line. I was wondering if anyone
could
Ok that was my misunderstanding of named-checkzone. I though I had to check
for all $ORIGINs.
I haven't played with IPv6 yet. I hope I'll have a chance to do it
eventually.
Thanks for your time guys!
On Mon, Jun 5, 2017 at 9:49 AM, Mark Elkins <m...@posix.co.za> wrote:
> Most
Most certainly - Yes.
You have a single zone here, thus only:
named-checkzone example.com <http://example.com> example.com.zone
...should work.
Wait till you play with a reverse IPv6 zone - where I personally use
many $ORIGIN statements - saves hours of typing and makes reading the
Bernard Fay <bernard@gmail.com> wrote:
>
> should I understand while using named-checkzone I need to enter *only*
> the top domain and named-checkzone will understand the subdomains
> defined by the multiple $ORIGIN in the zone file?
Yes, named-checkzone basically just l
I understand what $ORIGIN is doing by reducing the typing and making it
easier to maintain the zone files.
To Tony, should I understand while using named-checkzone I need to enter
*only* the top domain and named-checkzone will understand the subdomains
defined by the multiple $ORIGIN in the zone
le.com
> ...
> $ORIGIN sub1.example.com
> ...
> $ORIGIN sub2.example.com
> ...
> $ORIGIN sub3.example.com
> ...
>
>
> While checking the zone file with:
> named-checkzone example.com example.com.zone
> named-checkzone returns ok for the first $ORIGIN.
>
> But doing
(This feature is useful for empty zones,
for example, but it's usually not a good idea for normal zones.) The zone
name is used to set the default $ORIGIN and for the zone sanity checks.
So, this works...
> While checking the zone file with:
> named-checkzone example.com example.com.zo
ORIGIN sub3.example.com <http://sub3.example.com>
...
While checking the zone file with:
named-checkzone example.com <http://example.com> example.com.zone
named-checkzone returns ok for the first $ORIGIN.
But doing
named-checkzone sub1.example.com <http://example.com> example.
Sorry keyboard problem...
I took control of a DNS based on Bind 9.9. One of the zone files have
multiple $ORIGIN for example:
$ORIGIN example.com
...
$ORIGIN sub1.example.com
...
$ORIGIN sub2.example.com
...
$ORIGIN sub3.example.com
...
While checking the zone file with:
named-checkzone
Hi,
I took control of a DNS based on Bind 9.9. One of the zone files have
multiple $ORIGIN for example:
$ORIGIN example.com
...
$ORIGIN sub1.example.com
...
$ORIGIN sub2.example.com
...
$ORIGIN sub3.example.com
...
While checking the zone file with:
named-checkzone example.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/04/2014 11:54 PM, Mark Andrews wrote:
In message 545954b0.8080...@offerman.com, Adrian (Aad) Offerman
writes:
named keeps refusing my zone file in which I included a DANE
record:
[root]# named-checkzone offerman.com db.offerman.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
named keeps refusing my zone file in which I included a DANE record:
[root]# named-checkzone offerman.com db.offerman.com
db.offerman.com:59: _443._tcp.offerman.com: bad owner name (check-names)
db.offerman.com:60: _443._tcp.offerman.com: bad owner
In message 545954b0.8080...@offerman.com, Adrian (Aad) Offerman writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
named keeps refusing my zone file in which I included a DANE record:
[root]# named-checkzone offerman.com db.offerman.com
db.offerman.com:59: _443._tcp.offerman.com
root@ns0s:~ # named-checkzone
usage: named-checkzone [-djqvD] [-c class] [-f inputformat] [-F outputformat]
[-t directory] [-w directory] [-k (ignore|warn|fail)] [-n (ignore|warn|fail)]
[-m (ignore|warn|fail)] [-r (ignore|warn|fail)] [-i
(full|full-sibling|local|local-sibling|none)] [-M (ignore
Hi,
Running BIND 9.7.0-P2-RedHat-9.7.0-5.P2.el6
New setup/install and attempting to setup DNSSEC and clean any dirty data.
Got the zone signed and ran named-checkzone against it and got the following
(11) times:
addnode: NSEC node already exists
The .signed loads but want to have clean
the man page for named-checkzone and it
looks like one might be able to cause it to test load the zone
as if one was starting bind which means it has to read the
named.conf file. If I could see what path it thinks it is
loading from, the fix would be easy.
Can it do that? I am not quite sure
to a member of this list for helping me better use the
available tools.
I had been using named-checkzone and named-checkconf for
years to check syntax but these do so much more. Many thanks to
the ISC community for designing such good applications.
Martin McCormick
, October 13, 2010 4:54 PM
To: bind-us...@isc.org
Subject: Re: named-checkzone Test Runs
I wrote:
I am testing bind9.7 and seem to not be correctly defining the
path to the localhost forward and reverse zones which are in
/var/named/etc/namedb/master. After the chroot, they should be
found
A list member wrote:
named-checkzone doesn't need to read the named.conf file - it just makes
sure that the zone is correct. if you want to check named.conf, you will
need to use named-checkconf
For checking config, try
named-checkconf -t [chroot directory] [relative path to named.conf
For the sake of thoroughness, the -j flag causes
named-compilezone to also look at the .jnl files so that the
zone you getis as up to date as possible.
Martin
___
bind-users mailing list
bind-users@lists.isc.org
On Thu, Jun 24, 2010 at 04:37:45PM -0400, Paul Amaral wrote:
I was thinking more instantaneous without moving things around. I looked at
vim vimrc autocmd but I couldn't get named-checkzone to execute and I would
still have to somehow have named-checkzone look at the last zone
On Thu, Jun 24, 2010 at 03:46:37PM -0400, P.A wrote:
Hi, im trying to get some ideas how I can exec named-checkzone on a zone
file that has just been executed. We have com users who edit zone files but
forget to run the command when they are do editing the file. Trying to
figure out if anyone
Hi, im trying to get some ideas how I can exec named-checkzone on a zone
file that has just been executed. We have com users who edit zone files but
forget to run the command when they are do editing the file. Trying to
figure out if anyone has a good way of enforcing that the zone gets checked
My suggestion is to create a backup copy of the (current) zone files in
another directory. Only allow the users to edit those files, then
execute a shell script that checks them, and only moves them to the
production directory once the named-checkzone (and named-checkconf)
works correctly
I was thinking more instantaneous without moving things around. I looked at vim
vimrc autocmd but I couldn’t get named-checkzone to execute and I would still
have to somehow have named-checkzone look at the last zone that was edited.
Good suggestion though.
From: Taylor, Gord
I was thinking more instantaneous without moving things around. I looked at vim
vimrc autocmd but I couldn’t get named-checkzone to execute and I would still
have to somehow have named-checkzone look at the last zone that was edited.
Good suggestion though.
From: Taylor, Gord
If you wanted to throw CVS into the mix, it would make all this pretty easy.
You can have it run scripts on checkin, and you know all the files changed from
a cvs diff, so it’s easy to run that through the named-checkzone.
CVS doesn’t have to make things much more complicated. You could
I have downloaded 9.7.0-P1 and I am running into something odd with
named-checkzone
I have a simple zone with an NS record that has no A or record.
named-checkzone has flags to ignore this. and this same command (see below)
worked in 9.6
but given this zone file
test.net. 500 IN SOA d88
Correction:
I am calling named-checkzone not checkconf.
this:
named-checkconf -k ignore -n ignore -i none test.net. zonefile
should read
named-checkzone -k ignore -n ignore -i none test.net. zonefile
the rest of the email is correct
From: Jack Tavares
Sent: Monday, May 10, 2010 12:49 PM
would cause the zone
to fail the above checks if
committed. [RT #20678]
From: Jack Tavares
Sent: Monday, May 10, 2010 12:54 PM
To: Jack Tavares; bind-users@lists.isc.org
Subject: RE: named-checkzone behavior change?
Correction:
I am calling named
32 matches
Mail list logo
