PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Odoo Peppol DNS check failed on iso6523-actorid-upis.edelivery.tech.ec.europa.eu

When Odoo or the verification path fails on the upstream ISO6523 resolver host, it looks like every customer is wrong even though the real problem is infrastructure or resolver state.

Technical Peppol DNS failure Belgium-first Self-serve remediation
Symptoms

What this usually looks like

404 or DNS errors on iso6523-actorid-upis.edelivery.tech.ec.europa.euThe default nameserver path fails during verificationKnown-good customers suddenly look unavailable
Likely cause

What is usually actually broken

The verification chain is breaking at the resolver or upstream service layer, so Odoo cannot trust the participant lookup even when customer data is fine.

Next steps

Do these before you resend

  1. Treat the incident as resolver or infrastructure failure first, not as mass customer-data corruption.
  2. Test one known-good participant outside Odoo and compare the result.
  3. Pause bulk partner edits until the resolver path and verification host behave normally again.

The fastest path from this page is a prefilled diagnosis. It opens the analyzer with this exact issue pattern already loaded and immediately prepares the EUR 9 fix-pack preview when the route looks blocked or risky.

Open prefilled diagnosis See the fix pack
Direct help

Buy the rescue kit for this exact issue

If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.

Recent operator reports

Current public evidence for this exact failure

Odoo users tracing the failure to the upstream ISO6523 resolver host and fixing it by updating Odoo 18

r/Odoo · April 2026

Open source
FAQ

What people ask right before they get blocked

Why does this make every customer look broken?

Because the failure happens before the ERP can confirm any participant lookup, so healthy customers can all appear invalid at once.

Should I edit customer records while this is happening?

No. Infrastructure or resolver failures can mimic mass bad data, so bulk edits often make the aftermath harder to untangle.

Operator guides

Go one level deeper before you resend

Odoo Peppol triage for Belgium

A calm, ordered checklist for Belgian Odoo users when Peppol starts failing without a clear explanation.

Read the guide
When to resend a Peppol invoice and when to escalate

A fast decision guide for operators who need to know whether the next step is a resend, a partner-record fix, or a provider ticket.

Read the guide
Related issues

Similar failure patterns worth checking

Odoo suddenly says all customers are not on Peppol

If Odoo marks every customer as not on Peppol all at once, treat it as an environment or provider incident first, not a data-cleanup job on every partner record.

Open issue page