Subject: | |
From: | |
Reply To: | |
Date: | Fri, 17 Mar 2000 10:17:56 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
James Hofmeister <[log in to unmask]> wrote:
>
> I could see where users would want to be able to configure this
> alternative:
>
> hosts: dns [UNAVAIL=continue NOTFOUND=continue TRYAGAIN=continue] &
> files [UNAVAIL=return NOTFOUND=return TRYAGAIN=return]
>
> 1. Look in DNS first
> a. If DNS does not respond goto 2) HOSTS.NET.SYS
> b. If DNS responds node not found goto 2) HOSTS.NET.SYS
> c. If DNS does not get a response the first time goto 1) try DNS once
more
> 2. Look in HOSTS.NET.SYS second
> a. If HOSTS.NET.SYS not available stop search
> b. If HOSTS.NET.SYS responds node not found stop search
> c. Do not try HOSTS.NET.SYS again
>
>
> and I see another possible alternative users would want to be able to
> configure:
>
> hosts: files [UNAVAIL=continue NOTFOUND=continue TRYAGAIN=return] &
> dns [UNAVAIL=return NOTFOUND=return TRYAGAIN=continue] &
>
> 1. Look in HOSTS.NET.SYS first
> a. If HOSTS.NET.SYS not available goto 2) DNS
> b. If HOSTS.NET.SYS responds node not found goto 2) DNS
> c. Do not try HOSTS.NET.SYS again
> 2. Look in DNS second
> a. If DNS does not respond stop search
> b. If DNS responds node not found stop search
> c. If DNS does not get a response the first time goto 2) try DNS once
more
>
>
Yes, yes, yes, yes. I would settle for the first option, but the second
method (as a configurable option of course) is exactly what is needed.
When can I have it? ;-)
Doug.
Doug Werth Beechglen Development Inc.
[log in to unmask] Cincinnati, Ohio
|
|
|