$INCLUDE

[Kevin Darcy]

You could theoretically use resolver sortlists for this. But they're evil, so
don't.

Why are your users typing in hostnames anyway? This is the age of
bookmarks/hyperlinks/portals/search-engines/agents/etc.; physically typing in a
hostname should be a rare event for a regular user...


- Kevin

Stephens, Bill wrote:

>         I'm hesitant to do that, because not all of my users would remember
> to typein something like us381s04.sub.bubba.pvt  as opposed to
> us381s04.bubba.pvt.  Right now they just type in us381s04 and it resolves
> for them.  This is probably a stupid question but is there a way for me to
> put the dynamic addresses in a sub zone ie. us381s04.dyn.buba.pvt, and have
> it resolv the address for the user who is at us380s03.bubba.pvt when they
> just enter us381s04?  My understanding is that they would have to enter the
> fqdn.
>
>         Thanks
>
>         Bill Stephens
>
>         Joseph S D Yao <jsdy at cospo.osis.gov>
>         04/24/2000 11:21 AM
>         To:     Bill Stephens/Frito-Lay/US at Frito-Lay
>         cc:     comp-protocols-dns-bind at moderators.isc.org@SMTP at Exchange
>         Subject:        Re: $INCLUDE
>
>         On Mon, Apr 24, 2000 at 08:42:30AM -0500, Stephens, Bill wrote:
>         > I have bind 8.2.2p5 setup on a redhat 6.2 server for testing.  I
> have a zone
>         > file that I'm trying to seperate static from dynamic entries.  I
> would like
>         > to keep the static entries in a seperate file, and just do an
> include for
>         > the file.  However, when the ixfr runs, it moves all the entries
> that are
>         > $INCLUDE(d) file are placed into the including (zone) file.  Below
> is a
>         > sample of my zone file.  How do I keep from having the Included
> entries
>         > dumped into the including file?
>         >
>         > Thanks,
>         >
>         > Bill Stephens
>
>         Put them in a separate zone.
>
>         --
>         Joe Yao                         jsdy at cospo.osis.gov - Joseph S. D.
> Yao
>         COSPO/OSIS Computer Support
> EMT-B
>
> -----------------------------------------------------------------------
>         This message is not an official statement of COSPO policies.