Docs typo: Preprod proof-server URL `lace-proof-pub.preprod.midnight.network` returns NXDOMAIN

Technical Questions
1

markdown

Hi team — just a quick documentation correction report.

## Issue

The official environments docs page lists this URL for the Preprod proof server:

> https://docs.midnight.network/relnotes/network

| Service | URL listed |
|---|---|
| Proof server | `https://lace-proof-pub.preprod.midnight.network` |

However, this hostname does not resolve:

$ getent hosts lace-proof-pub.preprod.midnight.network (no output — NXDOMAIN)

$ curl -v https://lace-proof-pub.preprod.midnight.network/

  • Could not resolve host: lace-proof-pub.preprod.midnight.network

## Working URL found

The actual working Preprod proof-server URL appears to follow the same naming convention as the indexer/RPC hosts:

$ getent hosts proof-server.preprod.midnight.network 34.250.71.107 proof-server.preprod.midnight.network 63.34.190.149 proof-server.preprod.midnight.network 34.250.60.195 proof-server.preprod.midnight.network


Three IPs behind what looks like an AWS ALB — clearly a live, production endpoint.

## Cross-environment DNS check

For reference, here is the DNS state across all three environments:

| Environment | `proof-server.<env>.midnight.network` | `lace-proof-pub.<env>.midnight.network` |
|---|---|---|
| Preview | ✅ resolves | ✅ resolves |
| Preprod | ✅ resolves | ❌ NXDOMAIN |
| Mainnet | ❌ NXDOMAIN | ❌ NXDOMAIN |

So Preview keeps both hostnames (presumably for backwards compatibility), but Preprod only exposes the new naming. The docs were likely not updated when the rename happened.

## Suggested action

Update the Preprod row in https://docs.midnight.network/relnotes/network to:

> `https://proof-server.preprod.midnight.network`

This blocked me for a few hours while migrating a project from Preview to Preprod, so a docs fix would help future builders save time.

(For context, I'm the same builder who posted #1190 about the Mainnet 1016 issue. Migrating to Preprod for now while waiting for guidance on Mainnet.)

Thanks!
2

@takuya have the docs been updated from Lace? this is a Lace issue something we don’t any visibility. wondering if you received any updates from them.

3

Thanks @norm — and no, I haven’t heard anything from Lace directly; I don’t have a channel to them.

Good news though: this is already resolved on my side, and the fix doesn’t actually need Lace.

The lace-proof-pub.preprod.midnight.network host in the docs is just the old naming and no longer resolves (NXDOMAIN). The current working Preprod proof server is:

https://proof-server.preprod.midnight.network

It resolves to 3 AWS ALB IPs (34.250.71.107 / 63.34.190.149 / 34.250.60.195). The naming seems to have moved to proof-server.{network}.midnight.network — only Preview still has both names alive; Preprod dropped the lace-proof-pub.* one. After I pointed my config at the proof-server.* URL, deploy / record / verify all went through on Preprod with no issues.

So from a builder standpoint this thread is resolved. The only thing left is the docs page itself, which still lists the dead lace-proof-pub.* URL. If that page is Lace-managed, swapping it to proof-server.preprod.midnight.network would save the next person the same dig. Happy to mark this as solved.

4

Thank you @takuya for your response. I have escalated the issue to the proper team. You can follow the issue here: