| |||||||||||||||||||||||||||||||
|
> ww* IN A 1D <IP address> > >What is the correct syntax for a ww* >wildcard. or is this just not possible? There are a few hosts that would >fit the ww* wildcard (ww2, etc) which we could put in as explicit A >records instead. That isn't a wildcard in the "defined sense" of "wildcard" per IETF documents. But what you want to do isn't impossible - although BIND can't do pattern matching in that way. (I don't know of any implementation that does feature that form of answer synthesis, but some implementers say they want to offer it.) The closest you can come to what you intend with BIND is via BIND's $GENERATE. # $GENERATE 0-9 ww$ A 127.0.0.1 will cause these records to appear # ww0.tld. 900 IN A 127.0.0.1 # ww1.tld. 900 IN A 127.0.0.1 # ww2.tld. 900 IN A 127.0.0.1 # ww3.tld. 900 IN A 127.0.0.1 # ww4.tld. 900 IN A 127.0.0.1 # ww5.tld. 900 IN A 127.0.0.1 # ww6.tld. 900 IN A 127.0.0.1 # ww7.tld. 900 IN A 127.0.0.1 # ww8.tld. 900 IN A 127.0.0.1 # ww9.tld. 900 IN A 127.0.0.1 -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Mail archives, backups. Sometimes I think the true beneficiaries of standards work are the suppliers of disk drives.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com