RE: Wildcards not supported in & records?
David Hubbard <[email protected]> Tue, 2 Nov 2010 13:54:05 -0400
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
From: Maciej =AFenczykowski [mailto:[email protected]]=20 >=20 > if you're going to delegata *, why not delegate one level higher and > not have to do that? Oh, can I do that? Just &3.2.1 and send the whole thing over to him? I was not clear on if that would work or not. David > On Tue, Nov 2, 2010 at 10:12, David Hubbard > <[email protected]> wrote: > > Was trying to delegate the first of several /24's worth > > of in-addr.arpa records to a customer's name servers, > > some of which are present on said /24 and some not, so > > I did the following (first three octets and the domain > > name changed obviously): > > > > &*.3.2.1.in-addr.arpa:1.2.3.4:ns1.customerdns.com:3600 > > &*.3.2.1.in-addr.arpa:3.4.5.32:ns2.customerdns.com:3600 > > &*.3.2.1.in-addr.arpa:3.4.5.31:ns1.customerdns.net:3600 > > &*.3.2.1.in-addr.arpa:1.2.3.254:ns2.customerdns.net:3600 > > > > Did not get successful ptr lookups after putting that in > > place, just get an SOA response from our dns showing our > > dns. =A0I changed the records to test just one IP: > > > > &50.3.2.1.in-addr.arpa:1.2.3.4:ns1.customerdns.com:3600 > > &50.3.2.1.in-addr.arpa:3.4.5.32:ns2.customerdns.com:3600 > > &50.3.2.1.in-addr.arpa:3.4.5.31:ns1.customerdns.net:3600 > > &50.3.2.1.in-addr.arpa:1.2.3.254:ns2.customerdns.net:3600 > > > > Now it's happy. =A0Querying for 50.3.2.1.in-addr.arpa on > > my tinydns gives back four NS authority records of the > > customer's DNS servers. =A0If I do a straight root lookup > > of that ptr I get proper traversal to customer's dns and > > a correct response. > > > > So, I can of course write a little script to generate > > the thousand or so lines of records I'll need, but was > > hoping I could get away with four like you can with A > > records? > > > > Thanks, > > > > David > > >=20 >=20