Nameresolving problems with bind9??
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Wed Dec 5 23:02:54 UTC 2001
How long does it take your ISDN router to bring up the link and
for it to be operational?
My link takes < 4 seconds.
Mark
>
> Hi,
>
> ISDN is configured for autodial and a nameserver in my lan is set up.
>
> Trying e. g. fetchnews -v or lynx www.t-online.de or any other adresses
> from out of the gateway's bash or xterm, nameresolving fails for the first
> time and succeeds for the following times.
>
> In a sequence of two or more commands, the first one just causes the dialin
> without nameresolving, the following ones produce a correct nameresolving.
> A first query from my domain clients is sometimes successful and sometimes
> not.
>
> Inspite of this a query from the gateway itself, using the konquerer or
> netscape e.g. by clicking a web adress offline, always causes a dialin and
> a successfull DNS query after a few seconds.
>
> I thought, a DNS nameresolving works for ever, no matter if it answers the
> first query, or a following one?
>
> There is no difference whether I choose 127.0.0.1 or the gateway's ethernet
> ip as a cashing only nameserver and the T-Online's nameserver as a
> forwarder adress or whether I choose T-Online's nameserver directly.
> Does anybody have the same problems, or what could be the reason for this
> stupid and different behaviour?
>
>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list