[sf-lug] would __LOVE__ to set up a DNS server on ...

Michael Paoli Michael.Paoli at cal.berkeley.edu
Thu Aug 20 16:12:55 PDT 2015

Well, essential data bits (zone data dumped, compressed and uuencoded)
from (aformentioned unadvertised not NS delegated) slave is a bit
further below (some clients and/or list software may convert that
to "attachments" and/or discard such - but at least for the time
being it's relatively easy to grab again.  "Of course" that slave
is still pointing at the old/former (now defunct) master IPv4 address.

So, to set it up, just need some Linux (or Unix or BSD) host,
DNS server software (if not already present), and add the suitable
configuration bits.  That's pretty much it.  Zone data, as mentioned,
provided and thus far available, the rest of the configuration is quite
straight-forward and should work with most any reasonably sane DNS server
software (they'll pretty much all use the RFC standard zone format data
files - can't think of any worth bothering with that wouldn't handle such).

So, that in place, bump ("increase" per the RFCs) of serial number,
get slaves repointed to new master, get upstream delegation NS, and any
relevant "glue" records updated, then you're off 'n running (for the DNS
part, anyway).

The actual zone files on the (very recently defunct, also quite backed up,
recently former) master, has additional useful metadata, e.g. comments
for slave out-of-band contact information, various bits which may not be
100% suitable for full public disclosure - and there's also RCS version
history information available on said master (and its backups) too. Not
putting that full data here, for aforementioned reason(s) (possible
confidentiality, etc.), but that is available on "vicki" (notably the sflug
VM on "vicki"), and its backups thereof.  But that's not *essential* to get
you up 'n going with DNS *now*.  For the moment, you just need the other
bits I mentioned (host to run it on, static IPv4 address, DNS server software,
zone data, update DNS data and bump serial number, including notifying
slaves of new master, and updating upstream (registry) DNS NS records and
any relevant glue records) ... then the DNS bit is done!

Data, data ...

$ dig @ -t AXFR sf-lug.org. | gzip -9 | uuencode sf-lug.org.gz
begin 600 sf-lug.org.gz
M'XL(`$5;UE4"`[622T_"0!#'S^VGF,0+B$QVMEV at +2&2B(\+*ACU6LI2:[HM
J;!(;8BOA9+TI0J!EE.NI at 9J2QH2Q-$`7,%D5E>$PJMOV)XTL:C$N`P``
$ dig @ -t AXFR sf-lug.com. | gzip -9 | uuencode sf-lug.com.gz
begin 600 sf-lug.com.gz

> From: jim <jim at well.com>
> Subject: Re: [sf-lug] SF-LUG ... have to copy the web site files to  
> some other host ... DNS ...
> Date: Thu, 20 Aug 2015 20:27:55 +0000

>     I would __LOVE__ to set up a DNS
> server on the host.
> On 08/20/2015 05:06 PM, Michael Paoli wrote:
>> Well, I've got backups ... just need a place you want to land the
>> data/files.
>> You'll also need DNS server and the zone files - which are also in backups
>> I have ... or alternatively one can suck most or all that data from  
>> any slave,
>> at least short of the data expiring - may not be able to do zone pull from
>> slave(s), though ... actually, there's one (unlisted non-NS) slave you
>> can pull the zones from any IP: (*not* a high availability
>> site - that sits on my personal laptop - that may also go away as  
>> slave if it can't pull any newer authoritative data that's found).
>> Be sure you don't do anything problematic with zone serial numbers on
>> DNS, or the data may not properly propagate for quite a long while (until
>> zone expiration, which is ... 2 weeks on those SF-LUG zones.
>>> From: jim <jim at well.com>
>>> Subject: Re: "vicki", [www.]sf-lug.{org,com} down, ... (SF-LUG  
>>> list remains up: http://linuxmafia.com/mailman/listinfo/sf-lug)
>>> Date: Thu, 20 Aug 2015 16:40:00 +0000
>>>    I'll also have to copy the web site files to
>>> some other host and repoint the DNS data.

More information about the sf-lug mailing list