As Aleron Ives said, the server wasn't down -- Google's DNS just wouldn't resolve sylverant.net, as it seems to like to do from time to time. Unfortunately, sometimes when this happens, I don't find out about it for a while to try to take action to appease whatever stupid crap in the Google DNS code seems to dislike.
Because of this, I suggest to people that they don't use Google's DNS (8.8.8.8 or 8.8.4.4), but rather use a different DNS server such as the ones that most people's ISPs provide or one of the various public DNS servers out there (here's a list that seems fairly up-to-date as of right now:
https://www.lifewire.com/free-and-publi ... rs-2626062 ).
That said, unlike most times, I can't completely blame this one on Google's DNS. It actually appears this time that the registrar that sylverant.net is registered through was actually returning invalid DNSSEC responses (as opposed to what normally happens when Google is the only one that thinks it is returning invalid responses).