Skip to content

Latest commit

 

History

History
14 lines (10 loc) · 881 Bytes

tq-010-SOAs-and-NSes-for-possibly-censored-domain.md

File metadata and controls

14 lines (10 loc) · 881 Bytes
Raw

tq-010 SOAs and NSes for possibly-censored domain

When a domain is suspected to be censored by a resolver it is interesting to capture the resolver’s opinion on NS and SOA records for the domain and every parent domain up to TLD1. E.g. login.vk.com needs SOA and NS requests for at least login.vk.com and vk.com.

1: It may be easier to query all the domains up to the root as TLD definition is non trivial. See public suffix list for inspiration.

TBD: it’s unclear if SOA and NS records for some well-known subdomain are of use or not.

Examples

  • Italy, one ISP was transparent about login.vk.com blocking announcing the ISP in SOA Resource Record for vk.com
  • Russia, Omsk, one ISP was blocking youtube.com with an admin@ email address in SOA record