I have a large dag-cbor tree of data and a smaller dag-json one. To keep the data on the kubo servers, I just do an ipfs pin add on the root node CID. However, I’m not sure if this means all those CIDs are being published to the DHT, and it doesn’t seem so based on the length of time it takes for public gateways to try to access these CIDs.
How do I make sure they are all being published to the DHT?
You can define the DHT (re)provide strategy as described here, to choose which CIDs are advertised to the DHT.
Also, kubo v0.34.1 currently has a regression on the provide performance, because of it, DHT advertisements may be delayed. This could be explaining why the public gateways cannot find provider for newly added CIDs.
We are working on a fix, but if you cannot wait for the next release you can either downgrade to kubo v0.32.1 or build kubo from source using the boxo fix.