Your problem definitely seems to lie in DNS configuration. The great general troubleshooting guide written by Shawn contains a lot of useful information and based on it, you might verify whether the problem is connected with DNS. Adding to Shawn's suggestions, I'd recommend you to try manually resolving a hostname using
host like this (
microsoft.com is just a nice example ;) ) :
(this should yield no result if the DNS servers are not configures properly) and then
host microsoft.com 220.127.116.11
-this time you tell the
host tool explicitly what name server it should query. This should work regardless of what your
/etc/resolv.conf file contains.
Also, the fact that your wired connection works fine might be both a clue and a means of investigating the issue further. I suggest you do:
Connect though wire, verify web browsing works and then copy your
/etc/resolv.conf to some temporary place like
Disconnect the wire and connect via wireless. After establishing a connection (you can do a
ping 18.104.22.168 to test that), copy the contents of
/etc/resolv.conf to a second temporary file, say
Compare the two copied files. The first one should contain proper name servers, the second might contain none or a single improper entry such as your gateway address (typically
By now you probably understand why name resolution (typically needed for web browsing) does not work with your wireless configuration. However, it might be not obvious where the problem origins from.
Typically (n standard desktop distributions), the networking is controlled by a GUI program like NetworkManager or wicd. This tools are used to easily define how wired and wireless interfaces should connect to the network and, in each case, what information should be queried from the DHCP server.
So, finally, I believe that to solve your problem you just need to open up your network configuration GUI program and check how the configuration options for wired and wireless interface differ. It could be, for example, that the wired interface simply uses static configuration of both IP address and DNS. Another option is that both interfaces use DHCP, but one has some option ticked to use static DNS (those may be defined elsewhere).