Date: Thu, 07 Aug 97 21:39:30 -0800 From: "Studded" <Studded@dal.net> To: "David Kelly" <david@samara.co.zw> Cc: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Re: DNS Message-ID: <199708080440.VAA11864@mail.san.rr.com>
next in thread | raw e-mail | index | archive | help
On Fri, 8 Aug 1997 09:44:19 +0930 (CST), Greg Lehey wrote: >David Kelly writes: >> Hi, >> >> We're an ISP using FreeBSD 2.1.7.1 on our servers. We have a problem with >> our DNS. Our domain is SAMARA.CO.ZW When doing an nslookup for anything >> within that domain (e.g. mail.samara.co.zw) it appears that the lookup is >> done outside our network. If we disconnect our link to our upstream >> provider, we can't look up anything inside our network. [snip] >> Any ideas on the source of the problem? The /etc/resolv.conf file contains: >> >> domain samara.co.zw >> nameserver 196.2.64.1 <- samara.co.zw = 196.2.64.1 >> nameserver 147.28.0.34 >> nameserver 204.59.144.222 >> nameserver 204.117.214.10 > >This is a funny-looking resolv.conf. You're running a local name >server, but three of the addresses appear to be pointing to different >continents. It shouldn't cause timeouts, but it won't cause blinding >speed either. The domain keyword shouldn't be necessary, but there isn't anything wrong with specifying backup name servers "just in case." First off though, 'man resolv.conf' will tell you that you are only allowed 3 nameserver keywords. Secondly, if you are going to specify the local machine as a resolver, you should use 127.0.0.1 as the address, and make sure you have a primary/master db file for the 0.0.127.in-addr.arpa domain (this is usually localhost.rev). There is a script in /etc/namedb called make-localhost that'll do this for you. :) If you don't do this, a lot of software (nslookup for example) will try to resolve the PTR record for the name server you have. By referring to a dns that you are primary for, you save this ugly step. >Where is this file? You shouldn't have it on any system which runs a >name server. If this is really *on* samara.co.zw, remove or rename >it, and try again. If it still doesn't work, let's see your >/etc/named.boot file. Removing it will solve the problem too, since FreeBSD by default looks at localhost for the resolver. But if you want to specify backup name servers, follow the steps outlined above. Hope this helps, Doug Do thou amend they face, and I'll amend my life. -Shakespeare, "Henry V"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708080440.VAA11864>