# Unbound getting random SERVFAIL for any domain

**URL:** https://discourse.pi-hole.net/t/unbound-getting-random-servfail-for-any-domain/65761
**Category:** Help
**Created:** [October 20, 2023, 5:46pm UTC](https://discourse.pi-hole.net/t/unbound-getting-random-servfail-for-any-domain/65761 "2023-10-20T17:46:57Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)
#### Post date: [October 21, 2023, 9:47am UTC](https://discourse.pi-hole.net/t/unbound-getting-random-servfail-for-any-domain/65761/4 "2023-10-21T09:47:12Z")

</div>

Domain-specific failures are often related to maintenance work on the domain servers authoritative for that domain, or a switch of the domain's digital signatures (as used by DNSSEC validating resolvers like unbound), or sometimes misconfigurations.  
Those kind of failures usually get sorted quickly by the domain's maintainers, i.e. they don't last for long.

DNSSEC also relies on correct time information, so if your host's clock would be off by too much, consequently DNSSEC validation and thus DNS resolution would fail. However, that may not quite match your observation, as that would affect all DNS requests alike, until time is in sync again.

---

_[View the full topic](https://discourse.pi-hole.net/t/unbound-getting-random-servfail-for-any-domain/65761)._
