Post #1041990

2026-03-15 14:06 UTC

Homelabbing question: what is the danger of having your home IP address exposed as a DNS entry? Like does it attract more hackers attention that way? How many people are exposing their services directly from the home network? Reposts are welcome :)

Replies (4)

@andnull@social.nouveau.community 2026-03-15 14:15

@portaloffreedom@social.linux.pizza Watching this thread intently

Open ##2434674
@foxyloon@blimps.xyz 2026-03-15 14:34

@portaloffreedom@social.linux.pizza Usually all that happens is the login page of your homelab router/firewall is presented to the web. In theory, this could be an attack vector if hardening of the router isn't performed. I.E. leaving the default login credentials in use. That's before all the data scraping and pen-test bots start hitting said web interface of the router, which might cause performance degradation due to the sheer volume of traffic trying to connect and gain access. Definitely routinely comb through the logs and blacklist problematic IPs.

Open ##2434675
@tedmielczarek@mastodon.social 2026-03-15 15:29

@portaloffreedom@social.linux.pizza I keep all of my home services out of reach of the public internet and access them via tailscale.

Open ##2434676
@atax1a@infosec.exchange 2026-03-17 19:37

@portaloffreedom@social.linux.pizza we expose our mailserver and a webserver from our home, on a static IP, with proper rDNS and have to deploy the same protections (greylisting on the smtpd, freebsd blocklistd for ssh, and a custom HTTP binding to blocklistd to catch scanners) as we do for cloud stuff. highly recommend The Book of Pf as a tutorial for secure network design even if you end up using iptables — the advice downthread to silo the exposed stuff into a DMZ is also how we run things. @andnull@social.nouveau.community

Open ##2434678