My thanks to all who replied to my question.

The problem was with my local router, which I also used as DNS.
After excluding it from /etc/resolv.config and /etc/init.d/net files,
Firefox started to work as expected.

Thanks to all of you, I now have a working Gentoo on my desktop!!!

Still, a small problem that vlc hangs the GNOME, but I hope to solve
it in the nearest future (or post a separate question).

Below is the full report of what I did reacting on your suggestions.

Suggestions of Mark Pariente:

>> Internet browsers (I have tried Firefox and Links) can connect to
>> the WWW if I type the IP address as, for example, 173.194.71.104
>> but cannot if I type www.google.com
>>
>> And this is strange because the host utility works as expected
>> (converting www.google.com into 173.194.71.104) just adding the
>> following "Warning: query response not set."

> Do other command line tools like ping work?

Yes, the ping command works for everything I have tried including all
the DNS I put into my resolv.conf file.

> It looks like your DNS setup is correct but for some reason the GNOME setup 
> isn't.

At first, I also blamed GNOME. However, after trying the Links web browser from
a bare console (and obtaining the same results), it seems to me that the GNOME
setup cannot be responsible for this problem

> Few things:
> Are you using NetworkManager? Is the 'networkmanager' USE flag
> enabled? If so try going to Settings->Network->Wired->gear icon->IPv4
> and see what the DNS settings are like.

I have emerged GNOME with the default set of USE flags and currently
I have no NetworkManager in my GNOME menu.

> Also in Settings->Network, see if Network proxy is (mis)configured.

My GNOME Network Proxy Preferences show the option Direct Internet
Connection enabled.

Suggestions of  Michael Kintzios

>> the host utility works as expected (converting www.google.com into 
>> 173.194.71.104)
>> just adding the following "Warning: query response not set."

> Hmm .. wonder if this is something to do with your dns repeater
> (your lan router) sending malformed packets in response?

I am using Dlink DI-LB604 as my lan router and gateway.

>> The ifconfig utility shows that instead of eth0 I have somewhat
>> strange enp2s15 but I have played with this and found no difference
>> after forcing udev to name it eth0.

> This is the new kernel naming scheme of NICs.  Which-ever nomenclature you
> decide to use, check that that's the only one having a symlink in /etc/init.d
> to net.lo

Yes, there is only enp2s15 links to lo in /etc/init.d

> try leaving only your router's local_network_IP in [your /etc/conf.d/net file]

After deleting all but my lan router DNS from /etc/conf.d/net and
/etc/resolv.conf
files, I had the same problem as before but in addition the host
utility reports an
additional error. Please, see the full response below.

# host www.google.com
www.google.com has address 74.125.232.52
www.google.com has address 74.125.232.48
www.google.com has address 74.125.232.49
www.google.com has address 74.125.232.50
www.google.com has address 74.125.232.51
;; Warning: query response not set
;; Warning: query response not set
Host www.google.com not found: 4(NOTIMP)

After leaving in /etc/conf.d/net and /etc/resolv.conf files only the
DNS of my service
provider, Firefox started to work as predicted. Thank you!

> Can you please show us:
> ip route show
> ip addr show
> ip link show

$ ip route show
default via 192.168.0.1 dev enp2s15  metric 2
127.0.0.0/8 via 127.0.0.1 dev lo  scope link
192.168.0.0/24 dev enp2s15  proto kernel  scope link  src 192.168.0.9
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP qlen 1000
    link/ether <MAC_address_of_my_Ethernet_card> brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.7/24 brd 192.168.0.255 scope global enp2s15
    inet6 <IPv6_address_of_my_Ethernet_card>/64 scope link
       valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether <MAC_address_of_my_Ethernet_card> brd ff:ff:ff:ff:ff:ff
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT
    link/sit 0.0.0.0 brd 0.0.0.0

Suggestions of Kurian Thayil

> Can you do a ping and see if the resolv.conf DNS ips are reachable?

Yes, I can ping all my DNS. Moreover, I successfully use them from my
Ubuntu installation on the same computer.

> do a
> dig @8.8.8.8 www.google.com ## which will do a name resolution with Google 
> DNS servers.

Here is the output:

$ dig @8.8.8.8 www.google.co

; <<>> DiG 9.9.2 <<>> @8.8.8.8 www.google.co
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4036
;; flags: qr rd ra; QUERY: 1, ANSWER: 12, AUTHORITY: 4, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.google.co.                 IN      A

;; ANSWER SECTION:
www.google.co.          86400   IN      CNAME   www3.l.google.com.
www3.l.google.com.      13      IN      A       173.194.32.166
www3.l.google.com.      13      IN      A       173.194.32.167
www3.l.google.com.      13      IN      A       173.194.32.168
www3.l.google.com.      13      IN      A       173.194.32.169
www3.l.google.com.      13      IN      A       173.194.32.174
www3.l.google.com.      13      IN      A       173.194.32.160
www3.l.google.com.      13      IN      A       173.194.32.161
www3.l.google.com.      13      IN      A       173.194.32.162
www3.l.google.com.      13      IN      A       173.194.32.163
www3.l.google.com.      13      IN      A       173.194.32.164
www3.l.google.com.      13      IN      A       173.194.32.165

;; AUTHORITY SECTION:
google.com.             244594  IN      NS      ns3.google.com.
google.com.             244594  IN      NS      ns2.google.com.
google.com.             244594  IN      NS      ns4.google.com.
google.com.             244594  IN      NS      ns1.google.com.

;; ADDITIONAL SECTION:
ns1.google.com.         191550  IN      A       216.239.32.10
ns2.google.com.         191550  IN      A       216.239.34.10
ns3.google.com.         191550  IN      A       216.239.36.10
ns4.google.com.         191550  IN      A       216.239.38.10

;; Query time: 96 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Aug  5 07:59:45 2013
;; MSG SIZE  rcvd: 385

> also pls post make sure you have correct routing table (route -n)

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    2      0        0 enp2s15
127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0 lo
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp2s15

Reply via email to