IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

Windows DNS Resolution Issues After VPN Switch or Network Change

Estimated time

10-20 min

Editorial Intro (SEO-Aligned)

This troubleshooting guide is aligned to the exact query "certificate expired internal website" and focuses on enterprise-safe remediation for Windows DNS Client.

Severity: MediumUser SafeEnv: WindowsWindowsWindows DNS Client

Author & Verification

Tamem J

IT Solutions Engineer

Last verified: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

Tested on Windows 11 23H2Tested on Windows 10 22H2

Trust Signals

No ratings yet

0 total helpfulness votes

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)

Symptoms of certificate expired internal website

  • Websites or internal hostnames fail to resolve after network/VPN changes.
  • Some sites open by IP address but not by hostname.
  • Issue may improve temporarily after reconnecting.

Likely Causes of certificate expired internal website

  • DNS cache contains stale records from prior network/VPN state.
  • Adapter DNS servers are incorrect or not refreshed.
  • VPN split-DNS policy or resolver order issue.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: certificate expired internal website

Accordion runbook sections

  1. 1

    Confirm scope, user impact, and reproduction

    Info
    v

    Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

  2. 2

    Validate prerequisites and application/session state

    Info
    v

    Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

  3. 3

    Run safe diagnostics from the Commands section

    Command
    v

    Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

  4. 4

    Apply safe remediation steps

    Info
    v
    • Identify whether only internal names fail, only external names fail, or both.
    • Reconnect the affected network/VPN and retest using the same hostname.
    • Use approved DNS cache flush and adapter renew steps if documented for your environment.
    • Attach DNS server/resolution output to the ticket before escalation.
  5. 5

    Escalate when access, policy, or security controls are involved

    WarningAdmin required
    v
    • VPN split-DNS policy or name server assignment appears wrong.
    • Issue affects multiple users after a VPN or DHCP/DNS change.
    • Network engineering review is required.

Commands

Copyable diagnostic or remediation commands (1 snippet).

DNS resolver and cache checks (Windows)

CMD

ipconfig /all
nslookup microsoft.com
ipconfig /displaydns | more

When to Contact IT / Security

  • VPN split-DNS policy or name server assignment appears wrong.
  • Issue affects multiple users after a VPN or DHCP/DNS change.
  • Network engineering review is required.

Recommended Partners for This Topic

Selected from your affiliate registry based on this article's category, product family, and tags.

Disclosure: Active partner links may generate commission with no additional user cost.

Was this helpful?

Your response is stored locally in this browser for demo analytics.