Configuring iMac works, configuring airport extreme doesn't

Comments

12 comments

  • Avatar
    littlejon1

    Also, the airport extreme is now running in bridged mode as I just got switched to google fiber. Not sure if they are rerouting things. But they shouldn't be since it works when configured on my iMac. 

  • Avatar
    littlejon1

    And, in case anyone asks, yes, I have followed the airport extreme setup instructions at: https://store.opendns.com/setup/device/apple-airport-v761 and flushed the cache. 

  • Avatar
    rotblitz

    "the airport extreme is now running in bridged mode"

    This is the reason why it doesn't work.

  • Avatar
    nkmower

    I have the same problem, but I'm definitely not in bridge mode.  OpenDNS works at the Mac level, but not on the Airport Extreme level.  I also followed all the instructions (as far as I know).

  • Avatar
    rotblitz

    So you configured your Airport Extreme as of https://support.opendns.com/entries/42422810 ?
    Then post a screen shot of your AE here where you configured the OpenDNS resolver addresses.

  • Avatar
    Alexander Harrison

    After checking the configuration instructions for the AirPort, also consult Scenario 3 at https://support.opendns.com/entries/39861294-OpenDNS-is-Only-Working-on-One-or-Some-of-my-Computers-Devices for possible computer-level configuration conflicts. 

  • Avatar
    nkmower

    Here is how I have my Airport Extreme setup.  I'll check out the link Alexander shared.

     




    Screenshot 2014-09-17 15.53.00.png
  • Avatar
    rotblitz

    Can you please post the complete plain text output of the following diagnostic command:

       nslookup -type=txt debug.opendns.com.

  • Avatar
    Alexander Harrison

    Do you have another router on-network at 172.27.35.1? Also check each AirPort Utility tabs and confirm that this router is not in Bridge Mode. Also include the output to nslookup -type=txt debug.opendns.com. from above. 

  • Avatar
    nkmower

    Hi rotblitz, here is the text output of nslookup -type=txt debug.opendns.com.

     You know, Alexander, I don't have another router, but I just realized my Ooma internet phone device sits between my cable modem and my Airport extreme.  This is probably the device at 172.27.35.1.  Maybe this is the problem.

    Last login: Tue Sep 16 21:06:28 on ttys000

    NRM-Macbook-Pro-Retina:~ nkmower$ nslookup -type=txt debug.opendns.com

    Server: 208.67.222.222

    Address: 208.67.222.222#53

     

    Non-authoritative answer:

    debug.opendns.com text = "server 9.sea"

    debug.opendns.com text = "flags 20 0 2F6 7E00400014C3"

    debug.opendns.com text = "originid 24695045"

    debug.opendns.com text = "actype 2"

    debug.opendns.com text = "bundle 6566097"

    debug.opendns.com text = "source 98.145.148.19:55156"

     

    Authoritative answers can be found from:

     

    NRM-Macbook-Pro-Retina:~ nkmower$    nslookup -type=txt debug.opendns.com.

    Server: 208.67.222.222

    Address: 208.67.222.222#53

     

    Non-authoritative answer:

    debug.opendns.com text = "server 11.sea"

    debug.opendns.com text = "flags 20 0 2F6 7E00400014C3"

    debug.opendns.com text = "originid 24695045"

    debug.opendns.com text = "actype 2"

    debug.opendns.com text = "bundle 6566097"

    debug.opendns.com text = "source 98.145.148.19:57606"

     

    Authoritative answers can be found from:

     

    NRM-Macbook-Pro-Retina:~ nkmower$ 

    NRM-Macbook-Pro-Retina:~ nkmower$ 

     

  • Avatar
    rotblitz

    "I don't have another router, ..."

    Wrong, you seem to have one.   Your cable modem is apparently a router (NAT device) unless your ISP assigns you a private RFC-1918 IP address and the cable modem works in bridged mode.  The latter is rather unlikely, they wouldn't assign a gateway-like address of 172.27.35.1.

    "but I just realized my Ooma internet phone device sits between my cable modem and my Airport extreme."

    Your "Ooma internet phone device" may not be visible at all and may have no impact.

    "This is probably the device at 172.27.35.1."

    No, this is the LAN facing (private) IP address of your cable modem.  And the 172.27.35.27 is the WAN facing (private) IP address of your AE.

    Regarding your nslookup output, you're using the OpenDNS data center in Seattle, and your public IP address 98.145.148.19 is registered with OpenDNS network ID 24695045.

    It looks like you have configured the OpenDNS resolver addresses on the computer too when you executed the command.  You said it works with this scenario.  Can you execute the same command again when you have configured the OpenDNS resolver addresses on the router alone, to reflect the right scenario for your issue?

  • Avatar
    Alexander Harrison

    Can you also add in the results from "nslookup -timeout=10 myip.opendns.com." This would be what the Updater sees and would try to update. It seems that your OpenDNS setup is working without issue for your external IP of 98.145.148.19, but the IP checker for the Updater client (the command above) is returning an incorrect IP. You'd be able to use OpenDNS without issue, but IP updates may be delayed due to this issue with the Updater. The Updater will not update to the 172.X address, so you should be able to ignore the error when it appears due to something upstream of your network device. 172.x IP addresses are often used by larger managed networks because they have more private IPs than 192.168.x IPs.  

Please sign in to leave a comment.