What people keep running into with infrastructure
Complaints tagged infrastructure, each raised by more than one person. One-off posts are not included.
12 recurring problems · 61 people · 13 forums we read
Raised more than once
Most people first.
- 11How to keep hostnames and IPs when migrating domain controllersUpgrading domain controllers requires deciding whether to reuse the old name and IP after demotion or clean up metadata and DNS. While the process is mind-numbing and laborious, it lets you maintain the same hostnames and IPs during the migration.
- 9Why are cloud bills so unexpectedly high?Public cloud infrastructure locks teams into ecosystems with severe exit barriers and unpredicted bills from resource overruns. This dynamic leaves companies trapped with massive, uncontrollable hosting costs that can suddenly spike by hundreds of thousands of dollars.
- 9How to identify unknown plumbing parts in a buildingUnfamiliar plumbing components near a main drain or water line are difficult to recognize without professional blueprints, leaving buyers and owners unsure if an installation is a standard backflow valve or a failing system that requires immediate replacement. This uncertainty stalls property purchases and prevents safe maintenance decisions until an expert can visually inspect the setup.
- 8Doing senior IT work alone on helpdesk payCarrying total responsibility for critical business infrastructure without adequate staffing or backup systems leaves solo administrators drowning in infrastructure demands while making entry-level wages. This mismatch between heavy system-wide ownership and insufficient pay or experience creates constant burnout and drives people to feel trapped between loyalty to coworkers and the stress of the job.
- 6How do you manage DCIM and IPAM data in a GitOps workflow?Infrastructure-as-code workflows break down when engineers have to account for unexpected manual changes and configuration drift. Introducing a new machine or changing an existing IP address manually forces teams to constantly chase and patch out-of-sync environments.
- 4How to manage remote IT infrastructure without a dedicated teamManaging IT security and processes across a globally distributed team without local staff leads to overwhelming operational chaos. It prevents small businesses from establishing unified security workflows, leaving sensitive information vulnerable and leadership buried in disjointed administrative tasks.
- 3How to build an IT department from scratch aloneAs the first IT hire, you get overwhelmed trying to balance daily firefighting with long-term strategy while fixing every workflow problem in sight. Falling into this trap expands your scope so uncontrollably that basic user complaints go unattended and core infrastructure gets neglected.
- 3Server randomly rebooting with no error logs or dumpsMost unexpected server reboots trigger blank Kernel-Power 41 events with zero bugcheck parameters and leave management controller logs completely silent. Because these hard resets generate no minidumps or error entries, troubleshooting hits a dead end until underlying hardware issues like a failing UPS are identified.
- 3How to handle being the only IT person at a companyRunning legacy systems solo forces you into an endless loop of firefighting daily distractions like broken printers and lockouts, leaving zero time to fix root problems. This constant operational chaos creates permanent 24/7 on-call stress and makes major projects feel impossible to tackle alone.
- 2Why is public transit so packed during rush hour?Overcrowded buses and cancelled trains make peak-hour commuting suffocating and unreliable. When vehicles fill to the point where passengers can barely breathe and missing one means a long wait, getting anywhere becomes an exhausting ordeal.
- 2How to get WiFi across a large RV parkLarge outdoor properties struggle with reliable coverage because large vehicles like 40-foot fifth wheels frequently park directly between access points and block the signal. This makes maintaining a steady connection across dozens of acres a major headache that requires careful planning beyond just buying standard gear.
- 2How to manage internal DNS without running a domain controllerRetaining traditional domain controllers solely for local network name resolution creates unnecessary complexity and overhead for on-prem environments. This leaves administrators struggling to manually sync records across multiple sites when hardware or legacy servers are phased out.
Comes up alongside
Topics that keep appearing on the same problems — not topics with similar names.