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

RT-N16 on Toastman, DNS not working

Discussion in 'Tomato Firmware' started by RobertB, Oct 18, 2012.

  1. RobertB

    RobertB Serious Server Member

    It doesn't appear that DNS is working right - I can ping out to Google DNS and other sites just fine. DNS works just fine from the PK5000. Neither clients nor the RT-N16 can utilize DNS.

    Qwest/Centurylink PK5000 on 192.168.0.1, pulling DNS from upstream
    Asus RT-N16 WAN port at a reserved 192.168.0.10, in the PK5000's DMZ
    Asus RT-N16 LAN / Wireless on 192.168.1.1 gateway

    Clients pull DHCP 192.168.1.x fine and have RT-N16 192.168.1.1 as gateway, DNS, WINS

    Most recent build of Tomato Toastman (based on 1.28, not sure the number, I am posting from work)

    Basic / Network / WAN - Route Modem IP is 0.0.0.0...should this be set to 192.168.0.1? (I can get to the modem and the router currently with no problem...what does this do, anyway?)
    Basic / Network / LAN - Static DNS of 8.8.8.8 and 8.8.4.4
    Wireless Mode is Access Point
    Advanced / DHCP/DNS - Use internal DNS checked, Use recieved DNS with user-entered DNS checked, Prevent DNS-Rebind attacks is un-checked
    Router is in router mode

    I can see where RT-N16 is getting the CenturyLink DNS servers from the PK5000 as well on the status page.

    Hopefully I've not left out anything useful to explain this, but I'm at work right now and don't have it all in front of me. I have also tried with emtpy Static DNS as well as CenturyLink DNS entries there and there was no change.
     
  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    Route Modem IP I believe is if your router has an administration page that's on a different subnet than the WAN's IP address. AT&T UVerse does this, unless you create a static route to the damn thing there' was no way to talk to it.

    What if you disable the DMZ, static route, and Google DNS on the RT-N16. Does DNS work then?
     
  3. mstombs

    mstombs Network Guru Member

    Router mode? Lots of things don't work in that why not Gateway which actually means "Nat router"
     
  4. Monk E. Boy

    Monk E. Boy Network Guru Member

    That's true, some ISP router/modems are very picky about double NAT and will refuse to send packets out that have already undergone a NAT conversion. If you can stick their router into bridge mode, so the RT-N16 can get a physical IP address instead of a NAT address, it should remove this as an issue.
     

Share This Page