[nsd-users] nsd as master + slave

[A. Schulze]

hello,

I configured nsd-4.1.0 as master + slave. communication is forced via ipv6.

@master
zone:
  name: "example.org."
  zonefile: "/path/to/zonefile"
  outgoing-interface: 2001:0db8::1:1
  notify-retry: 5
  notify: 2001:0db8::2:1 NOKEY
  provide-xfr: 2001:0db8::2:1 NOKEY

@slave
zone:
  name: "example.org."
  allow-notify: 2001:0db8::1:1 NOKEY
  request-xfr: 2001:0db8::1:1 NOKEY

As the slave has not "zonefile" statement I could remove nsd.db and  
restart nsd to
force the slave fetch data from master. that works.
I could also build a newer zone on the master and run "nsd-control  
transfer" at the slave.
that work too.

But I would expect that a "nsd-control notify" at the master trigger a  
packet from master to slave
to inform the slave about the current serial. I do not see any logging  
nor any packets transferred.

Q1: how do I notify a slave about a new serial to force a update  
initiated by the slave?

For testing purposes I shortened the refresh and retry parameters in  
example.org SOA record.
( refresh 120s, retry 60s )

Now the slave initiate a tcp connection every 120s and trigger this  
logging at the master:
[2014-10-09 22:57:18.247] nsd[25239]: error: failed reading from  
2001:db8::2:1 tcp: Connection reset by peer
[2014-10-09 22:59:11.215] nsd[25239]: error: failed reading from  
2001:db8::2:1 tcp: Connection reset by peer
[2014-10-09 23:01:00.909] nsd[25239]: error: failed reading from  
2001:db8::2:1 tcp: Connection reset by peer
[2014-10-09 23:02:57.600] nsd[25239]: error: failed reading from  
2001:db8::2:1 tcp: Connection reset by peer
[2014-10-09 23:04:53.284] nsd[25239]: error: failed reading from  
2001:db8::2:1 tcp: Connection reset by peer

I did a tcpdump and saw that (at least a significant part of) the zone  
is transferred via tcp.
Finally the slave sent tcp reset packets. I could provide dumps.

Q2: Do I something completely wrong?

Thanks,
Andreas