[sf-lug] sf-lug.org DNS

[Rick Moen]

Might as well look at SF-LUG's other domain.

1.  Where are the authoritative servers, as per the public "whois"?

$ whois sf-lug.org | grep "Name Server"
Name Server:NS41.WORLDNIC.COM
Name Server:NS42.WORLDNIC.COM
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
$


2.  Where the parent zone (org)'s nameservers?

$ dig -t ns org. +short
c0.org.afilias-nst.info.
b2.org.afilias-nst.org.
a0.org.afilias-nst.info.
d0.org.afilias-nst.org.
b0.org.afilias-nst.org.
a2.org.afilias-nst.info.
$


What does one of those parent-zone nameservers say, if you ask it about
the location of sf-lug.org's namesevers?

$ dig -t ns sf-lug.org. @d0.org.afilias-nst.org.       
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25836
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; AUTHORITY SECTION:
sf-lug.org.             86400   IN      NS      ns41.worldnic.com.
sf-lug.org.             86400   IN      NS      ns42.worldnic.com.
$

(As noted, the .org top-level domain people, Public Interest Registry,
are currently issuing subtly wrong responses, as the above should have
been returned in the "Answer Section", not the "Authority Section".  If
curious, compare what the "com" top-level domain's nameservers return
concerning the .com domain of your choosing.[1])


3.  Last, what do SF-LUG's nameservers, thus identified, say about the
domain's NS, SOA, and key A records?

 $ dig -t ns sf-lug.org @ns41.worldnic.com +short
ns42.worldnic.com.
ns41.worldnic.com.

$ dig -t ns sf-lug.org @ns42.worldnic.com +short
ns41.worldnic.com.
ns42.worldnic.com.

 $ dig -t soa sf-lug.org @ns41.worldnic.com +short
NS41.WORLDNIC.COM. namehost.WORLDNIC.COM. 109012019 10800 3600 604800
3600

$ dig -t soa sf-lug.org @ns42.worldnic.com +short
NS41.WORLDNIC.COM. namehost.WORLDNIC.COM. 109012019 10800 3600 604800
3600

$ dig www.sf-lug.org @ns41.worldnic.com +short
208.69.41.175

$ dig www.sf-lug.org @ns42.worldnic.com +short
208.69.41.175



This all appears to be correct and satisfactory -- with the exception of
the administrative error of trying to get by with only two authoritative
nameservers.

(I am curious about why SF-LUG isn't doing authoritative DNS on its own
machine for its primary domain.)




[1] E.g.:

$ dig -t ns com. +short
i.gtld-servers.net.
m.gtld-servers.net.
l.gtld-servers.net.
h.gtld-servers.net.
g.gtld-servers.net.
k.gtld-servers.net.
j.gtld-servers.net.
a.gtld-servers.net.
c.gtld-servers.net.
e.gtld-servers.net.
b.gtld-servers.net.
d.gtld-servers.net.
f.gtld-servers.net.

$ dig -t ns linuxmafia.com. @i.gtld-servers.net. +short
ns.primate.net.
ns.tx.primate.net.
ns1.linuxmafia.com.
ns1.thecoop.net.
ns2.linuxmafia.com.


(Or, repeating the preceding command without "+short", to also see
section headers, flags, and information outside the "Answer Section":)

$ dig -t ns linuxmafia.com. @i.gtld-servers.net.
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19525
;; flags: qr rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 6

;; ANSWER SECTION:
linuxmafia.com.         172800  IN      NS      ns.primate.net.
linuxmafia.com.         172800  IN      NS      ns.tx.primate.net.
linuxmafia.com.         172800  IN      NS      ns1.linuxmafia.com.
linuxmafia.com.         172800  IN      NS      ns1.thecoop.net.
linuxmafia.com.         172800  IN      NS      ns2.linuxmafia.com.

;; ADDITIONAL SECTION:
ns.primate.net.         172800  IN      A       198.144.194.12
ns.primate.net.         172800  IN      AAAA    2001:470:1f00:ffff::6b7
ns.tx.primate.net.      172800  IN      A       72.249.38.88
ns1.linuxmafia.com.     172800  IN      A       198.144.195.186
ns1.thecoop.net.        172800  IN      A       66.220.20.163
ns2.linuxmafia.com.     172800  IN      A       63.193.123.122
$