I can buy plan for a year on a discount,
but i can also do without.
because a script can updates ip to a storj’s node, localy on my pc.
So i need auto updating IP, coz my ISP changes IP’s,
But i can also just type raw ip every time it changes to confg.yaml by my script.
I wonder is setting a raw ip for storj’s node a benefit or a downside?
Like is it bad practice? like making things easier for some attacks?
is it good, coz makes latency faster to my node?
my concern is mostly is it better to “hide” nodes ip behind a domain name from DDNS for security reasons idk.
Whats Your knowledge?
Thanks.
i don’t think there’s a significant security concern. attackers scan entire IP blocks, regardless if there is a domain name associated with them.
the DDNS is a convenience. use it with something like ddclient to keep it updated with your external IP. If your ISP changes your IP address after a router reboot, you may not even know it. Having it auto update with your domain name keeps things running.
there are also free DDNS services where you don’t even have to buy a domain name (you use their top level domain). Personally I pay the $10 a year or whatever for a custom domain from porkbun, because I thought it was cute, and host it with cloudflare, which is free.
Satellite is resolving the node IP for clients, so from client perspective there is no difference.
If DDNS is reliable — I would use it, even if you have static IP, for simplifying failover scenarios, and to provide TTL: ip does not have TTL so it will be up to satellite how to cache it. With DNS you can specify TTL.
Each my container that runs a node also runs inadyn, so regardless of how container is connected (directly, vpn, or LTE) DDNS is always correct within one minute. Literally setup a home server, installed a node, drove it across the county and plugged in. It “just worked”
You can use cloudflare DDNS on your domain for free, and cloudflare is quite reliable. I would not pay for DDNS.
TLDR — no difference in security, but much easier to manage, raw IP addresses best be avoid.
And restart the node? Seems excessive: extra scripts, extra restarts, all for no benefit.
Just don’t use crappy ddns providers, like DuckDNS and others
excessive as F, but i can avoid DNS failure, i have used several free DDNS service before, and when it fails it F’up the node online stats, so rather to pay for reiable like $9,99/Year to cover all my nodes, or just to save it and use raw ip with scripts no porblem at all, i guess i will save that 10$ then, thx!
Sure. But you are replacing a hypothetical dns failure (whichI experienced none so far) with hypothetical failure of your scripts and extra complexity and limitations (I.e. does it handle failover?)
On the other hand if you have already spent time setting it up and stabilizing and it works - no reason to change a thing.
Some domain registrars include a free DDNS service, for instance Namecheap or Strato. The router manufacturer AVM includes DDNS (Myfritz) for their devices.
Oh yes, that’s how I use CloudFlare — I host my domains there, and use inadyn to update A records.
The amount of value CloudFlare provides on a free account is beyond comprehension. I’ll be gladly paying for these services (zero trust, cache, dns, hosting, etc) and yet they are entirely free. Mind boggling.