Machine cannot read its own .internal DNS entry on startup

I am currently setting up an app that needs to be able to discover the 6PNs of other machines in the same region. To do this, I am making a DNS lookup on machine startup to <region>.<appname>.internal. However, I’ve noticed that it seems this DNS host intermittently isn’t available for a few seconds after the first machine has started up in a region.

I’m not sure if this was to be expected behavior, or if this unintended? For my use case I can probably assume when this DNS lookup fails it’s because it’s the first machine in the region, but having certainty would be nice.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.