In article <mailman.797.1337090936.63724.bind-us...@lists.isc.org>, Alexander Gurvitz <a...@net-me.net> wrote:
> You should NOT get A records. Wildcard works only for hostnames > that have NO records of ANY type. Excuse me while I delirk, but this is interesting. Is a name on the RHS of an RR regarded as existing enough to prevent wildcard lookup? In this I would have expected the NS lookup to be followed by an A lookup for abc.a.example.com which would match the wildcard, assuming no other records match that name on the LHS. Sam > >From wikipedia: > To quote RFC 1912, "A common mistake is thinking that a wildcard > MX for a zone will apply to all hosts in the zone. A wildcard MX will > apply only to names in the zone which aren't listed in the DNS at all. > " That is, if there is a wild card MX for *.example.com, and an > A record (but no MX record) for www.example.com, the correct > response (as per RFC 1034) to an MX request for www.example.com > is "no error, but no data"; this is in contrast to the possibly expected > response of the MX record attached to *.example.com. > > Regards, > Alexander, > net-me.net > > On Tue, May 15, 2012 at 9:34 AM, rams <brames...@gmail.com> wrote: > > Hi, > > I have NS record points a record [A/AAAA] which is falls into wildcard . But > > when I query for NS record against bind, we are not getting these records as > > glue records. > > > > ex: > > *.a.example.com A 1.1.1.1 > > example.com. NS abc.a.example.com. > > > > Querying example.com with any or ns. > > don't we get glue records for this scenario? please confirm. -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users