Stealth dns and SOA record

[Nicholas Lee]

"Jim Reid" <jim at rfc1035.com> wrote in message
news:5855.949610466 at gromit.rfc1035.com...

> No. The master server will by default sent NOTIFYs to the NS records
> in the newly-loaded zone. All that matters is that the SOA record's
> MNAME field is syntactically valid. An old version - 8.1? - of BIND
> exhibited the behaviour you describe if the MNAME in the SOA record
> didn't point at the master server, but that code is history now. The
> only requirement to list the master name server in the SOA MNAME is if
> dynamic DNS is used. It's the only way of reliably identifying the
> master server and dynamic DNS clients need to know this.

That is the behaviour I think I'm seeing with (openbsd) 8.2.2P6.  When I
changed SOA primary ns record from the published primary to the unpublished
one, the logs indicated that:

Feb  3 23:10:51 water named[9020]: master zone "kiwa.co.nz" (IN) loaded
(serial 2000020311)
Feb  3 23:10:51 water named[9020]: Forwarding source address is
[0.0.0.0].10751
Feb  3 23:10:51 water named[9020]: Ready to answer queries.
Feb  3 23:11:16 water named[9020]: Sent NOTIFY for "kiwa.co.nz IN SOA"
(kiwa.co.nz); 1 NS, 1 A
Feb  3 23:11:53 water named[9020]: reloading nameserver
Feb  3 23:11:53 water named[9020]: Zone "kiwa.co.nz" (file master/db.kiwa):
No default TTL set using
 SOA minimum instead
Feb  3 23:11:53 water named[9020]: master zone "kiwa.co.nz" (IN) loaded
(serial 2000020312)
Feb  3 23:11:53 water named[9020]: Forwarding source address is
[0.0.0.0].27186
Feb  3 23:11:53 water named[9020]: Ready to answer queries.
Feb  3 23:12:18 water named[9020]: Sent NOTIFY for "kiwa.co.nz IN SOA"
(kiwa.co.nz); 2 NS, 2 A
Feb  3 23:12:18 water named[9020]: Received NOTIFY answer from 203.96.152.4
for "kiwa.co.nz IN SOA"

Where  2000020311 had the 203.96.152.4  nameserver as primary and 2000020312
had water as primary in the SOA record.



Nicholas