News for hackers. Stuff that matters.
Re:DNS Is for People – Not for IT Infrastructure by louwrentius on Thursday June 04, 2026 @01:32AM (#48394395)
Tell me please what the problem is exactly
Re:DNS Is for People – Not for IT Infrastructure by JackSlateur on Thursday June 04, 2026 @03:31AM (#48395360)
Please describe how you plan to use ansible to deploy config in ~200k containers, with hundreds of data updates per day
Re:DNS Is for People – Not for IT Infrastructure by louwrentius on Thursday June 04, 2026 @07:03AM (#48396908)
I would not use containers in the first place as this adds added complexity and overhead in the first place.
Re:DNS Is for People – Not for IT Infrastructure by JackSlateur on Thursday June 04, 2026 @08:43AM (#48397840)
Please share how to manage ~200k applications without containers
Re:DNS Is for People – Not for IT Infrastructure by throwway120385 on Thursday June 04, 2026 @04:15PM (#48404019)
The real "fish out of water" question is "tell me how to use Ansible to configure 200k embedded appliances where the end customer doesn't always allow firmware updates through their firewall?"
Re:DNS Is for People – Not for IT Infrastructure by kassner on Thursday June 04, 2026 @05:02PM (#48404594)
Ansible will be terrible slow to update things if you're geographically far from the servers. Updating around 100 servers from another continent already takes longer than a 5 minute TTL. Parallel connections only work up to a point before a playbook run always have at least one failure and requires a re-run.

Ansible also does not have locks or parallel users coordination, so you’ll need a single user/VM/GHA workflow running the playbook or at some point concurrent users will start overriding each other.