Netgear Orbi RBK50 using OpenDNS parental controls - Never Block not working for me



  • Avatar
    steedvlx600 (Edited )

    Aw C'mon... Anybody??? Anything?... at all?

    It would seem that there are black holes in the OpenDNS database... As in; There are no entries for these .mil domains.
    How can that be?

    Comment actions Permalink
  • Avatar

    I do not see a relation to OpenDNS, but the domain hasn't an A or AAAA record assigned, just TXT records:

    nslookup -type=txt
    Server:  local

    Non-authoritative answer:   text =  "MS=ms72587166"   text =  "v=spf1 -all"

    If you think it is an issue with OpenDNS, raise a support ticket, link "Submit a request" above.

    Comment actions Permalink
  • Avatar

    Thanks for the response. But, I have no idea what that means.

    The "relation to OpenDNS" is that (as stated) when I am using the OpenDNS servers, I cannot access that website nor any like them.
    When using my ISP's DNS servers, I have no problem accessing them.

    Therefore, I asked the question because it does have something to do with using the OpenDNS servers. I will look up the meaning of this A record thing. But, if my regular DNS servers can look it up, why can't OpenDNS?

    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    "I have no idea what that means."

    You'll get the idea in a second.  It means that no IP address is associated with, (i.e. no A(ddress) record configured), therefore nothing and nobody can establish a HTTP connection to this domain.  The domain owner would have to configure this A record.

    Also, something is totally wrong on your end.  Your output of "nslookup -timeout=10 -type=txt" proves that you do not have Live Parental Controls enabled on your router, but you're using normal OpenDNS Home with your IP address ( at the time when you executed the command) registered at the OpenDNS Home dashboard which should not be the case.  Your LPC dashboard is only at

    And your DNS lookup for went through two OpenDNS server addresses and a DNS server address of "1xx.24.1xx.1" which doesn't look like the Netgear router's address which is to be used with LPC or OpenDNS Home.  You should not configure any DNS server addresses with LPC, even not OpenDNS addresses, far from additional ones like "1xx.24.1xx.1".

    After all, the problems are with you, not with OpenDNS or LPC.  If you meant to be using Live Parental Controls (LPC), to get LPC working:

    "But, if my regular DNS servers can look it up, why can't OpenDNS?"

    This question is rather meaningless as long as you don't use OpenDNS or LPC or your "regular" DNS servers the way they should be used.

    And again, If you're still facing issues, raise a support ticket, link "Submit a request" above.  We other users have only limited options to help you.  Staff is in a better position.

    Comment actions Permalink

Please sign in to leave a comment.