I am trying to block social media and news websites on my local machine (Windows 7).

I added the below lines into my hosts file: www.thatstamil.com www.facebook.com

In that way Facebook is successfully blocked. But thatstamil.com is still accessible. How do I block this site?

  • Try putting in and
    – StBlade
    Jul 30, 2015 at 11:21
  • @StBlade added and reboot my machine, but still its accessible. :-(
    – Butterfly
    Jul 30, 2015 at 11:27
  • 2
    @StBlade You can't use the HOSTS file to redirect one IP address to another IP address. You can just say if there's a request for url.com to go to the new IP address, Jul 30, 2015 at 18:00

4 Answers 4


Try removing the www. Just: thatstamil.com tamil.oneindia.com facebook.com
  • its working fantastic :-)
    – Butterfly
    Jul 30, 2015 at 12:05

If you put in www.thatstamil.com, but are accessing thatstamil.com, the latter is not the same fully qualified domain name (fqdn) as www.thatstamil.com. Try using the following: www.thatstamil.com thatstamil.com
  • No, I tried all the compinations www.thatstamil.com thatstamil.com www.tamil.oneindia.com tamil.oneindia.com
    – Butterfly
    Jul 30, 2015 at 11:57
  • facebook successfully blocked, and other site was also blocked successfully. Only this thatstamil.com is not able to block
    – Butterfly
    Jul 30, 2015 at 11:57
  • 3
    Putting in IP addresses, such as, shouldn't help, since the system won't consult the file to look up up an IP address. Perhaps there is some DNS caching factor making a difference. You can flush the cache by issuing the command ipconfig /flushdns at an administrator command prompt. If you use Chrome, you can use the instructions in How to Clear the Google Chrome DNS cache on Windows. Have you tried a different browser on the system to see if the issue is browser-specific? Also try a reboot.
    – moonpoint
    Jul 30, 2015 at 12:52

Try to block tamil.oneindia.com instead of thatstamil.

  • I tried it too..
    – Butterfly
    Jul 30, 2015 at 11:08

Some versions of Firefox have their own DNS resolver and/or caching, which can cause configuration changes to the DNS resolver built into the OS to have a only a delayed effect or even no effect at all.

Not the answer you're looking for? Browse other questions tagged or ask your own question.