lermit/puppet-bind — pull request #3 by dvestal (2012-10-16 15:52:32+00:00)
Title: Set a default order for ns records

After being able to get back to work on the manifests for the dns machine I came across a situation where the ns records were being placed in the middle of the other records instead of at the top.

```
; File managed by puppet

$TTL 300
@ IN SOA ns1 root.example.com (
1 ; serial
300 ; refresh
300 ; retry
300 ; expire
604800 ; TTL
);
api IN A 123.45.67.89
mail IN A 231.54.76.98
IN NS ns1
ns1 IN A 10.20.30.40
stage IN A 123.54.76.98
```

My fix for this builds on my previous change to add the ordering capability for wildcard records. I just set a default ordering of 0 on ns records to override the default of 10 for other records. This allows all ns records to be defined at the top instead of in alphabetical order with the rest of the records.

```
; File managed by puppet

$TTL 300
@ IN SOA ns1 root.example.com (
1 ; serial
300 ; refresh
300 ; retry
300 ; expire
604800 ; TTL
);
IN NS ns1
api IN A 123.45.67.89
mail IN A 231.54.76.98
ns1 IN A 10.20.30.40
stage IN A 123.54.76.98
```