Announcement

Collapse
No announcement yet.

WLAN0 will do reverse dns lookups but not forward

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    WLAN0 will do reverse dns lookups but not forward

    Laptop connects to a (wired) ethernet port on a DLINK DIR-625 wireless router using dhcp. All works perfectly.


    Using the same laptop connecting to the same wireless router, but using the wireless adapter and dhcp instead of wired ethernet, I can ping IP addresses on the LAN and also WAN IP's to/from anywhere on the net. I can perform reverse name resolutions (ip to host name), but not forward lookups (host names to ip addresses). I can use the DNS server obtained from dhcp or specify, by ip address, a DNS server to perform the lookups. This makes no difference.


    Web pages (LAN server pages or from the internet) are not accessible by site address name or by ip address specifically.



    This one has me stumped. I'd very much appreciate any ideas.


    -------------------------


    Kubuntu 11.01

    $ uname -r
    2.6.38-10-generic


    $ iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11bgn ESSID:"DLINK-DIR-625"
    Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:58:2E:EE:5F
    Bit Rate=58.5 Mb/s Tx-Power=20 dBm
    Retry long limit:7 RTS thrff Fragment thrff
    Power Managementn
    Link Quality=51/70 Signal level=-59 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:2 Missed beacon:0


    $ ifconfig
    eth0 Link encap:Ethernet HWaddr 00:0b:db:d7:eb:c3
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:14 errors:0 dropped:0 overruns:0 frame:0
    TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:780 (780.0 B) TX bytes:780 (780.0 B)

    wlan0 Link encap:Ethernet HWaddr c8:3a:35:cb:a7:88
    inet addr:192.168.0.188 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::ca3a:35ff:fecb:a788/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:69 errors:0 dropped:0 overruns:0 frame:0
    TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:9852 (9.8 KB) TX bytes:16223 (16.2 KB)


    $ route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.0.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
    169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
    0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0


    $ cat /etc/resolv.conf
    # Generated by NetworkManager
    nameserver 192.168.0.1


    $ ping 74.125.91.99
    PING 74.125.91.99 (74.125.91.99) 56(84) bytes of data.
    64 bytes from 74.125.91.99: icmp_req=1 ttl=47 time=44.0 ms
    64 bytes from 74.125.91.99: icmp_req=2 ttl=47 time=48.0 ms
    64 bytes from 74.125.91.99: icmp_req=3 ttl=47 time=47.9 ms
    64 bytes from 74.125.91.99: icmp_req=4 ttl=47 time=43.5 ms
    64 bytes from 74.125.91.99: icmp_req=5 ttl=47 time=45.2 ms
    64 bytes from 74.125.91.99: icmp_req=6 ttl=47 time=42.4 ms
    ^C
    --- 74.125.91.99 ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5006ms
    rtt min/avg/max/mdev = 42.438/45.202/48.002/2.130 ms


    $ ping www.google.com
    ping: unknown host www.google.com


    $ nslookup 74.125.91.99
    Server: 192.168.0.1
    Address: 192.168.0.1#53

    Non-authoritative answer:
    99.91.125.74.in-addr.arpa name = qy-in-f99.1e100.net.

    Authoritative answers can be found from:
    125.74.in-addr.arpa nameserver = NS2.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS1.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS4.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS3.GOOGLE.COM.


    $ nslookup 74.125.91.99 192.168.1.3
    Server: 192.168.1.3
    Address: 192.168.1.3#53

    Non-authoritative answer:
    99.91.125.74.in-addr.arpa name = qy-in-f99.1e100.net.

    Authoritative answers can be found from:
    125.74.in-addr.arpa nameserver = NS3.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS4.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS2.GOOGLE.COM.
    125.74.in-addr.arpa nameserver = NS1.GOOGLE.COM.


    $ nslookup www.google.com 192.168.1.3
    ;; connection timed out; no servers could be reached


    $ host www.google.com
    ;; connection timed out; no servers could be reached


    $ host 74.125.91.99
    99.91.125.74.in-addr.arpa domain name pointer qy-in-f99.1e100.net.


    $ host localhost
    localhost has address 127.0.0.1
    localhost has IPv6 address ::1


    $ dmesg
    [ 28.458110] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
    [ 28.458161] Intel ICH 0000:00:1f.5: setting latency timer to 64
    [ 28.787464] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 28.815019] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 29.292095] intel8x0_measure_ac97_clock: measured 55340 usecs (2666 samples)
    [ 29.292102] intel8x0: clocking to 48000
    [ 33.016949] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
    [ 36.215804] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
    [ 74.370991] wlan0: authenticate with 00:1e:58:2e:ee:5f (try 1)
    [ 74.372596] wlan0: authenticated
    [ 75.976219] wlan0: associate with 00:1e:58:2e:ee:5f (try 1)
    [ 75.978720] wlan0: RX AssocResp from 00:1e:58:2e:ee:5f (capab=0x431 status=0 aid=2)
    [ 75.978726] wlan0: associated
    [ 75.986865] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 76.189583] Intel AES-NI instructions are not detected.
    [ 76.233065] padlock_aes: VIA PadLock not detected.
    [ 86.984030] wlan0: no IPv6 routers present

    #2
    Re: WLAN0 will do reverse dns lookups but not forward

    I'd agree, the router likely does not have a DNS identified, and it should have at least one (I have two).
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Re: WLAN0 will do reverse dns lookups but not forward

      The router has 2 DNS servers... one local and one from the carrier.
      Connecting to the router by dhcp creates the client's DNS server as being the router.

      $ cat /etc/resolv.conf
      # Generated by NetworkManager
      nameserver 192.168.0.1

      I can create a manual connection and use the local DNS server with no change. All of this information has already been provided in the original post.

      Reverse lookups, as is shown to be working, wouldn't happen if no DNS server was available.

      Other computers connect using dhcp to the same router without fail. Ubuntu, Kubuntu and Fedora machines as well as any Windows machine.

      This issue is also on the Ubuntu forum.
      http://ubuntuforums.org/showthread.php?t=1806292

      Comment


        #4
        Re: WLAN0 will do reverse dns lookups but not forward

        So to be clear: Lookups, both reverse and forward, work when you use the wired connection, but do not when you use your wireless connection, both of which are served by the same router?
        Windows no longer obstructs my view.
        Using Kubuntu Linux since March 23, 2007.
        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

        Comment


          #5
          Re: WLAN0 will do reverse dns lookups but not forward

          Originally posted by Snowhog
          So to be clear: Lookups, both reverse and forward, work when you use the wired connection, but do not when you use your wireless connection, both of which are served by the same router?
          Yes, that is correct.

          Comment


            #6
            Re: WLAN0 will do reverse dns lookups but not forward

            Your resolv.conf file is mis-configured. It holds your local IP address when it should be holding the primary and secondary DNS IP addresses of your ISP.

            Here's mine:
            cat /etc/resolv.conf
            nameserver 207.69.188.186
            nameserver 207.69.188.187
            domain earthlink.net
            search earthlink.net
            My local IP address is 192.168.1.100.
            The IP of my wireless router is 192.168.1.1

            You appear to have the IP address of your wireless router in your resolv.conf file.
            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
            – John F. Kennedy, February 26, 1962.

            Comment


              #7
              Re: WLAN0 will do reverse dns lookups but not forward

              That is incorrect if you configure your router to include static DNS IPs, in which case your /etc/resolv.conf only needs your routers IP address. This is how my /etc/resolv.conf configured - it only contains my router IP address. I have none of the issues to OP is getting.
              Windows no longer obstructs my view.
              Using Kubuntu Linux since March 23, 2007.
              "It is a capital mistake to theorize before one has data." - Sherlock Holmes

              Comment


                #8
                Re: WLAN0 will do reverse dns lookups but not forward

                Originally posted by GreyGeek
                Your resolv.conf file is mis-configured. It holds your local IP address when it should be holding the primary and secondary DNS IP addresses of your ISP.

                Here's mine:
                cat /etc/resolv.conf
                nameserver 207.69.188.186
                nameserver 207.69.188.187
                domain earthlink.net
                search earthlink.net
                My local IP address is 192.168.1.100.
                The IP of my wireless router is 192.168.1.1

                You appear to have the IP address of your wireless router in your resolv.conf file.
                Here is the resolv.conf for a different computer that's connected to the same router and has worked perfectly for 18 months:
                $ cat /etc/resolv.conf
                # Generated by NetworkManager
                nameserver 192.168.0.1

                I don't wish to have an optional default search or domain in resolv.conf.

                The name server IS the router at 192.168.0.1 That router has multiple DNS server addresses that is uses to do lookups and passes the results back the to the client computer. As I said, I can manually put my local DNS server address in resolv.conf (at no successful change or result) OR can do an nslookup and tell that command to use any DNS server I wish.

                However, after all of this has been said, no reverse resolution could be accomplished if there was no DNS server. The computer will succeed to do reverse DNS. I won't perform a forward lookup.
                Thank you.

                Comment


                  #9
                  Re: WLAN0 will do reverse dns lookups but not forward

                  Something in your routers configuration isn't correct. That all works correctly from a wired connection but not from a wireless one suggests this to be true. How did you set up the router configuration with regard to DNS? Did you specify both static and dynamic DNS?

                  In my routers configuration (Linksys WRT54GL using Tomato Version 1.28 firmware) I have three Static DNS IPs (Basic > Network > LAN), and under DDNS (Advanced > DHCP / DNS) I'm using my ISP's IP address (Use WAN IP Address [recommended]) and None for each of the two Service entries.
                  Windows no longer obstructs my view.
                  Using Kubuntu Linux since March 23, 2007.
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    Re: WLAN0 will do reverse dns lookups but not forward

                    Originally posted by Snowhog
                    Something in your routers configuration isn't correct. That all works correctly from a wired connection but not from a wireless one suggests this to be true. How did you set up the router configuration with regard to DNS? Did you specify both static and dynamic DNS?

                    In my routers configuration (Linksys WRT54GL using Tomato Version 1.28 firmware) I have three Static DNS IPs (Basic > Network > LAN), and under DDNS (Advanced > DHCP / DNS) I'm using my ISP's IP address (Use WAN IP Address [recommended]) and None for each of the two Service entries.
                    I don't like to be redundant by copying and pasting from my above posts, but other computers connect using dhcp to the same router without fail. Ubuntu, Kubuntu and Fedora machines as well as any Windows machine. In fact, the computer that I'm currently using on this Kubuntu board is connected by wireless to the same router. This has all been stated in my original and subsequent posts.

                    Comment


                      #11
                      Re: WLAN0 will do reverse dns lookups but not forward

                      Originally posted by gtrip
                      ..
                      The name server IS the router at 192.168.0.1 That router has multiple DNS server addresses that is uses to do lookups and passes the results back the to the client computer. ....
                      Which is the only place the IP of the ISP's DNS can be if they are not in resolv.conf. Did they get changed or over written?
                      "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                      – John F. Kennedy, February 26, 1962.

                      Comment


                        #12
                        Re: WLAN0 will do reverse dns lookups but not forward

                        Let's approach this from the "what network manager"are you using on the "problem" PC, and how is it configured for the wireless connection?
                        Windows no longer obstructs my view.
                        Using Kubuntu Linux since March 23, 2007.
                        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                        Comment


                          #13
                          Re: WLAN0 will do reverse dns lookups but not forward

                          The problem machine's IP address is 192.168.0.188. It's gateway is the router at 192.168.0.1. The DNS server is also the router. A client only needs one DNS address because if it's not connected to the router, it's not online anyway. The router has multiple DNS servers it uses to return an answer back to the client.

                          All of this has little matter since the resolv.conf is exactly the same as any other machine I have that successfully connects through that router.

                          This is as fresh of an install as can be of Kubuntu 11.01. What is loaded during the install and the updates immediately afterward is what's on that machine.7.

                          Comment


                            #14
                            Re: WLAN0 will do reverse dns lookups but not forward

                            *** SOLVED ***
                            Tenda W311U Wireless Adapter didn't work well with the DLINK DIR-625 wireless router's enabled settings of:

                            - Multicast Streams
                            - UPnP
                            - QOS Engine

                            Once these 3 items were disabled, forward and reverse DNS functioned and normal network traffic passed without fail. The Tenda WiFi adapter must be more sensitive than other adapters. Other computer's WiFi adapters never have had difficulties connecting to this DLINK router with these settings enabled as they were.

                            Comment


                              #15
                              Re: WLAN0 will do reverse dns lookups but not forward

                              Originally posted by Snowhog
                              That is incorrect if you configure your router to include static DNS IPs, in which case your /etc/resolv.conf only needs your routers IP address. This is how my /etc/resolv.conf configured - it only contains my router IP address. I have none of the issues to OP is getting.
                              I have my TP-LINK wireless router configured that way but resolv.conf is always given the settings I showed. A property of the specific wireless router?
                              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                              – John F. Kennedy, February 26, 1962.

                              Comment

                              Working...
                              X