Changeset 357 for trunk

Timestamp:

07/05/12 17:50:16 (12 years ago)

Author:

Kris Deugau

Message:

/trunk

Checkpoint: timy-import.pl

• Fix handling of full tinydns '&' NS records; expand the hostname as per tinydns' automatic NS name, and add an A record for the NS name if an IP is present
• Fill in '@' MX records including MX hostname expansion and A record

File:

• trunk/tiny-import.pl (modified) (3 diffs)

trunk/tiny-import.pl

@@ -186 +186 @@
       $zone =~ s/^\&//;
       $zone =~ s/\.$//;
+      $ns =~ s/\.$//;
+      $ns = "$ns.ns.$fqdn" if $ns !~ /\./;
       $ttl = 0 if !$ttl;
       $stamp = '' if !$stamp;
@@ -206 +208 @@
         if ($fparent) {
           $recsth->execute($fparent, 0, $zone, 2, $ns, 0, 0, 0, $ttl);
+          $recsth->execute($fparent, 0, $ns, 2, $ip, 0, 0, 0, $ttl) if $ip;
         } else {
           push @deferred, $rec unless $nodefer;
@@ -268 +271 @@
     } elsif ($rec =~ /^\@/) {
       $cnt{MX}++;
+
+      my ($zone,$ip,$host,$dist,$ttl,$stamp,$loc) = split /:/, $rec, 7;
+      $zone =~ s/^\.//;
+      $zone =~ s/\.$//;
+      $host =~ s/\.$//;
+      $host = "$host.mx.$zone" if $host !~ /\./;
+      $ttl = 0 if !$ttl;
+      $stamp = '' if !$stamp;
+      $loc = '' if !$loc;
+      $loc = '' if $loc =~ /^:+$/;
+
+# note we don't check for reverse domains here, because MX records don't make any sense in reverse zones.
+# if this really ever becomes an issue for someone it can be expanded to handle those weirdos
+
+      # allow for subzone MXes, since it's perfectly legitimate to simply stuff it all in a single parent zone
+      my $domid = DNSDB::_hostparent($dbh, $zone);
+      if ($domid) {
+        $recsth->execute($domid, 0, $zone, 15, $host, $dist, 0, 0, $ttl);
+        $recsth->execute($domid, 0, $host, 1, $ip, 0, 0, 0, $ttl) if $ip;
+      } else {
+        push @deferred, $rec unless $nodefer;
+      }
 
     } elsif ($rec =~ /^'/) {