Milambar
16-07-2009, 07:32
This is more of a rant, than anything, but, I'd also like to know what actually happened here, so anyone knows what actually happened here, feel free to chip in.
Last night I decided to move some devices on my network around. Having done so, and having made and tested a new shortened series of cat5e cables (to avoid spaghetti junction), I powered down the modem and router waited 2 minutes, powered up the modem, waited for it to stablize, then powered up the router...
No internet. So I rechecked the cables with a cable tester. They were fine. Did the power down, power up thing again...
Still no internet. So I took the router out, and conencted directly. Powered everything down, then back up again...
Still no internet. But I did notice a curious thing, I could actually access sites if I knew their ip. Thankfully my day job is in networking, so I actually have quite a few of these memorized like any good nerd.
I put the router back into the equation and instead of letting it get the dns servers from dhcp, I explicitly specified the openDNS ones. Worked a charm, everything popped back onto the internet.
It appears I wasted a good hour and half diagnosing this, thinking I'd made an error in my own LAN networking, when, for some reason VM's nameservers appear to have dropped off the face of the earth, at least for me. The odd thing is, if I specify them by IP (194.168.4.100 I believe), they work fine too, but if I leave DHCP to configure them, they don't.
So, whats happened here? Other than me getting very fustrated. Why did the DNS not automatically configure itself as it normally does?
Last night I decided to move some devices on my network around. Having done so, and having made and tested a new shortened series of cat5e cables (to avoid spaghetti junction), I powered down the modem and router waited 2 minutes, powered up the modem, waited for it to stablize, then powered up the router...
No internet. So I rechecked the cables with a cable tester. They were fine. Did the power down, power up thing again...
Still no internet. So I took the router out, and conencted directly. Powered everything down, then back up again...
Still no internet. But I did notice a curious thing, I could actually access sites if I knew their ip. Thankfully my day job is in networking, so I actually have quite a few of these memorized like any good nerd.
I put the router back into the equation and instead of letting it get the dns servers from dhcp, I explicitly specified the openDNS ones. Worked a charm, everything popped back onto the internet.
It appears I wasted a good hour and half diagnosing this, thinking I'd made an error in my own LAN networking, when, for some reason VM's nameservers appear to have dropped off the face of the earth, at least for me. The odd thing is, if I specify them by IP (194.168.4.100 I believe), they work fine too, but if I leave DHCP to configure them, they don't.
So, whats happened here? Other than me getting very fustrated. Why did the DNS not automatically configure itself as it normally does?