Your IP:

Our Forums Have Moved!

Visit our new forums at to post on topics and read the latest content. These forums are now read-only archives.

K-12 Forums

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

Or see all states.


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.
    • CommentAuthorwstjohn
    • CommentTimeApr 22nd 2012
    I really don't understand this at all... I don't see how to make the ip addresses match... I need a step by step. thanks
    • CommentAuthorzelus
    • CommentTimeApr 22nd 2012 edited
    wstjohn, have you created a support ticket regarding the mismatch error that you're seeing? (

    Do the IP addresses seen at the following links differ in comparison to the output of running the command 'nslookup' in a terminal window/application?

    Edit: Thanks rotblitz.
    • CommentAuthorrotblitz
    • CommentTimeApr 23rd 2012
    "Do the IP addresses seen at these places differ for you?"

    Certainly not. He would have to compare with the output of:
    • CommentAuthorespencer
    • CommentTimeApr 30th 2012
    I have the same problem. "Your OpenDNS filter settings might now work due to DNS IP address and HTTP IP address mismatch."

    I have run the command "nslookup" on three computers on my home network. Two of them show the IP address being the same as the DNS IP shown in the OpenDNS Updater, but the other one shows it as being the same as the HTTP IP shown in the Updater. The IP for the internet port shown in my router manager (Netgear Smartwizard) is also the same as the HTTP IP from the Updater, which is also the IP address that I've recognized all along. The first one (DNS IP from Updater) looks new.
    • CommentAuthorrotblitz
    • CommentTimeApr 30th 2012
    In general, this is almost an ISP problem. Your ISP may route your DNS lookups down another path than your HTTP traffic. However, if this is different for computers in the same network (behind the same public IP address(es)), then it is a configuration problem on your end. Compare the outputs from different computers of:
    nslookup -type=txt
    ipconfig /all
    to possibly find out what the problem is.
    Thankful People: zelus

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