VoIP was acting up, but now DNS won't start after changing forwarders. Where should I look?

November 16, 2026 5 answers
Asked by 3m!gimbalstaple_824

While investigating phone problems, I corrected DNS forwarders on an Active Directory server. Now users can't reach the internet, domain tools can't find the domain, and the DNS service won't start.

There are also access denied errors involving services and an endpoint security agent that's no longer showing in its management portal. How should I sort out what's related?

Answers

Tavmira.5k

Stop changing forwarders for now. A forwarder can affect external lookups, but it doesn't explain the DNS service failing to start or multiple services reporting access denied. Those need a separate investigation.

Record the current configuration and recent changes before making more edits. Check the exact DNS service error and the events immediately before and after a failed start, including application and service logs. Error 1067 by itself just says the service terminated unexpectedly. The surrounding events may give you the actual reason.

Since registry permissions were already changed, damaged permissions are worth investigating. Avoid granting Network Service access to more keys at random. Compare the affected settings with a known good configuration and get experienced Windows Server help if needed.

Reply to this answer
Rilvexa-8p

Check what DNS servers the domain controller and clients are actually using. Active Directory clients need access to DNS that can resolve the domain's internal records. Handing out only ISP DNS through DHCP may get some public lookups working, but it won't replace internal AD DNS.

If there's another healthy internal DNS server, verify it has the required domain records and that clients can reach it before relying on it. Don't remove the DNS role as a quick fix without knowing what will serve those records instead.

Reply to this answer
_q58+funnelrivet.6

Get a clear picture of the domain before trying recovery. Is this the only domain controller? What are the adapter settings, DNS addresses, replication partners, and FSMO role holders? Run dcdiag where possible and check time synchronization too.

Verify the backups and involve whoever can assist with domain recovery. A second domain controller can be useful for resilience, but promoting a new one isn't a substitute for understanding whether the existing domain and DNS are healthy enough to replicate.

Reply to this answer
m.473!sparecrayon

The security agent is a lead, not a verdict. Check its management and local logs for the decommission event and any blocked activity around the service failures. Contact the vendor for a supported repair or removal procedure, including whatever authorization it requires. Don't assume uninstalling it will restore damaged permissions.

Same goes for the licensing problem. It's worth correcting, but the information here doesn't establish that it caused the DNS or phone trouble.

Reply to this answer
3y~buttonferry_682

Once the domain outage is contained, go back to the original phone symptoms. Were calls failing to register, dropping, or just sounding bad? Those point to different checks.

Test name resolution for the phone provider, then look at connectivity and traffic through the firewall. QoS being configured doesn't prove the whole path is healthy. Check the switching and network path too, rather than assuming DNS is the cause.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions