Spent 45 minutes trying to fix a DNS issue that was just a loose cable

I was troubleshooting a client's server that couldn't resolve any domain names - checked DNS settings, flushed cache, even rebuilt the config file. Turns out the ethernet cable from the modem had wiggled loose about a millimeter and was causing intermittent drops. Has anyone else wasted a huge chunk of their day on something that dumb?

3 comments

3 Comments

rosep8711d ago

DNS is actually the modem issue you described, not the cable. DNS stands for Domain Name System, and a loose cable is a physical layer problem.

max_ramirez4811d ago

Ha exactly, some people get too caught up in the technical definitions. You're right that it's all about the end result though.

leep8911d ago

Oh man, @rosep87 is actually being super specific about the OSI model there, but you're still right about the dumb tax we pay. DNS issues and cable problems both end up making you chase your tail for way too long. I once spent an hour thinking my router was dying because the power brick was barely plugged in. The worst part is when you finally find the loose cable you feel relieved but also want to punch something for wasting that time. Loose cables are the sneakiest because they look connected but they're not.