Win95 machine not looking at 2nd and 3rd DNS
nobody
nobody at nowhere.com
Fri Mar 10 09:40:29 UTC 2000
Delmer
I specifically don't want the internal to work as a forwarder. We are
only allowing those users with "Internet Access", to have the ISP DSN's
in their setup, everyone else should not be able to see them.
This is a rather dumb way of stopping unauthorised users accessing the
internet, I know, but at present its the only method we have
Mark
Delmer Harris wrote:
>
> I think this has come up before and was determined to be a misunderstanding
> about the multiple resolvers in the local equivalent of resolv.conf. The
> correct behavior is as you described - if the resolver on W95 receives any
> response from DNS#1 it will _not_ go to DNS#2 or DNS#3. It is only when
> there is no response from DNS#1 that it will go to DNS#2.
>
> You could achieve what you appear to desire by configuring your internal
> DNS to use the ISP's DNS as 'forwarder' DNS machines. Then your internal
> DNS will check itself first, then ask the ISP's DNS to resolve what it
> can't resolve and return the answer to the W98 machines.
>
> YMMV
>
> nobody <nobody at nowhere.com> on 03/09/2000 11:36:19 AM
>
>
>
> To: comp-protocols-dns-bind at moderators.isc.org
>
> cc:
>
>
>
> Subject: Win95 machine not looking at 2nd and 3rd DNS
>
>
> Hi All
>
> I have a Win 95 machine which is set up to look at 3 DNS servers. The
> first is our internal, and the second and third are the ISP's. If I
> look for a web address, the machine will query only the internal then
> give up (checked this with a packet sniffer).
>
> The internal DNS is sat on a linux box and serves subdomains beneath our
> internet registered domain (ie. registed domain foo.com, this box does
> london.foo.com and paris.foo.com). The machine has no zone for root
> ".".
>
> However, other machines I have seem to work fine (a linux box (not the
> name server), and an NT box. I'v done a quick test and it seems I have
> the same problem with another win95 machine as well.
>
> Any ideas (i'm sure it was working before)
>
> Mark Taylor
More information about the bind-users
mailing list