Date: Mon, 12 Mar 2001 10:03:51 -0000 From: Paul Crossley <paul.crossley@uk.easynet.net> To: 'Luke Kearney' <lukek@tkh.att.ne.jp>, Free BSD <freebsd-questions@FreeBSD.ORG> Subject: RE: named troubles Message-ID: <BE88953625EDD311A1C600508B5A9C5802451072@magrat.office.easynet.net>
next in thread | raw e-mail | index | archive | help
The nslookup problem is a fairly common one for new setups, until you fix this one you won't get much that's useful out of nslookup. Unfortunately the first thing nslookup does is try to tell you the NAME of the server that you are talking to , if it can't it gives up. You therefore need a reverse lookup to convert the ip address for your name server back into it's name. If you already have a reverse mapping for the loopback address you could set your nameserver to 127.0.0.1 until you've got things going, otherwise you will need to set up an authoritative domain for reverse name lookups - in your case you need to be authoritative for 0.168.192.in-addr.arpa. The zone file for this domain will have PTR records to turn the ip addresses into names. Adress to mane lookups are resolved by the same mechanism as name to address so the octets in the zone name (0.168.192) have to be written with the most specific portion on the left just as you do with domain names. Portmapper doesn't get involved with dns but you should see named running in fact I wonder whether it IS starting up but you've been fooled by the nslookup problem, your startup messages certainly make it look as if somethings already listening on port 53. Do a ps and check whether named is there. Problems in the configuration file or zone files can cause the nameserver to abort at startup so don't assume that they are correct. -----Original Message----- From: Luke Kearney [mailto:lukek@tkh.att.ne.jp] Sent: 12 March 2001 09:49 To: Free BSD Subject: named troubles Hi, I having no end of trouble in understanding what is going on with my name server setup. I have a server running FreeBSD 4.2 release and named 8.2.3 which I will upgrade just as soon as I can get this version to work properly ). The machine is an internal network nameserver with 2 NIC's. The NIC's have different IP's . The portmapper daemon is running. Mar 12 18:39:28 asakusa named[271]: bind(dfd=20, [192.168.0.2].53): Address already in use Mar 12 18:39:28 asakusa named[271]: deleting interface [192.168.0.2].53 Mar 12 18:39:28 asakusa named[271]: bind(dfd=22, [127.0.0.1].53): Address already in use Mar 12 18:39:28 asakusa named[271]: deleting interface [127.0.0.1].53 Mar 12 18:39:28 asakusa named[272]: Ready to answer queries. Mar 12 18:40:21 asakusa /kernel: arp: 192.168.0.2 is on lo0 but got reply from 00:90:99:24:62:e7 on xl0 Mar 12 18:40:56 asakusa /kernel: arp: 192.168.0.1 is on vr0 but got reply from 00:90:cc:08:31:83 on xl0 Mar 12 18:41:07 asakusa /kernel: arp: 192.168.0.1 is on vr0 but got reply from 00:90:cc:08:31:83 on xl0 Whenever I start named it dies pretty much instantly and the following messages appear when I try nslookups bash-2.04# nslookup localhost *** Can't find server name for address 192.168.0.2: Timed out *** Default servers are not available resolv.conf looks something like this bash-2.04# cat /etc/resolv.conf domain meibin.net nameserver 192.168.0.2 Any mistakes in my zone files don't seem to be the problem because initially I cannot get named started. This is probably something of a newbie question but any guidance is really appreciated. Thanks Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE88953625EDD311A1C600508B5A9C5802451072>