Import of existing bind zone doesn't handle AAAA records

[bigwillystyle42]

Hi,

I'm trying to import an existing bind zone with AAAA records and I'm seeing two broken behaviors:

1. AAAA records after an A record are treated as duplicates of the A record
2. AAAA records before any A records are dropped

This zone file demonstrates both issues:

$TTL   86400
@       IN      SOA     ns1.example.com. root.example.com. (
      2013042516    ; Serial
      28800         ; Refresh
      7200      ; Retry
      1209600   ; Expire
      86400)        ; Negative Cache TTL
;
@       IN      NS        ns1.example.com.
@       IN      NS        ns2.example.com.
@       IN      NS        ns3.example.com.
@       IN      NS        ns4.example.com.
@   IN  AAAA        2600:3c03::f03c:91ff:fedf:ef4d
@   IN  A       96.126.105.17
@   IN  MX  10  mail.example.com.
@ IN A 1.2.3.4
blah    IN  AAAA        2600:3c03::f03c:91ff:fedf:ef4d

[WillyXJ]

I agree that the zone importer does not handle AAAA records very well. This will probably take more work than a simple bug fix so I've targeted it for v1.2.

[WillyXJ]

Changed merged in.