NOTIFY Probs on Bind8.22 on NT
McNair, Dan
DMcNair at dgexchange.dg.com
Wed Aug 30 20:20:15 UTC 2000
Yes, Kevin is correct. :-) BIND's default is to notify. Sorry for the misinformation.
--Dan
(Sorry, Kevin. Meant to send this to the list before.)
-----Original Message-----
From: Kevin Darcy [mailto:kcd at daimlerchrysler.com]
Sent: Wednesday, August 30, 2000 2:24 PM
To: Comp-Protocols-Dns-Bind
Subject: Re: NOTIFY Probs on Bind8.22 on NT
The "notify yes" zone option would only be necessary if you had an explicit
"notify no" global option.
- Kevin
McNair, Dan wrote:
> Try adding "notify yes;" to your zone. (O'Reilly _DNS_and_BIND_ p.231)
>
> zone "mydomain.com" IN {
> type master;
> file "mydomain.com.dns";
> notify yes;
> also notify { 192.168.224.11; };
>
> -----Original Message-----
> From: Richard Murphy [mailto:richard at bgfl.org]
> Sent: Wednesday, August 30, 2000 7:00 AM
> To: Comp-Protocols-Dns-Bind
> Subject: NOTIFY Probs on Bind8.22 on NT
>
> Afternoon all
>
> I have a problem with notification on BIND2.2.2 runing on NT 4 (SP6a).
>
> Currently have 2 Internet Facing NS both running on above setup as Primary
> and secondary for mulitple zones yet when I update a zone and change the
> serial (date set) on the master notification fails to take place.
>
> Example zone from my primary named.conf looks like:
>
> zone "mydomain.com" IN {
> type master;
> file "mydomain.com.dns";
> also notify { 192.168.224.11; };
>
> Example conf from slave named.conf looks like:
>
> zone "mydomain.com" IN {
> type slave;
> file "mydomain.com.dns";
> masters { 192.168.224.10; };
>
> Where the zone file "mydomain.com.dns" SOA for the serial is configured as:
>
> @ IN SOA ns1.mydomain.com. hostmaster.mydomain.com. (
> 200008300 ; Serial
> 3600 ; Refresh after 3 Hours
> 3600 ; Retry after 1 Hour
> 604800 ; Expire after 1 Week
> 86400 ) ; Minimum TTL of 1 day
>
> The only answer has been to remove the zone file on my secondary Name Server
> and restart the service (ISC BIND) which will generate a new file from the
> updated master records but even this drastic action can fail as the new file
> on occasion will generate the records from its cache??
>
> Any ideas people, anyone experience problems before with Bind on NT and
> specifically notify requests.?? I could do with solving this as we are
> authoratative for 450 domains and administering these under either NT4 or
> 2000 (where notification works) will be a nightmare where as text based
> editing on Bind for 450 domains is a piece of, er, p1ss and somehting I want
> to keep.. Anyway who wants to have DNS records in the registry? ;)
>
> TIA
>
> Richard..
>
> *************************************************************
> This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity
> to whom they are addressed. If you have received this email
> in error please notify postmaster at bgfl.org
>
> The views expressed within this email are those of the
> individual, and not necessarily those of the organisation
> *************************************************************
More information about the bind-users
mailing list