Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!news.sprintlink.net!news.indirect.com!wes From: wes@indirect.com (Barnacle Wes) Subject: Re: BIND drives me nuts Message-ID: <CyxK9v.KIz@indirect.com> Sender: usenet@indirect.com (System Operator) Organization: Internet Direct, indirect.com Date: Tue, 8 Nov 1994 03:56:17 GMT References: <Cyv8Bz.vL@luva.lb.bawue.de> X-Newsreader: TIN [version 1.2 PL2] Lines: 33 Michael Giegerich (migieger@luva.lb.bawue.de) wrote: : I have here on the local side a mini network composed of only two : systems: setha (BSDI-1.1) and luva (FreeBSD-1.1.5.1 & patches). : Both are connected to remote system nadia via sporadic slip con- : nections between luva and nadia. : local setha <=====ed0=====> local luva <-----sl0-----> remote nadia : Now the problem: if the slip connection isn't active (99 % of the : time) a simple `telnet setha' needs between 2..3 minutes to be : built because either the resolver or the nameserver are queried : endless times before the connaect is actually made, grrrrr. : Is there any workaround? (Please no answers like connect forever : to the world :-) No workarounds, but I do have a couple of simple solutions. You didn't state whether setha and luva are on the same 'network' as nadia. If setha and luva have their own IP network address, make luva the domain name server for your domain and run named there. Tell setha the default nameserver is luva. If setha and luva are on the same network as nadia (in terms of IP address), you can simply put caching nameservers on both setha and luva, and pre-load the caches with the addresses for setha and luva. Then, any time you query for the address of one of the 'local' machines, it will be in the local cache. Whichever approach you take, I *highly* recommend you obtain a copy of O'Reilly and Associates _TCP/IP Network Administration_. Wes Peters