[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] One server and secondary DNS



Rodolfo Paiz wrote:

> Whoa, Jeff...

Okay <smile>.

> I think we may have a tiny little communications error here, and it's at
> least mostly my fault for failing to make clear some of the basic
> assumptions I made upon reading the earlier post. So, let me soothe the
> waters here...
> 
> I am getting a cable modem put into my home. Here, my wife and I (and my
> seven computers, my only children) will share the domain "indahaus.com" for
> the sake of my personal entertainment. I bought my Qube to do everything it
> normally does, since my house is wired for 100Mbps Ethernet, whole-house
> audio, and voice-command home automation and I wanted to run Internet access
> and services through one box. (And I didn't want to use Win2K...)

Yes, I did presume you were referring to a commercial environment.

> This (or close) is the environment to which I thought the earlier post
> referred. Everything I've written here is consistent with this level of
> informality, and offers no quality-of-service concerns under those
> constraints. DNS on a cable modem is a perfectly reasonable solution when
> the worst thing that can happen is that my wife and I get our email bounced
> to our other addresses and our friends can't check my thoughts on SETI@home
> progress.
> 
> > You're being extremely short-sighted.
> 
> Jeff, I can only think that this comment refers to your opinion of
> implementing my suggestion in a commercial environment (any kind of serious
> environment, in fact). However, should I be wrong, please do comment in more
> detail; no one here should take offense to constructive criticism.

Yes, it does.

> > How much do you know about the Internet?  How much do you know about
> > DNS?  Enough to be dangerous?
> 
> Well, I've been using the Net since 1989, and I've been running businesses
> on it since 1995. However, I'd say none of us really is or can be "expert"
> on anything that changes so damn fast. And my entire focus is
> entrepreneurial; anything I do on a technical level, I do as a hobby and on
> my own time. This should be kept in mind.

Yes, I agree, I should not have said what I did had I known you were
talking about your own noncommercial domain.

> Of course, all of us know "enough to be dangerous." After all, it is well
> said that nothing is more dangerous than an idiot with initiative. And boy,
> do I have initiative...  :)
> 
> > I care.  My customers care.  They like knowing that in the unlikely
> > event their website goes down people won't be told it doesn't exist.
> 
> Of course you care! And anyone with enough sense to grab his/her genitals in
> case of barbed wire also cares. I'll just repeat that I assumed that the
> other user was in a case similar to mine, and didn't clearly state either
> that assumption or my actual situation.
> 
> I agree entirely with your general perspective. It just didn't apply to me
> at the time of my writing, and I was remiss in not being explicit so that
> others would not misunderstand.

While I now understand your point of view, I'd still put DNS for
personal domains on other servers, and not host it myself, if possible. 
And since there are places that host DNS for free, it's easily
possible.  I don't remember the names of the free DNS hosters, so I hope
someone else will jump in here.

I do apologize for any of the misunderstanding that was my fault.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
nobaloney.net
P. O. Box 52672
Riverside, CA  92517
voice: (909) 787-8589  *  fax: (909) 782-0205