F5F Stay Refreshed Power Users Networks Dynamic DNS

Dynamic DNS

Dynamic DNS

S
SoulRawr
Member
191
08-15-2025, 04:36 PM
#1
Hi, I see you're setting up a web server on your Raspberry Pi using noip.com via a BT Business router. Before you connect, it's good to check if there are any potential security concerns for your network devices. Make sure your router is updated, use strong passwords, and consider enabling a firewall if available. Also, ensure noip.com is trusted and secure for your use case.
S
SoulRawr
08-15-2025, 04:36 PM #1

Hi, I see you're setting up a web server on your Raspberry Pi using noip.com via a BT Business router. Before you connect, it's good to check if there are any potential security concerns for your network devices. Make sure your router is updated, use strong passwords, and consider enabling a firewall if available. Also, ensure noip.com is trusted and secure for your use case.

I
i0cean
Member
218
08-23-2025, 01:16 AM
#2
Always be cautious when connecting devices to the internet. Keep your passwords secure and avoid outdated software versions. You can explore more details at https://www.cvedetails.com if you wish.
I
i0cean
08-23-2025, 01:16 AM #2

Always be cautious when connecting devices to the internet. Keep your passwords secure and avoid outdated software versions. You can explore more details at https://www.cvedetails.com if you wish.

D
DriveIn
Senior Member
739
08-30-2025, 06:32 AM
#3
Varies based on setup, here are key recommendations. (Searching online will yield countless guides.) Place the web service in a DMZ to limit risk. (Only this server is affected, not the whole network.) Use virtualization tools like QEMU because Raspberry Pi virtualization is challenging. (In case of breach, only the VM is impacted.) Only run essential services. Disable anything unnecessary. Avoid default configurations—no extra accounts, weak passwords, hidden files. Enable logging for all services and review logs regularly.
D
DriveIn
08-30-2025, 06:32 AM #3

Varies based on setup, here are key recommendations. (Searching online will yield countless guides.) Place the web service in a DMZ to limit risk. (Only this server is affected, not the whole network.) Use virtualization tools like QEMU because Raspberry Pi virtualization is challenging. (In case of breach, only the VM is impacted.) Only run essential services. Disable anything unnecessary. Avoid default configurations—no extra accounts, weak passwords, hidden files. Enable logging for all services and review logs regularly.