[sf-lug] And then there were 5: SFLUG.NET, SFLUG.COM, SFLUG, ORG, SF-LUG.COM, SF-LUG.ORG: Re: SFLUG.COM Re: SFLUG.[...] Re: SFLUG.org
Rick Moen
rick at linuxmafia.com
Thu Apr 18 01:23:34 PDT 2019
Quoting Michael Paoli (Michael.Paoli at cal.berkeley.edu):
> Uhm, are we done adding domains for a while now, or ... are we gonna pick up
> yet more? SF-LUG.NET also seems available, but I don't know that Jim
> specifically suggested that ... nor up to how many domains he's willing
> to be reimbursing folks for.
Well, that's an issue going forward, isn't it? For now, I'm going to
infer a desire for slave nameservice from my two nameservers for...
> Anyway, master now available for not only sflug.org.
> but also now sflug.com. and sflug.net.:
> ns1.sf-lug.org.:
> 198.144.194.238
> 2001:470:1f04:19e::2
> Not sure where the slaves may be in the process.
> Rick - if you want to coordinate with Al, you do also have access to
> edit those zone masters:
> balug-sf-lug-v2.balug.org
[snip]
Looks like Al (I assume) has gone ahead and declared authoritative the
usual gang of nameservers:
Liten-Datamaskin:~ rick$ whois sflug.net | grep 'Name Server'
Name Server: NS.PRIMATE.NET
Name Server: NS1.LINUXMAFIA.COM
Name Server: NS1.SF-LUG.ORG
Name Server: NS1.SVLUG.ORG
Name Server: NS.PRIMATE.NET
Name Server: NS1.LINUXMAFIA.COM
Name Server: NS1.SVLUG.ORG
Name Server: NS1.SF-LUG.ORG
Liten-Datamaskin:~ rick$ whois sflug.com | grep 'Name Server'
Name Server: NS.PRIMATE.NET
Name Server: NS1.LINUXMAFIA.COM
Name Server: NS1.SF-LUG.ORG
Name Server: NS1.SVLUG.ORG
Name Server: NS.PRIMATE.NET
Name Server: NS1.LINUXMAFIA.COM
Name Server: NS1.SVLUG.ORG
Name Server: NS1.SF-LUG.ORG
Liten-Datamaskin:~ rick$
Checking at the master:
Liten-Datamaskin:~ rick$ dig -t soa sflug.net @NS1.SF-LUG.ORG +short
ns1.sflug.net. jim.well.com. 1555254673 10800 3600 1209600 86400
Liten-Datamaskin:~ rick$ dig -t soa sflug.com @NS1.SF-LUG.ORG +short
ns1.sflug.com. jim.well.com. 1555254672 10800 3600 1209600 86400
Liten-Datamaskin:~ rick$
Notice that the FQDN of the master nameserver cited in the SOA record
('ns1.sflug.net', 'ns1.sflug.com') is a mismatch compared to the
parent-zone NS record FQDN ('NS1.SF-LUG.ORG') -- but this is admittedly
a very minor problem.
Neither of these two is yet set up at my two nameservers. We'll do
that now. Adding slave nameservice on offered nameserver 1 of 2,
ns1.linuxmafia.com:
[Snip my adding two new stanzas to /etc/bind/named.conf.local. Then:]
linuxmafia:/etc/bind# rndc reconfig
linuxmafia:/etc/bind# dig -t soa sflug.net @ns1.linuxmafia.com +short
ns1.sflug.net. jim.well.com. 1555254673 10800 3600 1209600 86400
linuxmafia:/etc/bind# dig -t soa sflug.com @ns1.linuxmafia.com +short
ns1.sflug.com. jim.well.com. 1555254672 10800 3600 1209600 86400
linuxmafia:/etc/bind#
Confirmed functional.
Moving on to configurating slave nameservice on offered nameserver
2 of 2, ns1.svlug.org, where it's NSD rather than BIND
rick at gruyere:~$ sudo su -
[sudo] password for rick:
root at gruyere:~ # cd /etc/nsd3
root at gruyere:/etc/nsd3
[Snip my adding two new stanzas to /etc/nsd3/nsd.conf. Then:]
root at gruyere:/etc/nsd3 # nsdc restart
root at gruyere:/etc/nsd3 # nsd-xfer -z sflug.net -f secondary/sflug.net.zone 198.144.194.238
[1555575378] nsd-xfer[23460]: info: send AXFR query to 198.144.194.238 for sflug.net.
root at gruyere:/etc/nsd3 # nsd-xfer -z sflug.com -f secondary/sflug.com.zone 198.144.194.238
[1555575396] nsd-xfer[23467]: info: send AXFR query to 198.144.194.238 for sflug.com.
root at gruyere:/etc/nsd3 # chown nsd:nsd secondary/sflug.net.zone secondary/sflug.com.zone
root at gruyere:/etc/nsd3 # nsdc rebuild
root at gruyere:/etc/nsd3 # dig -t soa sflug.net @ns1.svlug.org +short
ns1.sflug.net. jim.well.com. 1555254673 10800 3600 1209600 86400
root at gruyere:/etc/nsd3 # dig -t soa sflug.com @ns1.svlug.org +short
ns1.sflug.com. jim.well.com. 1555254672 10800 3600 1209600 86400
root at gruyere:/etc/nsd3 #
Confirmed functional.
You'll bug Aaron Porter about adding slave nameservice for sflug.net and
sflug.com to ns.primate.net, right? It's not serving those, yet.
AFAIK, I'm done as to my part(s).
More information about the sf-lug
mailing list