Re: squirting spray foam into the crack at the bottom of the BAW

2010/3/16 Dean Anderson <[email protected]>:
> Name some that don't support TCP.

Off the top of my head: b.ns.yp.to, ns1.msft.net, a.ns.spamhaus.org,
m.root-servers.net

Try the following queries, and then try them again with +vc:

dig -t a cr.yp.to @b.ns.yp.to
dig -t a www.microsoft.com @ns1.msft.net
dig -t a 1.2.3.4.zen.spamhaus.org @a.ns.spamhaus.org
dig -t a www.google.com @m.root-servers.net

> You are aware the the IETF is now moving to make TCP required,

They're moving to require *software support* for TCP.  They're not
requiring operators to support TCP.

> *Public service dns operators are:  root, TLD and ccTLD operators.

Not all root or TLD servers support TCP.  Here's a list of TLD zones
and their name servers (from the root zone file) that respond to a SOA
request over UDP but fail over TCP:

AD. DINIS.AD. DNS2.AD. DNS3.AD. DNS4.AD.
AW. NS1.SETARNET.AW. NS2.SETARNET.AW.
CAT. DNS4.AD.
CN. A.DNS.CN. B.DNS.CN. NS.CERNET.NET.
ET. NS1.TELECOM.NET.ET. NS2.TELECOM.NET.ET.
IR. NS1.NIC.IR.
KW. DNS1.KW. DNS2.KW. DNS3.KW.
LK. NS-C.NIC.LK. NS-L.NIC.LK. NS-T.NIC.LK.
MA. NS1.IAM.NET.MA. NS2.IAM.NET.MA. NS3.IAM.NET.MA.
MN. NS1.MAGIC.MN.
MO. UMACSN1.UMAC.MO. UMACSN2.UMAC.MO. UMACSS1.UMAC.MO.
UMACSS2.UMAC.MO. UMACSS3.UMAC.MO.
MV. NS.DHIVEHINET.NET.MV. NS2.DHIVEHINET.NET.MV.
NC. PYTHON.OPT.NC. TRITON.OPT.NC.
NP. SHIKHAR.MOS.COM.NP.
OM. OM14.OMANTEL.NET.OM.
PA. NS.NIC.PA. NS.PA.
PK. M-2.PKNIC.NET.PK.
TK. ROOT-A.TALOHA.TK. ROOT-C.TALOHA.TK. ROOT-D.TALOHA.TK.
ROOT-E.TALOHA.TK. ROOT-G.TALOHA.TK.
VN. B.DNS-SERVERS.VN.
VU. SANTO.VANUATU.COM.VU.
ZW. NS1.TELONE.CO.ZW. NS2.TELONE.CO.ZW.

I don't think there are any public zones that have *no* TCP access,
but that's hardly to say that every public zone name server supports
TCP.