A/zone entry using wildcard.
Kevin Darcy
kcd at daimlerchrysler.com
Fri Sep 23 00:13:26 UTC 2005
$GENERATE 1-999 test${0,3,d} A 127.0.0.1
- Kevin
Fabiano Silos Reis wrote:
>Content-Type: text/plain;
> charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>It is a shame. I have a zone already created and inside this zone I
>Need to create A entries pointing to the same ip address.
>
>Example:
>
>test001 IN A 127.0.0.1
>test002 IN A 127.0.0.1
>test003 IN A 127.0.0.1
>...
>testN IN A 127.0.0.1
>
>N is a number between 001 and 999.
>
>Thank you!
>
>
>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf
>Of Kevin Darcy
>Sent: quinta-feira, 22 de setembro de 2005 20:35
>To: bind-users at isc.org
>Subject: Re: A/zone entry using wildcard.
>
>Fabiano Silos Reis wrote:
>
>
>
>>Content-Type: text/plain;
>> charset="us-ascii"
>>Content-Transfer-Encoding: 7bit
>>Hi list,
>>
>>I would like to know if it is possible to register a entry using wildcard
>>
>>
>in
>
>
>>named like:
>>
>>test* IN A 127.0.0.1
>>
>>In a way that when I execute 'nslookup test001.mydomain' I get the address
>>127.0.0.1.
>>
>>Other question is, can I register a zone entry using wildcard?
>>
>>Example:
>>
>>zone "test*.domain" {
>> type master;
>> file "zones/test.domain";
>>};
>>
>>
>>
>>
>No. Not possible in BIND. The DNS protocol defines a wildcard mechanism,
>but it only matches 1 or more whole labels.
>
>Of course, you could always just put 1 or more wildcard records into
>"domain" itself and not have any subzones. The wildcard would match the
>name "test001.domain" and anything else under "domain" that wasn't
>already explicitly defined.
>
>
>
>>If no for both questions, do someone know a patch to make named answer
>>
>>
>using
>
>
>>this wildcard?
>>
>>
>>
>I know of no such patch.
>
>
> - Kevin
>
>
>
>
>
>-- Binary/unsupported file stripped by Ecartis --
>-- Type: application/x-pkcs7-signature
>-- File: smime.p7s
>
>
>
>
>
>
>
>
More information about the bind-users
mailing list