bind-users Digest, Vol 1798, Issue 1

[Bob McDonald]

This sounds like a Microsoft IP stack where it can be configured to search
the parent domain after a domain failure.  (as opposed to domain suffix
search order).  An attempt to resolve everything for the client no matter
what the client types in.  This generates unnecessary traffic, IMHO.

Bob



----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 23 Mar 2014 14:09:16 -0400
> From: Alan Clegg <alan at clegg.com>
> To: bind-users at lists.isc.org
> Subject: Re: localhoast A record?
> Message-ID: <532F234C.7090700 at clegg.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On 3/21/14, 2:18 PM, Chris Thompson wrote:
>
> > But in the context of search lists an NXDOMAIN will just make the
> resolver
> > go on to try the next entry. So in the case of search lists automatically
> > generated from a "domain" entry, if localhost.astrology.cam.ac.ukdoesn't
> > exist, localhost.cam.ac.uk will be tried, and then localhost.ac.uk ...
>
> I'm trying wrap my head around this "automatically generated" search
> list that runs outside your domain idea.
>
> Under what circumstances would this ever be a good idea?
>
> AlanC
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 600 bytes
> Desc: OpenPGP digital signature
> URL: <
> https://lists.isc.org/pipermail/bind-users/attachments/20140323/a5a73d31/attachment-0001.bin
> >
>
> ------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20140324/61c9fa87/attachment.html>