At 07:08 15-05-2012, Alexander Gurvitz wrote:
From wikipedia:
To quote RFC 1912, "A common mistake is thinking that a wildcard
Using Wikipedia to quote RFC 1912 is odd ...
Regards,
-sm
___
Please visit https://lists.isc.org/mailman/listinfo/bind-u
Sam Wilson wrote:
>
> Not I - another poster.
Sorry!
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Forties, Cromarty, Forth, Tyne, Dogger: Northwest 5 to 7, occasionally 4 in
Forth and Tyne. Moderate or rough, occasionally very rough in Forties and
Dogger. Showers. Good, occasionally moderate.
In article ,
Tony Finch wrote:
> Sam Wilson wrote:
> >
> > Is a name on the RHS of an RR regarded as existing enough to prevent
> > wildcard lookup?
>
> No, only RR owner names.
>
> > In this I would have expected the NS lookup to be followed by an A
> > lookup for abc.a.example.com which wou
Sam Wilson wrote:
>
> Is a name on the RHS of an RR regarded as existing enough to prevent
> wildcard lookup?
No, only RR owner names.
> 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 m
In article ,
Alexander Gurvitz 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 woul
You should NOT get A records. Wildcard works only for hostnames
that have NO records of ANY type.
>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 l
Hi,
I have NS record points a record [A/] 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 recor
7 matches
Mail list logo
