> Sorry, no.
> You can on the other hand probably create a separate internal domain
> for each subnet and mask on this name...
From my perspective, it's not good to force someone to use DNS to
establish better security to a server. The key is, on most systems using
TCP/IP, it is possible to set up controls at the bitmask level. In your
solution, if a DNS server went down, the database would choke. That would
be bad, and in some cases, not uncommon.
If mySQL doesn't implement such a feature, then it will not be flexible
enough for all networks, and it will not be "complete" as far as TCP/IP is
concerned. Considering it's only a few lines of code to implement (since
slashes are not valid in domain names, so are available for ip addrs), I'd
strongly recommend adding it to the product.
Justin Yunke + yunke@stripped
PC/Unix Network Administrator + http://www.productivity.org/
Database and Windows Software Design + http://www.dbasecentral.com/