<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Michael,<br>
<br>
Regular expressions to match host names are not easy. This page
offers some suggestions:
<a class="moz-txt-link-freetext" href="http://stackoverflow.com/questions/106179/regular-expression-to-match-hostname-or-ip-address">http://stackoverflow.com/questions/106179/regular-expression-to-match-hostname-or-ip-address</a><br>
<br>
I'd split the list into individual names and validate each
separately so you tell the user which one is malformed.<br>
<br>
Good luck!<br>
<br>
Eric<br>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title></title>
<br>
</div>
On 4/23/14 7:33 PM, Michael Stauber wrote:<br>
</div>
<blockquote cite="mid:53585BF1.9050102@blueonyx.it" type="cite">
<pre wrap="">Hi Michael,
</pre>
<blockquote type="cite">
<pre wrap="">Why not leave all the input fields the way they are and simply add a
checkbox where appropriate that says something like "Accept Wildcard DNS
requests" and "Accept Wildcard Web Server requests".
Then you never have to actually store the asterisk in the database, just
look for the flag and have the output correct when the underlying OS files
are written.
</pre>
</blockquote>
<pre wrap="">
Sounds like a good idea, but due to the way CODB works, I have to do it
the hard way: Create input verification schemas for hostname and FQDN
with wildcards. Then use these in the few fields that actually can use
wildcards. I just wrapped that up for DNS and there are some DNS record
types which don't like wildcards.
Now it's just messing with "web server alias" and I'm just banging my
head on the table with one particular complicated regular expression for
a field that takes multiple domain names - optionally separated by
either line wraps or comas.
</pre>
</blockquote>
<br>
</body>
</html>