Notify not happening can someone help me out
Elijah Savage
esavage at digitalrage.org
Sat Oct 25 23:55:17 UTC 2003
I do not see how this is any different from what I posted before but
here it is. I am not saying this is a config issue but I do not see how
it is on a different box running 8.3.4 in a test lab this same config
file works great and I see the notify in /var/log/messages.
options {
directory "/etc/namedb";
version "Why are you asking?";
query-source address * port 53; };
acl "secondary" {
64.39.29.216/32;
};
};
// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the
Internet.
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
// Setting up secondaries is way easier and the rough picture for this
// is explained below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// into your /etc/resolv.conf so this server will be queried first.
// Also, make sure to enable it in /etc/rc.conf.
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone
"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT
" {
type master;
file "localhost-v6.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone where your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is the first bytes of the respective IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to setup a primary zone, better make sure you fully
// understand how DNS and BIND works, however. There are sometimes
// unobvious pitfalls. Setting up a secondary is comparably simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in
rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind:bind /etc/namedb/s
// chmod 750 /etc/namedb/s
zone "digitalrage.org" in {
type master;
file "/etc/namedb/db.digital.org";
notify yes;
allow-transfer { secondary; };
};
-----Original Message-----
From: marka at isc.org [mailto:marka at isc.org] On Behalf Of
Mark.Andrews at isc.org
Sent: Saturday, October 25, 2003 6:53 PM
To: Elijah Savage
Cc: bind-users at isc.org
Subject: Re: Notify not happening can someone help me out=20
> Ok it was a typo I am running the latest 8.4.1, and I am not sure it
is
> a config error because these config files worked on the older version,
> but I guess I should have still posted them.
>=20
> options {
> directory "/etc/namedb";
> version "Why are you asking?";
> query-source address * port 53; };
>=20
> acl "secondary" {
> {
> X.X.X.X/32;
> };
> };
>=20
> zone "myzone.com" in {
> type master;
> file "/etc/namedb/db.myzone.com";
> notify yes;
> allow-transfer { secondary; };
> };
Do you want help or not?
Next time please send the requested data and don't edit it.
I don't believe the zone is myzone.com. Also editing can
hide the errors.
Mark
=09
> -----Original Message-----
> From: marka at isc.org [mailto:marka at isc.org] On Behalf Of
> Mark.Andrews at isc.org
> Sent: Saturday, October 25, 2003 5:57 PM
> To: Elijah Savage
> Cc: bind-users at isc.org
> Subject: Re: Notify not happening can someone help me out=20
>=20
>=20
> > All,
> >=20
> > Bind has always worked great for me but I upgraded to 8.4.3 here
> > recently and noticed that the notify message is not showing up in
> > /var/log/messages I am running this on FreeBSD 4.8.
> >=20
> > If I make changes of course changing the serial then reloading bind
I
> > even tried stopping and starting bind the notify message never goes
> out,
> > what made me notice this was my secondary after changes would have
old
> > info and not transfer until the refresh period like it should. I
> thought
> > this all was built in to bind ver8 or higher but just in case I even
> > added
> > Notify yes;
> >=20
> > To my config file.
> >=20
> > Any help would be greatly appreciated
>=20
> Firstly. BIND 8.4.3 does NOT exist.
>=20
> Secondly this will be a configuration problem / resolution
> problem. If you don't post the configuration information
> (named.conf entries, zone files, IP addresses of servers)
> there is nothing anyone can do for you.
>=20
> Mark
> --
> Mark Andrews, Internet Software Consortium
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
>=20
>=20
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list