Verify which address a configured Bitcoin peer resolved to
After moving a private peer to a new host, inspect the address Bitcoin Core actually connected to under the configured peer name.
Inspect configured peer records
The addednode field preserves the configured name or endpoint. For a connected entry the address objects show the actual endpoint and direction. Run this query on the node that maintains the manual peer configuration.
bitcoin-cli getaddednodeinfo | jq '.[] | {addednode, connected, addresses}'
Verify the migration outcome
Find the configured hostname and compare its connected address with the planned destination. connected false means there is no active connection for that entry at sample time. A one-time onetry connection is excluded from this inventory. To inspect all currently connected peers regardless of how they were discovered, use getpeerinfo.
bitcoincore.org getaddednodeinfo · bitcoincore.org getpeerinfo