4 ms·
Rule #1: Domain registrar and DNS should never be the same source. Rule #2: See Rule #1 Rule #3: https://www.gov.uk/guidance/protect-domains-that-dont-send-em
by dazc 4y ago
Rule #1: Domain registrar and DNS should never be the same source.
Rule #2: See Rule #1
Rule #3: https://www.gov.uk/guidance/protect-domains-that-dont-send-email https://www.gov.uk/guidance/protect-domains-that-dont-send-e...
- somehnguy 4y agoLaziness wing again! I’ve been meaning to move my domains from Namecheap to Cloudflare for no reason other than I switched to Cloudflare DNS years ago. Turns out I was just following best practices :) Side note so this comment isn’t completely devoid of info: in the 10+ years I’ve had domains at Namecheap I’ve never had so much as a hiccup. Highly recommend them as a registrar.
- netsectoday 4y ago> Rule #1: Domain registrar and DNS should never be the same source. The domain registrar POINTS to whatever DNS servers, so in this attack the registrar just POINTED to their own DNS servers. Rule #1 and Rule #2 were followed but the domain was still taken over. The attacked domain also needs to send email so the gov.uk link is great guidance but can't be followed here.
- agwa 4y ago> Rule #1: Domain registrar and DNS should never be the same source. But why? A compromise of either service leads to a domain takeover (although recovering from a DNS compromise is easier than recovering from a registrar compromise) so you're doubling your risk exposure if you follow this rule.
- dazc 4y agoRecovering one service from one source is a lot easier than recovering two at the same time from one single source.