Date: Wed, 21 Dec 2005 14:21:43 -0500 (EST) From: doug@safeport.com To: freebsd-questions@FreeBSD.ORG Subject: RE: nslookup strangeness Message-ID: <20051221140517.N71203@pemaquid.safeport.com> In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAWk27stpn1EeEJTAPYrt2mMKAAAAQAAAANyMf%2BCEpokSpcd2Xvj1LGgEAAAAA@bloemgarten.demon.nl> References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAWk27stpn1EeEJTAPYrt2mMKAAAAQAAAANyMf%2BCEpokSpcd2Xvj1LGgEAAAAA@bloemgarten.demon.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi - thanks for the reply. The host in question runs named because it is also a secondary name server for the domains Safeport hosts. I also use it as the name server for our internal network. The error is that nslookup terminates after the message and that I apparently changed something as this as been this way for years. What I was looking for is some other log/file that might give an indication of why the server will not answer the IPV4 query sent on 192.168.3.1. On Tue, 20 Dec 2005, Ruben Bloemgarten wrote: > Hi Douglas, > > If you are using dns relay on your gateway why would you want to use named ? > Also, it might be an idea to put the dns server ( i.e. the gateway) in your > resolv.conf. Furthermore, neither your hosts ip4 ip (192.168.3.1) nor your > non existant ip6 ip (:::) should be able to be resolved, unless you've set > this up specifically yourself. In short, your 'error' message is more > message than error. > > Regards, > Ruben > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of doug@safeport.com > Sent: December 20, 2005 6:37 PM > To: freebsd-questions@FreeBSD.ORG > Subject: nslookup strangeness > > I was using nslookup because of its convenient syntax to do some stuff. My > workstation communicates via a gateway which also severs as its name server. > I > get the following: > > nslookup > *** Can't find server name for address 192.168.3.1: Non-existent host/domain > *** Can't find server name for address ::: No response from server > *** Default servers are not available > > However dig works fine as does "regular" use of DNS. > > /etc/resolv.conf: nameserver 192.168.3.1 > > I started and stopped named and was able to use nslookup for a while. > > My question for the list is where I might look to find an indication of the > error. there is nothing in /var/log/messages or all.log. Sockstat shows > named > listening on 192.168.3.1. Except for an occasional abnormally long response > using ssh DNS also works normally. > > Thanks for any ideas. > > _____ > Douglas Denault > http://www.safeport.com > doug@safeport.com > Voice: 301-469-8766 > Fax: 301-469-0601 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.1/207 - Release Date: 12/19/2005 > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.1/207 - Release Date: 12/19/2005 > > _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-469-8766 Fax: 301-469-0601
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051221140517.N71203>