Found this entry in external named log:
Mar 26 20:07:18 local@mercury named[4043]: [ID 873579 daemon.notice] client
72.13.58.93#39043: view outhouse: notify question section contains no SOA
This IP is not one of mine.
Does the word 'notify' related to zone transfers or something else.
Thanks
On 27/03/13 15:57, Manson, John wrote:
Found this entry in external named log:
Mar 26 20:07:18 local@mercury named[4043]: [ID 873579 daemon.notice]
client *72.13.58.93*#39043: view outhouse: notify question section
contains no SOA
This IP is not one of mine.
Does the word ‘notify’ related to
You wouldn't normally expect to see NOTIFY from clients, but maybe that
IP is (or thinks it is) a master for a zone you slave?
or it thinks it is an authoritative slave and hasn't been told with
notify master-only; to not send NOTIFY messages.
Several months ago, I reported that several of the make tests were failing due
to couldn't start server ns2 and the like.
Working with the BIND 9.9.2-P2 compile, I just spent several minutes tracking
the source of this down with some judicious use of print in the
'bin/tests/system/start.pl'
In the work around section of this notice, it talks about 'make clear' and
editing a file statement.
No problem with that.
Does 'make clear' affect the running named or is it best to stop named and
start it afterward?
Do I also need to run configure again or just make?
Will dig and rndc be
John,
You do not need to run the configure script again if you're compiling from the
same directory you have compiled from previously. Just edit the specified
file(s), then run
make clean
(and it is make clean, not make clear - this removes previously compiled
objects from your build
On Wed, 27 Mar 2013, Luther, Dan wrote:
For the tests, BIND starts up with an empty group descriptor:
I:issuing command '/home/luther/bind-9.9.2-P2/bin/named/named -m
record,size,mctx -T clienttest -c named.conf -d 99 -g named.run 21 echo
$!'
I guess you are talking about -g. It is
On Wed, 27 Mar 2013, Luther, Dan wrote:
Working with the BIND 9.9.2-P2 compile, I just spent several minutes
tracking the source of this down with some judicious use of ?print? in the
?bin/tests/system/start.pl? script and viewing the ?*.run? output. It really
comes down to file permissions
So it's not.
Dan Luther
Operations Engineer
Systems Operation Engineering
Level 3 Communications
One Technology Center, Tulsa OK 74103
p: 918-547-4370
e: dan.lut...@level3.com
-Original Message-
From: Jeremy C. Reed [mailto:jr...@isc.org]
Sent: Wednesday, March 27, 2013 3:17 PM
To:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.five-ten-sg.com/util/bind-9.9.2-0.3.P2.fc18.src.rpm
EL4:
rpmbuild --rebuild --define 'dist .el4' \
bind-9.9.2-0.3.P2.fc18.src.rpm
EL5:
rpmbuild --rebuild --define 'dist .el5' \
bind-9.9.2-0.3.P2.fc18.src.rpm
EL6:
On 3/26/2013 9:40 PM, Novosielski, Ryan wrote:
I have no idea how things work on Windows, but I doubt directory is optional.
- Original Message -
From: Joanne Homier [mailto:joanne.hom...@gmail.com]
Sent: Tuesday, March 26, 2013 11:30 PM
To:bind-users@lists.isc.org
BIND 9 is setup to be build and tested as a ordinary user.
You only need to be root to configure the test interfaces
and to do the final install.
On Linux named drops root's abilities to override file
permissions so when you extract the tarball as root you
12 matches
Mail list logo
