I’m receiving the message “invalid hostname not pointing to client IP” in
topologyUpdater_lastresult.json since registering my relays with the pool certificate.
I registered the pool first with my operator cli keys and address with only one relay. I submitted my Ledger account as a pledging owner about 8 hours later, including both relays in the new certificate.
I feel it is the registration that somehow caused this to happen, or at least to visibly manifest, as the
topologyUpdater_lastresult.json for each relay reflects the change to “invalid” occured at the time of certificate online propogation for each.
Aside from adding the relays to the certificate and submitting it, nothing about their setup has changed. The “glad you’re staying with us” message reliably came through for hundreds of hours until this.
Both relays are still running great and processing transactions. Block producer shows 2 in and 2 out (both relays) and each relay has outgoing and incoming peer connections.
- pool id:
- relay addresses:
- both subdomains cname aliased to