jhart at kevla.org
Tue Feb 28 20:25:26 EST 2012
Well, it seems that my domain dropped off the face of the planet this morning.
No internet connectivity on any of my machines, and hence email was dead as
well. Wife stated that the Verizon FIOS router was operating "normally". So,
I assumed my server was having issues, and once I got home this evening
started looking into the problem.
Looked through the log files, but everything looked ok. However, couldn't
ping anything outside the FIOS router.
So, I rebooted the FIOS router, and that gave me internet connectivity back. I
could send emails, but was unable still to receive emails or visit my "domain"
from my smartphone (still dead to the world).
Again, very carefully reviewed all services and logs on the server, and
rebooted it and looked at all logs as it finished starting services, and
everything looked fine.
Something told me "LOG INTO THE STUPID FIOS ROUTER AND CHECK IT", so I did.
Port forwarding looked like it still had the correct settings. Eventually
made my way to the "Advanced" tab and looked at the 'Dynamic DNS' section. Lo
and behold it is reporting DYNDNS as in "error" condition. Went to update it
and the dang router picked that exact moment to reboot. Once it came back up
I updated the username/pwd for dyndns again and within 10 minutes I had
service restored to my domain.
I had power issues last night, lost an entire leg and Dominion dug a 2x2x3
foot hole in my yard to fix. I turned everything off, and everything came
back up fine and I had connectivity at 0715 this morning. Not sure what
happened after that.
Lesson learned: Dominion has great service, and Verizon equipment still sux...
> Guess the test worked, depending on what it was trying to do.
> On 2/28/12, Jay Hart <jhart at kevla.org> wrote:
>> Novalug mailing list
>> Novalug at calypso.tux.org
More information about the Novalug