Problem using DNSMasq and name resolution

Discussion in 'DD-WRT Firmware' started by conman, Jan 18, 2006.

  1. conman

    conman Network Guru Member

    DDWrt V23SP1
    WRT54GS V3 being used as main router/AP
    LAN consisting of several mixed clients (W2k, XP, VOIP adapters)
    plus two WDS bridges supplying some further clients.

    DDWrt configuration:
    DNSMasq with leases on JFFS2
    A subset of clients defined with static DHCP via DDWrt UI

    All basic operations viz. internet connectivity, bridging, wireless and security work correctly. I've telnet'ed to the router, and everything looks good there as well - jffs filesystem, mounts etc. etc.

    The DHCP client table in the GUI is always empty, even after I renew the DHCP lease on the various clients. The same happened to me with V23 as well.

    There are a number of non-Windows clients on my LAN (VOIP adapter, print server). I'm unable to ping any of them by name, even though they are visible via nslookup.
    However, I'm able to ping them if I append "." after their name.
    e.g. My voip adapter is named ATT.
    "ping ATT" does not work (Unknown host ATT)
    "ping ATT." does work.

    I'm presumably able to ping all my Win2k/XP clients by name because their names are being resolved via Netbios broadcast - I confirmed this by looking at their Netbios caches (nbtstat -c).

    Is there any way I can remove this inconsistency viz. having to append a period on the names of some lan-clients, while not others ... ?

    Thanks for any help.
  2. Couledouce

    Couledouce Network Guru Member

    Problem 1 is a known problem, has a bugtracker link, you can register and find the reference there.

    For problem 2 I have no idea.
  3. mingus

    mingus Guest

    I'm also having the same problem with lookups. I'm at a bit of a loss because it's not like there are a whole lot of options to configure in the GUI

    (2)re-501:~/ nslookup -sil puppies
    Name:   puppies
    (3)re-501:~/ ping puppies
    ping: cannot resolve puppies: Unknown host
    clients are Mac OS X and linux. Router is a v2.2 running v23 of DD-WRT
  4. Marsha

    Marsha Network Guru Member

    Welcome to the world of lightly documented :eek: software!

    Named devices (using DNSMasq) assume a "domain" name follows. Such as .lan or .home or ........

    So, if you use nothing, it still looks for the "." Just the way it was programmed, I guess; no one has changed/improved it.

    In a Windows environment, I suggest you use a name of your liking ( say .lan ) in the DNS setup, and then in your computers, under advanced settings for TCP/IP, have it append .lan to as a DNS suffix. Do the equivalent operation on Linux and Mac's. Problem usually solved.
  5. conman

    conman Network Guru Member

    Thanks, you nailed it. That solves it.
    I also used the "expand-hosts" option for DNSMasq, to be consistent and safe.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice