![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
В «NCSC Advisory on Ongoing DNS Hijacking Campaign» дается совет:
if operating your own DNS infrastructure, consider robust change control processes to manage any changes to your zone file. Ideally you should use a DNS zone file that is managed through a version control system, such as git. This will provide a backup of your DNS records, allow change-auditing and easy rollback. Enforce levels of organisational approval which is monitored before changes are made.
[...]
if you operate a critical domain, consider monitoring for domain transfers, WHOIS data changes, and nameserver changes.
А я ещё с 2000 года держал зоны tomsk.ru, tomsk.su и остальные в CVS, и мониторил изменения в базе RIPN, посылая каждые 2 часа whois-запрос и сравнивая с результатом last known good запроса.
Я молодец?
if operating your own DNS infrastructure, consider robust change control processes to manage any changes to your zone file. Ideally you should use a DNS zone file that is managed through a version control system, such as git. This will provide a backup of your DNS records, allow change-auditing and easy rollback. Enforce levels of organisational approval which is monitored before changes are made.
[...]
if you operate a critical domain, consider monitoring for domain transfers, WHOIS data changes, and nameserver changes.
А я ещё с 2000 года держал зоны tomsk.ru, tomsk.su и остальные в CVS, и мониторил изменения в базе RIPN, посылая каждые 2 часа whois-запрос и сравнивая с результатом last known good запроса.
Я молодец?