1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

DNS resolution on slave WDS routers with DHCP disabled?

Discussion in 'Tomato Firmware' started by mvsgeek, Feb 24, 2012.

  1. mvsgeek

    mvsgeek Addicted to LI Member

    I want to name a specific PC on my LAN so that all LAN users can access its web server by name rather than fixed IP. All users connect to the main router via WDS slaves, which have DHCP disabled. The PC in question is connected to the main router via cat5. I've tried adding entries to /etc/hosts on a test slave, also adding the following to dnsmasq advanced config :


    but I can't ping wanker or wanker.mydomain from a PC connected to the slave, either wired or wirelessly. Ping to works as expected.

    I notice there was a bug fix for this in one of the recent 2.6 releases, but my slaves are WRT54GL's running a 2.4 variant (Exact versions are in my sig).

    Is there a dnsmasq option, or other method that I'm missing, that will permit DNS resolution when DHCP is disabled?
  2. skyanvi1

    skyanvi1 Addicted to LI Member

    To trouble shoot DNS issues enable logging in the custom configuration of your router.
    (web interface) Advanced : DHCP/DNS : Dnsmasq Custom configuration: add the switch `log-queries` without quotes .
    Watch the log by ssh or telnet (note user: root pass: same) and execute the following command:
    tail -f /var/log/messages
    This will actively update the log as you clear the DNS cache on your clients and ping your wankers.
  3. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "ping your wankers"

    We've come to that now have we?
  4. mvsgeek

    mvsgeek Addicted to LI Member

    OK, I went back to square one. Removed all entries from /etc/hosts, cleared all dnsmasq custom settings, on both master and slave. Ran ipconfig /flushdns, cleared browser cache on all PC's.

    Then as follows :

    1. Added 'mydomain' (no quotes) to routers - Basic --> Identification --> Domain Name
    2. Added a single entry in dnsmasq custom on main router only :


    3. Reverted all PC network properties back to dynamic allocation of IP address and DNS server address.

    And voila! I can "ping my wanker" successfully:) I still have an issue accessing wanker's web server with some browsers requiring the 'http://' prefix, but that's for another day, another forum.

    Skyanvi1, thanks for the 'log-queries' tip, that's a useful one. I'm using WallWatcher to log to a remote PC, so didn't use the 'tail' option.

    I can only assume that my problem was self-created, a consequence of specifying too many conflicting parameters among the various devices. Eliminating possible conflicts now ensures that DNS resolution is handled only by the main router.
  5. skyanvi1

    skyanvi1 Addicted to LI Member

    "We've come to that now have we?"
    I couldn't help myself...

    @mvsgeek -glad you have it sorted.

Share This Page