trouble with DNS forwarding & Linksys RV082

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by tadr, Apr 13, 2006.

  1. tadr

    tadr Network Guru Member

    I have a Linksys RV082 setup load balancing two WAN connections.

    WAN1: T1 (static IP, static DNS servers)
    WAN2: Cable Modem (static IP on the Cable gateway, which provides an internal IP to the RV082)

    For some reason, I am having trouble with DNS queries on connected clients. The RV082 is and is performing DHCP. The DNS server on the client side is picked up as, which I assume then forwards requests to the appropriate WAN DNS server. Unfortunately, this doesn't seem to be working properly.

    1. Accessing a domain name causes about a 3 second pause while it is looking up "whatever".com, the page will then load.
    2. nslookup returns:

    DNS request timed out.
    timeout was 2 seconds.
    DNS request timed out.
    timeout was 2 seconds.
    *** Request to timed-out

    Any ideas? this is driving me nuts! Thanks!
  2. TazUk

    TazUk Network Guru Member

    On the DHCP config page you can specify the DNS servers that are given out, try entering your ISP's DNS servers there and see if it's any better.
  3. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Haven't noticed this as I run domain controllers on the networks which naturally are the DNS for the LAN. But in the case of using ISPs DNS servers, try entering the DNS from the secondary WANs ISP into the DHCP you'd have 4x DNS servers being handed out...2x from the first WAN ISP, 2x from the second WAN ISP.
  4. cmoglia

    cmoglia Guest

    I have seen this with a few of my RV016 routers on workstations that use the linksys as the DNS.
    It can also be seen if you go to System Maintenance and try to perform a DNS lookup within the router. The web page try to perform the DNS lookup, but goes into a loop and finally times out without resolving the address.
    Rebooting the router fixes the issue but I think there is definitly something wrong within the firmware.
    I have firmware 2.10 and still see the issue occur.
  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