You are not logged in.

#1 2009-12-12 21:06:54

olol85
Member
Registered: 2009-12-12
Posts: 4

name resolving with protocol prefix issue

Hi!

First message on this forum, welcome to me smile

I'm having troubles resolving names when the adress is typed with the protocol prefix, for example:

lau@cigogne: ~ $ host http://www.google.com
Host http://www.google.com not found: 3(NXDOMAIN)

now, removing the http:// part gives:

host www.google.com
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 74.125.43.103
www.l.google.com has address 74.125.43.104
www.l.google.com has address 74.125.43.105
www.l.google.com has address 74.125.43.106
www.l.google.com has address 74.125.43.147
www.l.google.com has address 74.125.43.99

This is pretty annoying when trying, for example, to use the makepkg utility. Also, the evolution mail client can't access pop/imap servers (name resolving failure) because of this.

Offline

#2 2009-12-12 21:10:23

olol85
Member
Registered: 2009-12-12
Posts: 4

Re: name resolving with protocol prefix issue

btw, i'm currently using wicd to connect to my wifi router (which i think is properly configured).

Offline

#3 2009-12-12 22:12:22

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: name resolving with protocol prefix issue

Same results here, with the host comand - but I have no trouble with makepkg, or anything else. :?

Offline

#4 2009-12-12 22:34:26

olol85
Member
Registered: 2009-12-12
Posts: 4

Re: name resolving with protocol prefix issue

ok now it's becoming really weird: i manage to ping the host:

lau@cigogne: ~ $ ping archlinux.mirror.kangaroot.netPING mirrorhost.kangaroot.net (62.213.203.174) 56(84) bytes of data.
64 bytes from mirrorhost.kangaroot.net (62.213.203.174): icmp_seq=1 ttl=52 time=52.3 ms
64 bytes from mirrorhost.kangaroot.net (62.213.203.174): icmp_seq=2 ttl=52 time=103 ms
^C
--- mirrorhost.kangaroot.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 52.362/77.688/103.015/25.328 ms

but can't ping it with the http:// prefix (which must be related with the name resolving issue):

and wget doesn't work either with or without the prefix:

lau@cigogne: ~ $ wget archlinux.mirror.kangaroot.net/iso/2009.08/archlinux-2009.08-netinstall-x86_64-isolinux.iso
--2009-12-12 23:33:45--  http://archlinux.mirror.kangaroot.net/i … olinux.iso
Resolving archlinux.mirror.kangaroot.net... failed: Temporary failure in name resolution.
wget: unable to resolve host address "archlinux.mirror.kangaroot.net"

lau@cigogne: ~ $ wget http://archlinux.mirror.kangaroot.net/i … olinux.iso
--2009-12-12 23:34:14--  http://archlinux.mirror.kangaroot.net/i … olinux.iso
Resolving archlinux.mirror.kangaroot.net... failed: Temporary failure in name resolution.
wget: unable to resolve host address "archlinux.mirror.kangaroot.net"

any idea?

Offline

#5 2009-12-12 23:35:23

mikesd
Member
From: Australia
Registered: 2008-02-01
Posts: 788
Website

Re: name resolving with protocol prefix issue

@OP

DNS has no direct relation to HTTP. HTTP is a protocol that web clients/servers use to communicate. DNS only knows about host names. Prepending http:// to a hostname and then trying to do a DNS lookup on it will not work unless the DNS client is clever enough to drop it, such as a web browser.

Likewise  Ping doesn't use HTTP either. This won't work either. Don't prepend hostnames with http:// when pinging them.

From the sound of it you have some sort of DNS issue. Check your resolv.conf file and check your nameserver settings.

Offline

#6 2009-12-13 13:01:02

olol85
Member
Registered: 2009-12-12
Posts: 4

Re: name resolving with protocol prefix issue

Solved, the problem was that in my resolv.conf file, the ip adress of the dns server was set to a local ip: 192.168.1.1
i checked on my router configuration page, and changed the latter by the external ip adress.

thanks!

Offline

Board footer

Powered by FluxBB