public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Running HTTP and DNS on same machine
Date: Wed, 17 Aug 2011 23:43:13 +0200	[thread overview]
Message-ID: <2005305.NAJv4TkKfY@nazgul> (raw)
In-Reply-To: <4E4C310D.9010408@badapple.net>

On Wed 17 August 2011 14:22:21 kashani did opine thusly:
> On 8/17/2011 2:08 PM, Alan McKinnon wrote:
> > On Wed 17 August 2011 13:56:10 Grant did opine thusly:
> >> I currently use a free service to host the DNS records for my
> >> website, but I'm thinking of running a DNS server on the same
> >> machine that runs my website instead.  Would that be fairly
> >> trivial to set up and maintain?  If so, which package should
> >> I use?> 
> > The first question is Why?
> > 
> > There's no real benefit, it's a huge amount of work for little
> > gain, you carry the cost of increased traffic yourself, and if
> > that host goes blip, you not only lose access to the web server
> > but to the entire zone as well.
> > 
> > Technically there's no good reason why you can't co-host web and
> > dns. However, depending on your upper level domain and
> > registrar, TWO dns servers may be a requirement (this is the
> > norm) and you propose only one. Where's the second one going to
> > be? Only one is a very bad idea indeed.
> > 
> > Your last two questions reveal that this is not something you
> > are
> > familiar with already, so I highly recommend you investigate
> > everything thoroughly and fully understand just what you are
> > letting yourself in for before deciding.
> > 
> > If you simply don't like your current DNS provider, then finding
> > a different one you do like is quite simple.
> 
> Exactly what Alan said. It's not worth it and no registar will let
> you do it on one IP.

I'm just itching to type up the long list of horror stories I've 
stored from people doing their own DNS thinking it was real easy.

But there's this little thing called an NDA and it says I can't :-(

Truly though, the devastation from DNS mistakes is horrendous. 
The primary error folk make is this:

You do not configure and treat the DNS service like any other service.
You do not USE the internet to maintain dns, as dns BUILDS the 
internet. 

It's a subtle distinction but a vital one.

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2011-08-17 21:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 20:56 [gentoo-user] Running HTTP and DNS on same machine Grant
2011-08-17 21:08 ` Alan McKinnon
2011-08-17 21:22   ` kashani
2011-08-17 21:43     ` Alan McKinnon [this message]
2011-08-17 22:08       ` kashani
2011-08-17 22:51         ` Alan McKinnon
2011-08-18  0:50           ` Peter Humphrey
2011-08-17 21:49   ` Grant
2011-08-17 22:09     ` Alan McKinnon
2011-08-17 21:23 ` Michael Mol
2011-08-17 21:53   ` Alan McKinnon
2011-08-18  1:35     ` Michael Mol
2011-08-18 18:17       ` Florian Philipp
2011-08-18 18:36         ` Michael Mol
2011-08-19  7:17           ` Alan McKinnon
2011-08-17 23:51 ` Paul Hartman
2011-08-18  0:18   ` Adam Carter
2011-08-18  0:40     ` kashani
2011-08-18  1:56     ` Grant
2011-08-18 17:26     ` Jarry
2011-08-18 17:39       ` Michael Mol
2011-08-18 18:22       ` Grant
2011-08-18 18:38         ` Michael Mol
2011-08-18 18:47         ` Jarry
2011-08-18 21:48     ` Stroller
2011-08-18  0:35   ` Pandu Poluan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2005305.NAJv4TkKfY@nazgul \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox