Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.42!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder2-2.proxad.net!nx01.iad01.newshosting.com!newshosting.com!69.16.185.21.MISMATCH!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.supernews.com!news.supernews.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 15 Oct 2011 15:31:03 -0500 Newsgroups: comp.os.linux.networking,alt.os.linux.slackware Subject: Re: Only some IPs accessable? References: <2hpim8x384.ln2@news.roaima.co.uk> <87ty7av2ar.fld@apaflo.com> From: floyd@apaflo.com (Floyd L. Davidson) Organization: __________ Date: Sat, 15 Oct 2011 12:30:55 -0800 Message-ID: <87d3dyuhds.fld@apaflo.com> User-Agent: gnus 5.10.6/XEmacs 21.4.15/Linux 2.6.27 Cancel-Lock: sha1:Q7MVxjdt1yY/8ZhDU6OL6JnyQX0= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 62 X-Trace: sv3-SuveCZiO2FZ76vnaeSi8jfBw7fVq2V5l4RXAnFdGwcBntjGvgOjuV+AHAGr9lX4ay/OzBT6MqCbQP9+!Pw7OQ/U6JU2TaPd4uycLFxOqqZoc/3sCcGqyXrZylrRMd1AsAlsrVHRsNuGtdQ== X-Complaints-To: www.supernews.com/docs/abuse.html X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3227 Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.networking:708 Henrik Carlqvist wrote: >Now, when trying to recreate that I only got partial success. I have no >DNS server running on localhost: > >-8<--------------------- >bash-3.1# cat /etc/resolv.conf ># Generated by dhcpcd for interface wlan0 >search Belkin >nameserver 192.168.30.254 ... >bash-3.1# time nslookup www.google.com >Server: 192.168.30.254 >Address: 192.168.30.254#53 > >Name: www.google.com >Address: 209.85.169.105 > >real 0m0.104s >user 0m0.004s >sys 0m0.004s That is as expected. >bash-3.1# emacs -nw /etc/resolv.conf >bash-3.1# cat /etc/resolv.conf ># Generated by dhcpcd for interface wlan0 >search Belkin >nameserver 192.168.30.254 >nameserver 127.0.0.1 > >bash-3.1# time nslookup www.google.com >;; Got recursion not available from 192.168.30.254, trying next server >;; connection timed out; no servers could be reached > >real 0m15.113s >user 0m0.004s >sys 0m0.000s >-8<--------------------- On my system the same configuration results in exactly the same time as with only a single valid nameserver entry. If I put the invalid entry first it takes about 1 second longer. I only get the 15 second time out if there are no valid entries. >In the example above "nslookup www.google.com" takes 0.1s with a single >working nameserver in resolv.conf. Adding a broken nameserver increases >that time to 15s and also gives no answer. This test was done on Slackware >12.2. I'm using Slackware 13.37, but have never seen it any different. >The above example does not behave exactly as I remembered the problem, but >at least it shows there is something fishy with nslookup. Yep, that's downright weird! -- Floyd L. Davidson Ukpeagvik (Barrow, Alaska) floyd@apaflo.com