domain resolving to 0.0.0.0 protected?

Discussion in 'Prevx Releases' started by m00nbl00d, Jul 11, 2011.

Thread Status:
Not open for further replies.
  1. m00nbl00d

    m00nbl00d Registered Member

    Joined:
    Jan 4, 2009
    Posts:
    6,623
    I was using a relative's computer, and I noticed that under SafeOnline protection list was a domain that my relative didn't add to SOL. That domain is being blocked access by resolving it to 0.0.0.0.

    During a search, my relative entered the website in question, but it failed because it was resolving to 0.0.0.0.

    No, it wasn't SOL doing it. It was me. But, I'm wondering why SOL added it to its protection? Odd.
     
  2. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    Could you send me a PM with the website name? I suspect it is to be expected when redirected to an address like 0.0.0.0 (or 127.0.0.1 in the case of someone serving a website locally) but I can double check on our back-end.

    Thanks!
     
  3. m00nbl00d

    m00nbl00d Registered Member

    Joined:
    Jan 4, 2009
    Posts:
    6,623
    Do you know what happened? :p
     
  4. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    It looks like this is just caused because of 0.0.0.0 being resolved to a local address which is considered to be protected. You shouldn't have any negative side effects from it.
     
Thread Status:
Not open for further replies.