Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

This discussion has been inactive for longer than 30 days, and is thus closed.

Domain Name System (DNS) troubles: PC remembers old Qwest default resolver

Bottom of Page

1 to 10 of 10

  1.  
  1.  permalink
    Hi - I have configured my router (ActionTEC GT701) to use OpenDNS IPs, and have restarted it. The router's status shows that it is using OpenDNS IPs for DNS.

    My PC, however, is less than cooperative. My PC (Windows XP Pro) is a DHCP client. I need to get DNS server from DHCP server, since the PC also works on a domain at work, so I can't hard code OpenDNS IPs for DNS, or none of my work access will work. No sweat though, so I check the "Obtain DNS server addresses automatically" in the TCP/IP properties control panel.

    When I open a command window and type "nslookup", I get the following:

    C:\>nslookup
    *** Can't find server name for address 192.168.0.1: No response from server
    Default Server: resolver.qwest.net
    Address: 205.171.3.65

    >

    There is NO Qwest software on the laptop. The only thing I can find is a registry entry where it is remembering the old Qwest DNS server IP. The registry entry is:

    HKLM/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/DhcpNameServer, which is set to "192.168.0.1 205.171.3.65". Can I just remove the 205.171.3.65 from the registry entry, or is there a more "proper" way to get my computer to forget the old Qwest entry?

    I've also tried putting a '192.168.0.1 router' entry in my C\Windows\System32\Drivers\etc/hosts file, but that doesn't seem to help.

    Thanks!

    Peter

    petergregory@yahoo.com
    • CommentAuthorpencoyd
    • CommentTimeJul 9th 2007
     permalink
    Very strange. I'm tentative when it comes to editing the registry (I'm on a Mac, so less experience), but you certainly seem to have found the likely candidate.

    John
    • CommentAuthorahoier
    • CommentTimeJul 9th 2007
     permalink
    Have you gone into Control Panel > network connections and checked out all of your adapters? None of them are set to the qwest DNS IPs?
  4.  permalink
    Thank you pencoyd and ahoier for responding!

    No network connection (incl alternate or advanced panes) include any Qwest DNS IPs.

    I removed the Qwest IP addr from the registry, and rebooted. The address STILL came up. Makes me wonder if the router is passing it through. I will have to fire up Ethereal (ahem, Wireshark) and see what's in the DHCP response from the router. I'll report on that.

    Thanks again!
  5.  permalink
    Hi again, I just did a trace (Ethereal) of the DHCP dialog between my PC and the router. The router is configured ONLY with OpenDNS's two IP addresses for DNS. And yet, it still says that the two DNS IPs are: 192.168.0.1 (the router itself) and 205.171.3.65 (Qwest).

    I double-checked the router (Actiontec GT701). Nowhere in its configuration ANYWHERE is Qwest's DNS seen. It must be stored in its cache and delivers it in DHCP requests. Grrrrrrr. :devil:

    Looks like I might have to write some registry scripts to change the DNS back and forth between home and work..... :tongue:
    • CommentAuthorpencoyd
    • CommentTimeJul 9th 2007
     permalink
    Pesky router!
  7.  permalink
    I have the same router/modem (ActionTEK GT701) and Qwest is my ISP. I'm not real smart when it comes to this stuff, but I seem to be having the same problem. In the DHCP setup for the router, the DNS servers are set to OpenDNS's IP addresses and "Static".

    Unfortunately I'm getting the "Oops" message when I check the status using http://welcome.opendns.com.

    I contacted Qwest and they said they are not blocking this functionality.

    I really want to employ Adult Site Blocking through the router rather than having to mess with each individual PC on my home network.

    Does anybody have any suggestions for me? Were you able to resolve the original issue in this thread?
  8.  permalink
    I had this problem too, and after some digging and experimenting I've found a workaround.
    This only seems to affect Qwest users using the gt701, and that's because the Actiontec modem supplied by Qwest has different firmware than the standard Actiontec. Changing the dns from the web interface just doesn't work right on the Qwest model, so you'll have to use the following method. Keep in mind that every time you restart your modem or have a power outage, etc. you have to do this all over again.
    Open the DOS command window, and type

    telnet 192.168.0.1

    you'll now be prompted for your username (Administrator, unless you've changed it).
    Then you'll be asked for your modem password. Being that you are now basically working in linux, you won't see your password as you type it. If you got the right password, you're now inside your router's operating system.
    Now type
    cd etc; ls
    and a list of files will be displayed. Make sure you have one called resolv.conf
    now type
    cat > resolv.conf
    you'll notice the cursor will change somewhat
    now type
    nameserver 208.67.222.222
    and then hit enter
    now type
    nameserver 208.67.220.220
    and hit enter
    now hold control and hit d to save the file
    now type
    exit
    and you should get a message saying connection to host lost. now you're back in DOS. Next, type
    ipconfig /flushdns
    and then close the DOS window.
    opendns will probably still give you the oops page for about 4 more hours, but after that everything will work fine and you'll be able to block sites etc in the dashboard, you'll just have to do this procedure every time you restart the modem.
    Thankful People: j8048188
    • CommentAuthorpencoyd
    • CommentTimeJan 6th 2008
     permalink
    ipconfig /flushdns

    or

    ipconfig /release
    and
    ipconfig /renew
    • CommentAuthorchampro
    • CommentTimeJan 8th 2008 edited
     permalink
    Thanks a bunch! I used this same procedure on my Actiontec GT704. Verizon recently forced their DNS on us and changing it in the modem web interface did nothing. :cry: It's crazy that I had to login into the Linux (BusyBox) core of the router just to change that setting.

    Now I'm back to good, fast OpenDNS. :smile:

1 to 10 of 10

  1.  

This discussion has been inactive for longer than 30 days, and is thus closed.