Something really a Baby Gap

Thu 24 Jul 2008, 07:40 PM by Jay Kastner
I was listening to All Things Considered (NPR) on my way home tonight. That's course of habit when it's possible to leave work before 7:00 PM.

So tonight's story was about a gardener that involved, of course, Texass.

Anyway, the person responsible for this story made a comment that led me to the following questions:

1. Why are good but unexplainable events so commonly refered to as miracles?
2. What's the opposite of a miracle?
3. What's the difference between a miracle and "a random event with a positive outcome"?
4. Is it just easier to place the "miracle" label on things we can't explain?
5. Doesn't the Catholic church have a specific definition of a miracle? I believe for sainthood consideration, it's necessary to have been the source of a miracle. True?

P.S. If you answered number two with "George Bush", not only are you right, but you also get an eHug.

Wed 23 Jul 2008, 01:25 PM by Jay Kastner
So it looks like one of my wishes came true...
Thu 17 Jul 2008, 10:18 PM by Jay Kastner

ok, how about this: "alright kids, it's time for bed. Go get your sneakers on."

Sun 13 Jul 2008, 01:40 PM by Jay Kastner
"...the people who are impressed by it are not very tech savvy. They just bought into the marketing hype."

Sat 12 Jul 2008, 04:41 PM by Jay Kastner
Sun 6 Jul 2008, 08:43 PM by Jay Kastner
Several people e-mailed me about problems accessing the following sites:

The server was up and this was not a connection issues. Rather, it was a DNS issue. I battled this for about a week and had to "help" my registrar/DNS service. Everything is working properly now, but you might find this conversation interesting...

Thanks for your mail.
There is nothing wrong at our end. We tried accessing all your sub domain site and there is no problem.
This may be just an isolated incident or you may wish to check with your local ISP regarding access issues.
Let us know if you require further assistance.

Hi. Thanks for the update. Could you please run the following check on your end:
1. Do an nslookup of "" using your primary DNS server.
2. Do the same nslookup using your secondary DNS server.
You will see that the secondary works, while the primary does not.

Hi Jay,
Upon further investigation, we found the problem to be due to the MX setting for "googlee81a3317314bf313".
It was configured to point to "". The starting "." caused a problem to our DNS server and caused the primary to not load the dns entries properly.
I have removed the starting "." so that host googlee81a3317314bf313 points to "".
You may wish to change this if this is not the correct address.
Your subdomains should start resolving properly in a few hours after the propagation is complete. Thanks.