[nsd-users] nsd zonefile format

Anand Buddhdev anandb at ripe.net
Tue Nov 9 15:10:47 UTC 2010


On 09/11/2010 14:02, Matthijs Mekking wrote:

Hi Matthijs,

> This is according to spec. RFC 1035 says that omitted class and TTL
> values are default to the last explicitly stated values. If you want the
> records after the MX to have a TTL of 1d, you should add explicitly say
> so; either by adding the line:
> 
> $TTL 1d
> 
> after the MX record, or by giving the TXT record an explicit TTL of 1d.

My copy of NSD 3.2.6 does not behave this way. Here's a zone snippet:

$TTL 1d
@		SOA     ns1.example.net admin.example.net. (
                                2010091501
                                3600
				1800
                                1209600
                                7200
                        )
		NS      ns1.example.com.
		NS      ns2.example.com.
	3600	MX	1 mail.example.com.
		TXT	"text"

results in:

$ dig +norec @localhost any example.net

; <<>> DiG 9.6.0-APPLE-P2 <<>> +norec @localhost any example.net
; (3 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19946
;; flags: qr aa; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;example.net.			IN	ANY

;; ANSWER SECTION:
example.net.		86400	IN	SOA	ns1.example.net.example.net.
admin.example.net. 2010091501 3600 1800 1209600 7200
example.net.		86400	IN	NS	ns1.example.com.
example.net.		86400	IN	NS	ns2.example.com.
example.net.		3600	IN	MX	1 mail.example.com.
example.net.		86400	IN	TXT	"text"



More information about the nsd-users mailing list