discuss: who is responsible for the tldp.org domain name
Subject:
Re: [discuss] Re: who is responsible for the tldp.org domain name
From:
Rick Moen ####@####.####
Date:
7 Nov 2008 23:16:17 +0000
Message-Id: <20081107231518.GZ5561@linuxmafia.com>
Quoting Guylhem Aznar ####@####.####
> Bad idea. If it isn't broken, don't touch it. Admins are meant to be
> contacted ! The UNC DNS team is usually very responsive. Just ask
> them to change the IP br.tldp.org is pointing to, and voila.
I concur. Just say "Dear hostmasters, please replace
br IN A 200.140.247.68
...with...
br IN A 1.2.3.4
...in the zonefile for tldp.org, at your earliest convenience. Thank
you."
(Substituting the desired IP for 1.2.3.4.)
> I wouldn't consider using Gandi or any commercial DNS service.
Nor should, I would maintain, any moderately competent Linux user who
has a static IP. Please note: This is an observating I'm making about
people generally; it doesn't have much to do with LDP. (Even people on
broadband or dialup with dynamic IP will benefit from doing _recursive_
DNS locally. In fact, they especially benefit from doing so, more than
others.)
> If it's done in-house, yes. But the overhead of managing our own DNS
> servers on gabber is hardly justified IMHO.
Truth to tell, running secondary (slave) nameservice requires really
zero administration and maintenance. You just define the zone, and it
automatically tracks what the master does. There's nothing to
administer.
However, if "gabber" is in the same network as UNC's nameservers, it'd
be pretty foolish to use it as an additional secondary, as it is subject
to the same single points of failure, and thus adds no real redundancy.
I keep having to re-learn: People who don't understand DNS tend to have
a lot of very peculiar opinions about it!
