Different zone file data from two blockstack core nodes?

Support
#1

Hi, Just noticed something curious while playing around with lucene indexing of name/app data.

My local blockstack-api returns zonefile json:
https://core.brightblock.org/v1/names/mike.personal.id {… “zonefile_txt”: … no address field}
but the same call to the blockstack api returns:
https://core.blockstack.org/v1/names/mike.personal.id: {… “zonefile”: …, address: “…” }

The same zone file hash and last_txid is returned in both cases.

Running ping in both cases returns:
{“status”: “alive”, “version”: “0.18.0”}

Running (on my debian vm),

$ blockstack info
{
    "cli_version": "0.18.0.0",
    "consensus_hash": "1f26e1d8639c8d38172269583906cdc2",
    "last_block_processed": 520001,
    "last_block_seen": 520007,
    "queues": {},
    "server_alive": true,
    "server_host": "node.blockstack.org",
    "server_port": 6263,
    "server_version": "0.18.0.2"
}

My client.ini contains…

[subdomain-resolution]
subdomains_db = /home/bob/.blockstack/subdomains.db
…
[blockstack-client]
server = node.blockstack.org

but subdomains.db doesn’t exist and node.blockstack.org is not pingable.

I tried restarting core, fast sync and then restart api but get the same results. Should this data be in sync or is this just a networking issue my end?

Thanks,
Mike.

#2

Seems like this was a transient error – I’m seeing the same response from both servers.