wget not resolving domain names
Paul Howarth
paul at city-fan.org
Tue Nov 1 10:52:33 UTC 2005
Cameron Beattie wrote:
> I have the following issue where wget won't resolve a domain name the
> first time I try it. It will only resolve the name once I do an nslookup.
>
> /etc/resolv.conf
> nameserver 192.168.0.253
>
> ping fedoraproject.org
> PING fedoraproject.org (152.3.183.74) 56(84) bytes of data.
> 64 bytes from fedoraproject.org (152.3.183.74): icmp_seq=0 ttl=44
> time=286 ms
>
> wget http://fedoraproject.org/extras/3/i386/plone-2.0.5-2.noarch.rpm
> --05:11:00--
> http://fedoraproject.org/extras/3/i386/plone-2.0.5-2.noarch.rpm
> => `plone-2.0.5-2.noarch.rpm'
> Resolving fedoraproject.org... 1.0.0.0
> Connecting to fedoraproject.org|1.0.0.0|:80...
>
> nslookup
>
>> fedoraproject.org
>
> Server: 192.168.0.253
> Address: 192.168.0.253#53
>
> Non-authoritative answer:
> Name: fedoraproject.org
> Address: 152.3.183.74
>
> wget http://fedoraproject.org/extras/3/i386/plone-2.0.5-2.noarch.rpm
> --05:11:37--
> http://fedoraproject.org/extras/3/i386/plone-2.0.5-2.noarch.rpm
> => `plone-2.0.5-2.noarch.rpm'
> Resolving fedoraproject.org... 152.3.183.74
> Connecting to fedoraproject.org|152.3.183.74|:80... connected.
>
> I am using Fedora Core 3.
>
> I'm sure there is a very simple solution. Any help would be appreciated.
Please post the output of:
$ grep hosts /etc/nsswitch.conf
Is the nameserver at 192.168.0.253 reliable?
Try looking up an IP address that you haven't tried recently and see if
it returns the same results every time, e.g.
$ dig @192.168.0.253 www.uit.no
$ dig @192.168.0.253 www.uit.no
Paul.
More information about the users
mailing list