[dns-operations] Oddball DNS servers for tplinkdns.com

[Mark Andrews]

> On 3 Apr 2018, at 12:17 am, wbrown at e1b.org wrote:
> 
> Viktor wrote on 03/30/2018 02:13:10 PM:
> 
>> This looks like a DNS implementation that cuts a few too many corners...
> 
> And not likely to care as long as it is doing what they need/expect.

Well at the moment the servers are returning addresses for
ns1.tplinkdns.com and ns2.tplinkdns.com which differ from those
in the com zone and those servers don’t answer for tplinkdns.com.

ns1.tplinkdns.com.	172800	IN	A	52.204.177.89
ns2.tplinkdns.com.	172800	IN	A	54.87.217.253

			vs

ns1.tplinkdns.com.	811	IN	A	80.217.70.196
ns2.tplinkdns.com.	797	IN	A	49.207.84.148

If basic delegation checks were being performed as REQUIRED by
RFC 1035 such errors would be cleaned up even if it requires temporary
removal of the delegation to get the delegatee to pay attention.

Operational error like this are SUPPOSED to result in temporary
removal of the delegation if they are not FIXED.  See RFC 1033.

We just need TLDs (and similar) and their agents to follow what is already 
described instead of taking the attitude that anything is permitted.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka at isc.org