zone update to slave

[Jan-Piet Mens]

> $ORIGIN 184.16.172.in-addr.arpa.
> $TTL 14400	; 4 hours
> 105			PTR	GVC-E237-A01.wks-gvc.domain.com.
> 88			PTR	GVC-LIB-C07.wks-gvc.domain.com.
> 9			PTR	gvc-busdrivers.wks-gvc.domain.com.
> 90			PTR	nb-csiler.wks-gvc.domain.com.
> 98			PTR	GVC-RES-A05.wks-gvc.domain.com.
> 16.184.16.172.in-addr.arpa.	IN	PTR	off-hp4050.gvc.domain.com.
> 24.184.16.172.in-addr.arpa.	IN	PTR	str-r7500.gvc.domain.com.
> 22.184.16.172.in-addr.arpa.	IN	PTR	lib-hp4300.gvc.domain.com.
> 11.184.16.172.in-addr.arpa.	IN	PTR	res-hp4300.gvc.domain.com.
> 
> 
> It seems as if these types of records get transfered:
> 
> 9			PTR	gvc-busdrivers.wks-gvc.domain.com.
> 
> But these do not:
> 
> 24.184.16.172.in-addr.arpa.	IN	PTR	str-r7500.gvc.domain.com.

You should find a record called

24	IN	PTR	str-r7500.gvc.domain.com.

on the slave. Note that BIND stores that below the current value of
$ORIGIN so that's fine and dandy. Query your slave for the PTR to verify
[ dig -x @slaveIP 172.16.84.24 ]

> If I delete the journal file on the on the slave server up the serial
> number on the master I get the same results.  The first type of record
> is updated dynamically and the second type of record is added
> manually.

This sentence doesn't really make sense: updated dynamically vs added
manually? For the record, if you're using dynamic DNS updates to the
master, you should avoid editing the master zone file manually.

        -JP