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

Issues with Wireless Ethernet Bridge mode

Discussion in 'Tomato Firmware' started by Kiwi8, Mar 5, 2008.

  1. Kiwi8

    Kiwi8 LI Guru Member

    For my main router, I can access it by the domain name I specified, namely "root.net" in addition to the IP address.

    But for my secondary router which is configured to the main router as a Wireless Ethernet Bridge, I can't seem to do so, even though I have specified a domain name on the router.

    What could be the problem, and what should I do to rectify it?

    Thanks in advance.
  2. HennieM

    HennieM Network Guru Member

    Resolving fully qualified domain names (FQDN) to IP addresses is a function of a DNS server. It has nothing to do with routers per se. So, your DNS server (wherever it is running) must know that

    FQDN whatevername.root.net = IP address x.x.x.x

    If you want reverse lookups, like find out what the FQDN is for IP address x.x.x.x, your DNS server must also know that

    IP address x.x.x.x = FQDN whatevername.root.net

    Thus, you must add your 2nd router's FQDN and IP address to your DNS server. From your post it sounds like you are using the DNS server on your main router, so see how you can add a static DNS entry on that router's DNS server.
  3. Kiwi8

    Kiwi8 LI Guru Member

    Wah that was a lot to absorb. :tongue:

    I dunno what to do. My internet connection is using the DNS server from my ISP. So how can I go about adding a static DNS entry on the router?

    Thanks in advance.
  4. houman

    houman LI Guru Member

    So your ISP is giving you DNS addresses, and you're using an extra one (like one associated in a VPN ?)

    or is it that you just can't access a domain name in your WET... ? Normally when you set the WET, everything accessible in your main router should be accessible in the WET to the devices you connect (I do that for example to my Xbox 360 & Tivo that are in the other room)
  5. Kiwi8

    Kiwi8 LI Guru Member

    Ok no. Let me explain again and describe my router situation.

    My main router has an address of and is associated with the domain name "mainrouter.net".

    My secondary router has an address of and is associated with the domain name "secondaryrouter.net".

    I able to resolve mainrouter.net, but not secondaryrouter.net. What should I do on the main or secondary router to be able to resolve secondaryrouter.net to
  6. houman

    houman LI Guru Member

    I am not sure if you can do this using a router and a wet, since everything under the main router is shared under wet. Maybe you just need to define two different subnets with different dns and somehow bridge them together, or define the 2nd dns under main router...
  7. HennieM

    HennieM Network Guru Member

    Guys, WET has nothing to do with the DNS stuff. In terms of DNS, and any sort of networking in general, a WET link is not any different from a wired link, a fiber link, or no link at all. DNS is about resolving host names, not about how the network is connected.

    A way to get your secondary router into the DNS tables of your DNS server (which I reckon is your main router) might be to:

    On your main router, go to

    Basic > Static DHCP

    Now add the IP ( and DNS name (secondaryrouter.net) to the static DHCP table.
    (If you want to do it right also add the MAC address of your secondary router's LAN interface [the wired interface] in the MAC address field.)

    Hopefully now Tomato's DNS server on main router will use the entries in the static DHCP table.

Share This Page