| 1 |
My thanks to all who replied to my question. |
| 2 |
|
| 3 |
The problem was with my local router, which I also used as DNS. |
| 4 |
After excluding it from /etc/resolv.config and /etc/init.d/net files, |
| 5 |
Firefox started to work as expected. |
| 6 |
|
| 7 |
Thanks to all of you, I now have a working Gentoo on my desktop!!! |
| 8 |
|
| 9 |
Still, a small problem that vlc hangs the GNOME, but I hope to solve |
| 10 |
it in the nearest future (or post a separate question). |
| 11 |
|
| 12 |
Below is the full report of what I did reacting on your suggestions. |
| 13 |
|
| 14 |
Suggestions of Mark Pariente: |
| 15 |
|
| 16 |
>> Internet browsers (I have tried Firefox and Links) can connect to |
| 17 |
>> the WWW if I type the IP address as, for example, 173.194.71.104 |
| 18 |
>> but cannot if I type www.google.com |
| 19 |
>> |
| 20 |
>> And this is strange because the host utility works as expected |
| 21 |
>> (converting www.google.com into 173.194.71.104) just adding the |
| 22 |
>> following "Warning: query response not set." |
| 23 |
|
| 24 |
> Do other command line tools like ping work? |
| 25 |
|
| 26 |
Yes, the ping command works for everything I have tried including all |
| 27 |
the DNS I put into my resolv.conf file. |
| 28 |
|
| 29 |
> It looks like your DNS setup is correct but for some reason the GNOME setup isn't. |
| 30 |
|
| 31 |
At first, I also blamed GNOME. However, after trying the Links web browser from |
| 32 |
a bare console (and obtaining the same results), it seems to me that the GNOME |
| 33 |
setup cannot be responsible for this problem |
| 34 |
|
| 35 |
> Few things: |
| 36 |
> Are you using NetworkManager? Is the 'networkmanager' USE flag |
| 37 |
> enabled? If so try going to Settings->Network->Wired->gear icon->IPv4 |
| 38 |
> and see what the DNS settings are like. |
| 39 |
|
| 40 |
I have emerged GNOME with the default set of USE flags and currently |
| 41 |
I have no NetworkManager in my GNOME menu. |
| 42 |
|
| 43 |
> Also in Settings->Network, see if Network proxy is (mis)configured. |
| 44 |
|
| 45 |
My GNOME Network Proxy Preferences show the option Direct Internet |
| 46 |
Connection enabled. |
| 47 |
|
| 48 |
Suggestions of Michael Kintzios |
| 49 |
|
| 50 |
>> the host utility works as expected (converting www.google.com into 173.194.71.104) |
| 51 |
>> just adding the following "Warning: query response not set." |
| 52 |
|
| 53 |
> Hmm .. wonder if this is something to do with your dns repeater |
| 54 |
> (your lan router) sending malformed packets in response? |
| 55 |
|
| 56 |
I am using Dlink DI-LB604 as my lan router and gateway. |
| 57 |
|
| 58 |
>> The ifconfig utility shows that instead of eth0 I have somewhat |
| 59 |
>> strange enp2s15 but I have played with this and found no difference |
| 60 |
>> after forcing udev to name it eth0. |
| 61 |
|
| 62 |
> This is the new kernel naming scheme of NICs. Which-ever nomenclature you |
| 63 |
> decide to use, check that that's the only one having a symlink in /etc/init.d |
| 64 |
> to net.lo |
| 65 |
|
| 66 |
Yes, there is only enp2s15 links to lo in /etc/init.d |
| 67 |
|
| 68 |
> try leaving only your router's local_network_IP in [your /etc/conf.d/net file] |
| 69 |
|
| 70 |
After deleting all but my lan router DNS from /etc/conf.d/net and |
| 71 |
/etc/resolv.conf |
| 72 |
files, I had the same problem as before but in addition the host |
| 73 |
utility reports an |
| 74 |
additional error. Please, see the full response below. |
| 75 |
|
| 76 |
# host www.google.com |
| 77 |
www.google.com has address 74.125.232.52 |
| 78 |
www.google.com has address 74.125.232.48 |
| 79 |
www.google.com has address 74.125.232.49 |
| 80 |
www.google.com has address 74.125.232.50 |
| 81 |
www.google.com has address 74.125.232.51 |
| 82 |
;; Warning: query response not set |
| 83 |
;; Warning: query response not set |
| 84 |
Host www.google.com not found: 4(NOTIMP) |
| 85 |
|
| 86 |
After leaving in /etc/conf.d/net and /etc/resolv.conf files only the |
| 87 |
DNS of my service |
| 88 |
provider, Firefox started to work as predicted. Thank you! |
| 89 |
|
| 90 |
> Can you please show us: |
| 91 |
> ip route show |
| 92 |
> ip addr show |
| 93 |
> ip link show |
| 94 |
|
| 95 |
$ ip route show |
| 96 |
default via 192.168.0.1 dev enp2s15 metric 2 |
| 97 |
127.0.0.0/8 via 127.0.0.1 dev lo scope link |
| 98 |
192.168.0.0/24 dev enp2s15 proto kernel scope link src 192.168.0.9 |
| 99 |
$ ip addr show |
| 100 |
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN |
| 101 |
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 |
| 102 |
inet 127.0.0.1/8 scope host lo |
| 103 |
inet6 ::1/128 scope host |
| 104 |
valid_lft forever preferred_lft forever |
| 105 |
2: enp2s15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc |
| 106 |
pfifo_fast state UP qlen 1000 |
| 107 |
link/ether <MAC_address_of_my_Ethernet_card> brd ff:ff:ff:ff:ff:ff |
| 108 |
inet 192.168.0.7/24 brd 192.168.0.255 scope global enp2s15 |
| 109 |
inet6 <IPv6_address_of_my_Ethernet_card>/64 scope link |
| 110 |
valid_lft forever preferred_lft forever |
| 111 |
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN |
| 112 |
link/sit 0.0.0.0 brd 0.0.0.0 |
| 113 |
$ ip link show |
| 114 |
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN |
| 115 |
mode DEFAULT |
| 116 |
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 |
| 117 |
2: enp2s15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc |
| 118 |
pfifo_fast state UP mode DEFAULT qlen 1000 |
| 119 |
link/ether <MAC_address_of_my_Ethernet_card> brd ff:ff:ff:ff:ff:ff |
| 120 |
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT |
| 121 |
link/sit 0.0.0.0 brd 0.0.0.0 |
| 122 |
|
| 123 |
Suggestions of Kurian Thayil |
| 124 |
|
| 125 |
> Can you do a ping and see if the resolv.conf DNS ips are reachable? |
| 126 |
|
| 127 |
Yes, I can ping all my DNS. Moreover, I successfully use them from my |
| 128 |
Ubuntu installation on the same computer. |
| 129 |
|
| 130 |
> do a |
| 131 |
> dig @8.8.8.8 www.google.com ## which will do a name resolution with Google DNS servers. |
| 132 |
|
| 133 |
Here is the output: |
| 134 |
|
| 135 |
$ dig @8.8.8.8 www.google.co |
| 136 |
|
| 137 |
; <<>> DiG 9.9.2 <<>> @8.8.8.8 www.google.co |
| 138 |
; (1 server found) |
| 139 |
;; global options: +cmd |
| 140 |
;; Got answer: |
| 141 |
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4036 |
| 142 |
;; flags: qr rd ra; QUERY: 1, ANSWER: 12, AUTHORITY: 4, ADDITIONAL: 5 |
| 143 |
|
| 144 |
;; OPT PSEUDOSECTION: |
| 145 |
; EDNS: version: 0, flags:; udp: 4096 |
| 146 |
;; QUESTION SECTION: |
| 147 |
;www.google.co. IN A |
| 148 |
|
| 149 |
;; ANSWER SECTION: |
| 150 |
www.google.co. 86400 IN CNAME www3.l.google.com. |
| 151 |
www3.l.google.com. 13 IN A 173.194.32.166 |
| 152 |
www3.l.google.com. 13 IN A 173.194.32.167 |
| 153 |
www3.l.google.com. 13 IN A 173.194.32.168 |
| 154 |
www3.l.google.com. 13 IN A 173.194.32.169 |
| 155 |
www3.l.google.com. 13 IN A 173.194.32.174 |
| 156 |
www3.l.google.com. 13 IN A 173.194.32.160 |
| 157 |
www3.l.google.com. 13 IN A 173.194.32.161 |
| 158 |
www3.l.google.com. 13 IN A 173.194.32.162 |
| 159 |
www3.l.google.com. 13 IN A 173.194.32.163 |
| 160 |
www3.l.google.com. 13 IN A 173.194.32.164 |
| 161 |
www3.l.google.com. 13 IN A 173.194.32.165 |
| 162 |
|
| 163 |
;; AUTHORITY SECTION: |
| 164 |
google.com. 244594 IN NS ns3.google.com. |
| 165 |
google.com. 244594 IN NS ns2.google.com. |
| 166 |
google.com. 244594 IN NS ns4.google.com. |
| 167 |
google.com. 244594 IN NS ns1.google.com. |
| 168 |
|
| 169 |
;; ADDITIONAL SECTION: |
| 170 |
ns1.google.com. 191550 IN A 216.239.32.10 |
| 171 |
ns2.google.com. 191550 IN A 216.239.34.10 |
| 172 |
ns3.google.com. 191550 IN A 216.239.36.10 |
| 173 |
ns4.google.com. 191550 IN A 216.239.38.10 |
| 174 |
|
| 175 |
;; Query time: 96 msec |
| 176 |
;; SERVER: 8.8.8.8#53(8.8.8.8) |
| 177 |
;; WHEN: Mon Aug 5 07:59:45 2013 |
| 178 |
;; MSG SIZE rcvd: 385 |
| 179 |
|
| 180 |
> also pls post make sure you have correct routing table (route -n) |
| 181 |
|
| 182 |
route -n |
| 183 |
Kernel IP routing table |
| 184 |
Destination Gateway Genmask Flags Metric Ref Use Iface |
| 185 |
0.0.0.0 192.168.0.1 0.0.0.0 UG 2 0 0 enp2s15 |
| 186 |
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo |
| 187 |
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp2s15 |
Archives