Difference in SOA record between master and slave?

Richard Stevenson RichardS at adv.net.nz
Thu Feb 24 23:58:49 UTC 2000


Hi

I've discovered an interesting trick, which I am finding somewhat annoying. 
 I've set up a couple of nameservers to serve 64.20.202.in-addr.arpa, and 
I'd like to have that zone delegated to them.  Unfortunately, APNIC refuses 
to accept the delegation because the two servers give different answers to 
a query for the SOA record.  From the intended master, I get this (note the 
TTL on the SOA record):

> [richards at bones richards]$ dig @ns1.akl.adv.net.nz 64.20.202.in-addr.arpa in
> soa
> 
> ; <<>> DiG 8.2 <<>> @ns1.akl.adv.net.nz 64.20.202.in-addr.arpa in soa 
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;;
> QUERY SECTION: ;;      64.20.202.in-addr.arpa, type = SOA, class = IN
> 
> ;; ANSWER SECTION:
> 64.20.202.in-addr.arpa.  2D IN SOA  adv.net.nz. soa.adv.net.nz. (
>                                         2000021800      ; serial
>                                         4d4h            ; refresh
>                                         1H              ; retry
>                                         5w6d16h         ; expiry
>                                         4d4h )          ; minimum
> 
> 
> ;; AUTHORITY SECTION:
> 64.20.202.in-addr.arpa.  2D IN NS  ns1.akl.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns2.akl.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns1.wlg.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns2.wlg.adv.net.nz.
> 
> ;; ADDITIONAL SECTION:
> ns1.akl.adv.net.nz.     2D IN A         202.20.64.19
> ns2.akl.adv.net.nz.     2D IN A         202.20.64.18
> ns1.wlg.adv.net.nz.     1H IN A         202.49.144.2
> ns2.wlg.adv.net.nz.     1H IN A         202.49.144.3
> 
> ;; Total query time: 1 msec
> ;; FROM: bones.akl.adv.net.nz to SERVER: ns1.akl.adv.net.nz  202.20.64.19 ;;
> WHEN: Fri Feb 25 12:52:43 2000 ;; MSG SIZE  sent: 40  rcvd: 234


But I get this one from the slave (again, note the TTL of the SOA record):

> [richards at bones richards]$ dig @ns2.akl.adv.net.nz 64.20.202.in-addr.arpa in
> soa
> 
> ; <<>> DiG 8.2 <<>> @ns2.akl.adv.net.nz 64.20.202.in-addr.arpa in soa 
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;;
> QUERY SECTION: ;;      64.20.202.in-addr.arpa, type = SOA, class = IN
> 
> ;; ANSWER SECTION:
> 64.20.202.in-addr.arpa.  4d4h IN SOA  adv.net.nz. soa.adv.net.nz. (
>                                         2000021800      ; serial
>                                         4d4h            ; refresh
>                                         1H              ; retry
>                                         5w6d16h         ; expiry
>                                         4d4h )          ; minimum
> 
> 
> ;; AUTHORITY SECTION:
> 64.20.202.in-addr.arpa.  2D IN NS  ns1.akl.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns2.akl.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns1.wlg.adv.net.nz.
> 64.20.202.in-addr.arpa.  2D IN NS  ns2.wlg.adv.net.nz.
> 
> ;; ADDITIONAL SECTION:
> ns1.akl.adv.net.nz.     2D IN A         202.20.64.19
> ns2.akl.adv.net.nz.     2D IN A         202.20.64.18
> ns1.wlg.adv.net.nz.     1H IN A         202.49.144.2
> ns2.wlg.adv.net.nz.     1H IN A         202.49.144.3
> 
> ;; Total query time: 1 msec
> ;; FROM: bones.akl.adv.net.nz to SERVER: ns2.akl.adv.net.nz  202.20.64.18 ;;
> WHEN: Fri Feb 25 12:54:16 2000 ;; MSG SIZE  sent: 40  rcvd: 234


My initial thought was that the zone file wasn't being transferred 
correctly, but that's not the case (I've pasted in both files below - from 
the master and from the slave).  It looks as if ns1.akl.adv.net.nz is 
ignoring the TTL specified on the SOA record in favour of the minimum TTL 
in the SOA record itself.  Is this normal?

Regards

Richard


---------- Zone file from master ----------
$TTL 172800

@		IN	SOA	adv.net.nz. soa.adv.net.nz. (
				2000021800	; serial
				360000		; refresh
				3600		; retry
				3600000		; expire
				360000		; minimum
				)
		IN	NS	ns1.akl.adv.net.nz.
		IN	NS	ns2.akl.adv.net.nz.
		IN	NS	ns1.wlg.adv.net.nz.
		IN	NS	ns2.wlg.adv.net.nz.
10		IN	PTR	scottie.akl.adv.net.nz.
17		IN	PTR	scottie.akl.adv.net.nz.
18		IN	PTR	spock.akl.adv.net.nz.
19		IN	PTR	bones.akl.adv.net.nz.
20		IN	PTR	sulu.akl.adv.net.nz.
---------- End master zone file ----------

---------- Zone file from slave ----------
; BIND version named 8.2.2-P3 Thu Nov 11 00:04:50 EST 1999
; BIND version root at porky.devel.redhat.com:/usr/src/bs/BUILD/bind-8.2.2_P3/src/bin/named
; zone '64.20.202.in-addr.arpa'   first transfer
; from 202.20.64.17:53 (local 202.20.64.18) using AXFR at Mon Feb 21 10:06:25 2000
$ORIGIN 20.202.in-addr.arpa.
64	172800	IN	SOA	adv.net.nz. soa.adv.net.nz. (
		2000021800 360000 3600 3600000 360000 )
	172800	IN	NS	ns1.akl.adv.net.nz.
	172800	IN	NS	ns2.akl.adv.net.nz.
	172800	IN	NS	ns1.wlg.adv.net.nz.
	172800	IN	NS	ns2.wlg.adv.net.nz.
$ORIGIN 64.20.202.in-addr.arpa.
20	172800	IN	PTR	sulu.akl.adv.net.nz.
18	172800	IN	PTR	spock.akl.adv.net.nz.
10	172800	IN	PTR	scottie.akl.adv.net.nz.
19	172800	IN	PTR	bones.akl.adv.net.nz.
17	172800	IN	PTR	scottie.akl.adv.net.nz.
---------- End slave zone file ----------



More information about the bind-users mailing list