Nice writeup...creating a "blocklist" with /etc/hostsjml401 wrote: ↑Fri Apr 26, 2019 12:11 am I've created my first post on this forum to help out the OP regarding this issue. I've dealt with this for some time and finally got frustrated enough to tinker with the Personal Cloud's file system. Essentially, we will prevent the DNS queries to these five sites by redirecting them on the Personal Cloud instead of using the pi-hole.
Seagate Personal Cloud runs a form of ARM Unix architecture. Which means it has it's own hosts file which we can edit to redirect the repeated DNS queries to the 5 addresses you listed - I got the same ones too! First and foremost, we need to connect to the Personal Cloud via SSH. If you don't have this enabled in your settings on the Personal Cloud, please do so. After you connect via SSH, follow the commands below:
1: Edit hosts file by typing the following command (without quotes) "sudo vi /etc/hosts" and hit enter
2. Enter your user password to the Personal cloud and hit enter
3. Edit the file to include the following lines (you may want to read up on how to edit text files in vi to figure out how to insert or replace text):
127.0.0.1 localhost localhost.localdomain
192.168.***.*** PersonalCloud *your own local IP address of the Personal Cloud
4. Type ":wq" (without quotes) and then hit enter to save and exit vi and get back to the command line
5. Lock the file so no changes can be made to the file by typing "sudo chattr +i /etc/hosts" and hit enter. (If you have to modify the file, you can reverse this by typing "sudo chattr -i /etc/hosts" instead).
6. Type "exit" and hit enter to end the SSH session
7. Reboot the Seagate Personal Cloud via it's own interface
8. Enjoy the lack of repeated DNS queries to the above sites!
Hope the above information is helpful.
I prefer nano..but vi or vim is just as good
Oh and but a cool walkaround for bad sites (TONS OF EM)