Changeset 1027 for branches

Timestamp:

02/06/26 10:21:06 (45 hours ago)

Author:

Kris Deugau

Message:

/branches/cname-collision

Add test group for updating a record to a valid-after CNAME
Add arguably redundant test checking for collision with nontimestamped record
See #72, #88

File:

• branches/cname-collision/t/cname.t (modified) (1 diff)

branches/cname-collision/t/cname.t

@@ -512 +512 @@
   }; # update to expiring CNAME
 
+  ## Update to valid-after CNAME
+  subtest 'CNAME update - valid after' => sub {
+    my @ltime = localtime(time + 86400 * 3);
+    $expirystamp = sprintf "%i-%i-%i %i:%i", $ltime[5] + 1900, ($ltime[4] + 1) % 12, $ltime[3], 15, $ltime[1];
+    $newval = 'target.example.com';
+    subtest 'collision with nonexpiring record' => sub {
+      $newname = 'validafter1a.expiry3.test';
+      ($code, $msg) = $dnsdb->updateRec('n', 'n', 100, 6, \$newname, \$rectype, \$newval, 900, undef, 'f', $expirystamp);
+      ok( $code eq 'FAIL', "updateRec() claimed failure" );
+      if ($code eq 'FAIL') {
+        ($rcount) = $dbh->selectrow_array("SELECT count(*) FROM records WHERE domain_id = 6 AND host = '$newname'");
+        ok( $rcount == 1, " ... [$rcount] yep, hostname only occurs once" );
+        like( $msg, qr/One or more non-CNAME records/, " ... returned matching error" );
+      }
+    };
+  }; # update to valid-after CNAME
+
 }; # record expiry/valid-after