Changeset 833 for trunk

Timestamp:

04/19/22 13:55:07 (3 years ago)

Author:

Kris Deugau

Message:

/trunk

Handle an edge case with SRV records - target host of "." explicitly
specifies "this service does not exist"

File:

• trunk/DNSDB.pm (modified) (3 diffs)

trunk/DNSDB.pm

@@ -3 +3 @@
 ##
 # $Id$
-# Copyright 2008-2021 Kris Deugau <kdeugau@deepnet.cx>
+# Copyright 2008-2022 Kris Deugau <kdeugau@deepnet.cx>
 # 
 #    This program is free software: you can redistribute it and/or modify
@@ -1083 +1083 @@
 
     # SRV target check - IP addresses not allowed.  Must be a more or less well-formed hostname.
+    # Allow a bare . to indicate "this service does not exist"
     return ('FAIL', "SRV records cannot point directly to an IP address")
-      if ${$args{val}} =~ /^(?:[\d.]+|[0-9a-fA-F:]+)$/;
+      if ${$args{val}} ne '.' && ${$args{val}} =~ /^(?:[\d.]+|[0-9a-fA-F:]+)$/;
   } else {
     # hm.  we can't do anything sane with IP values here;  part of the record data is in
@@ -1098 +1099 @@
 
     # SRV target check - IP addresses not allowed.  Must be a more or less well-formed hostname.
+    # Allow a bare . to indicate "this service does not exist"
     return ('FAIL', "SRV records cannot point directly to an IP address")
-      if ${$args{host}} =~ /^(?:[\d.]+|[0-9a-fA-F:]+)$/;
+      if ${$args{host}} ne '.' && ${$args{host}} =~ /^(?:[\d.]+|[0-9a-fA-F:]+)$/;
 
     # SRV records in reverse zones get stricter treatment.  The UI bars adding them in