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.

OpenDNS services: No CacheCheck results for DFW, LAX, and MIA

Bottom of Page

1 to 12 of 12

  1.  
    • CommentAuthoreri3k
    • CommentTimeJun 29th 2009 edited
     permalink
    I see on the system status page that OpenDNS has added Dallas, Los Angeles, and Miami locations since I last visited. However, the new locations do not show up in CacheCheck results. Are there plans to add these three locations to the CacheCheck?

    I frequently use the CacheCheck feature to determine the IP addresses resolved for CDN URLs in different parts of the country. If OpenDNS is not already planning on adding the new locations, please consider this a request to do so.

    Thanks for providing a great service.
  2.  permalink
    If they are listed on Cachecheck it's very likely they are in testing and will be open soon.. don't see why those locations would be showing up otherwise..
  3.  permalink
    I only see them listed on System Status currently here..
    I'm Guessing they will make an annoucement on the blog when they are fully up and running.. although system status is showing them as up and running.. nslookup -type=txt which.opendns.com 208.67.222.222 is still showing 4.ash for me at work right now and I'm guessing if Miami was up I would be moved to Miami. although work Internet is via AT&T which shows the IP location as atlanta instead of Gainesville,FL so that could play into it as well. I havent checked from home on Cox yet..
  4.  permalink
    I'm sure they will be added to CacheCheck as fast as they can get to it. I'd wager that bringing the new locations up has kept OpenDNS quite busy. They are also headed for Amsterdam, and are still working on getting a location closer to Asia, according to the last blog post in mid June.
    • CommentAuthorrotblitz
    • CommentTimeJun 29th 2009 edited
     permalink
    @eri3k
    I'm curious too what OpenDNS will come back with.

    However, you can check your OpenDNS location's cache yourself:
    "nslookup -type=txt which.opendns.com." will return the server location you are using.
    "nslookup DomainName.TLD." will return the result from OpenDNS, similar to the one on the cache check page.
    Do another nslookup on the IP address to see if it's not in fact NXDOMAIN or SERVFAIL.

    You can put this into a .BAT or .CMD script, which you can simply double-click:

    @echo off
    setlocal
    echo.
    (set /p domain=Enter Domain: )
    if not defined domain goto exit
    echo.
    echo OpenDNS Server Location:
    nslookup -type=txt -timeout=5 which.opendns.com.|find """"
    echo.
    for /f "tokens=2" %%a in ('nslookup -timeout^=5 %domain%.^|findstr/b "Address"') do set IP=%%a
    if defined IP set IP=%IP:,=%
    echo Returned IP address for %domain%: %IP%
    echo.
    nslookup -timeout=5 %IP%
    :exit
    endlocal
    pause
  6.  permalink
    @rotblitz Batch file doesnt seem to work, not a biggy just thought I'd Try it

    Below are the results I get.. it gives the addresses for our DNS server here that is forwarding to OpenDNS.. instead of Google.com Addresses...

    Enter Domain:
    OpenDNS Server Location:
    "4.ash"

    Returned IP address for google.com: 192.168.0.4

    Server: xxxx.xxxx.local
    Address: 192.168.0.4

    Name: xxxx.xxxx.local
    Address: 192.168.0.4

    Press any key to continue . . .
    • CommentAuthorrotblitz
    • CommentTimeJun 29th 2009 edited
     permalink
    Funny, this was a quicky just off-hand, rather a model only, tested on my desktop...
    I only tested with a domain, which returns ONE IP address, Google returns more. I will see how I can improve it.

    Edit: The script has been updated to reflect multiple returned IP addresses. It just takes the first one returned.
    • CommentAuthoreri3k
    • CommentTimeJun 30th 2009 edited
     permalink
    Thank you, guys. I really appreciate your responses.

    Not that it matters, but I probably was not very clear on how I use CacheCheck. Typically I use the service to ensure that a URL on a content delivery network is resolving to different IP addresses for each OpenDNS location (e.g., cdn.netflix.com). If I am helping someone in Virginia who is having difficulty streaming video from Netflix, I need to know that OpenDNS's DC location is resolving IP addresses for the Netflix servers in DC rather than the ones in Los Angeles. The results of nslookup from my location are not particularly helpful in this case, and CacheCheck is just the right tool for the job.
  9.  permalink
    I'm not sure, but I don't think those locations have been listed as long as the history of green check marks suggests. But now, we all wait with much anticipation... :bigsmile: :cool:
    • CommentAuthorrotblitz
    • CommentTimeJun 30th 2009
     permalink
    "I need to know that OpenDNS's DC location is resolving IP addresses".
    This is possible too, you need to use the real IP address of the related OpenDNS server location instead of the well known four Anycast IP addresses.
    nslookup domain.tld. <LocalODNSipAddress>
    How to obtain the real IP addresses? Thats the art!
    • CommentAuthoreri3k
    • CommentTimeJun 30th 2009 edited
     permalink
    @rotblitz
    Fortunately, that level of art is within my ability: 4.ash is at 208.69.32.14 and 3.pao (which I use) is at 208.67.219.13. Unfortunately, all local OpenDNS servers appear configured to listen for queries from only other OpenDNS IP addresses. Please feel free to correct me if I've got it wrong.
    • CommentAuthorrotblitz
    • CommentTimeJun 30th 2009
     permalink
    Confirmed, they do not listen on port 53. :sad:
    Thanks for pointing this out. I didn't test it before.
    Not sure if there is any other method. For now I ran out of ideas.

1 to 12 of 12

  1.  

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