# DNSSEC problems

**URL:** <https://forum.virtualmin.com/t/dnssec-problems/116540>\
**Category:** Virtualmin\
**Created:** [August 17, 2022, 3:21pm UTC](https://forum.virtualmin.com/t/dnssec-problems/116540 "2022-08-17T15:21:11Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![fakemoth](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/fakemoth/32/244_2.png) [@fakemoth](https://forum.virtualmin.com/u/fakemoth)\
**Post date:** [August 18, 2022, 7:21pm UTC](https://forum.virtualmin.com/t/dnssec-problems/116540/7 "2022-08-18T19:21:09Z")

</div>

I do not agree, not completely. It has some quirks as I also posted here [DNSSEC keys changed after modiying DNS and Sender Policy Framework options - #3 by Ilia](https://forum.virtualmin.com/t/dnssec-keys-changed-after-modiying-dns-and-sender-policy-framework-options/114358/3) , but it is still usable. Could use some love though, yeah, but something like DNSSEC shouldn’t be simply dropped. Still not doing that even for good technical reasons: for a personal domain rather than dropping DNSSEC not working with nsupdate and dynamic IP (trying to end up with some local servers from home on the internet), I rather hooked a direct FO over a few houses between my home servers and the public servers, and transported a static IP.

For the moment yeah, it is stopped for my main domains, but only for convenience because I rebuilt everything; I am doing that every 3-5 years or so. Don’t know why, it is in my blood or something…

---

_[View the full topic](https://forum.virtualmin.com/t/dnssec-problems/116540)._