To setup a wildcard DNS A record for GCP Private Service Connect and Azure PrivateLink

Once you have set up the Endpoint within your Application VPC, the next step is to link it to the Endpoint Service offered by Neo4j Aura. To ensure that all the application's network traffic is directed through this Endpoint and eventually reaches your Aura instance, you will need to create a wildcard DNS A record using the following format:

*.production-orch-<orch>.neo4j.io. IN A <ip-address-of-your-endpoint>

This step is crucial for two main reasons:

1. PrivateLink/Private Service Connect will be enabled for all the Aura instances running inside the same region. Adding the wildcard DNS entry will allow name resolution for all the instances.
2. When the Application's neo4j database connection reaches the Aura instance, the Aura instance sends back a routing table with all three cluster node FQDNs:
   <dbid>-<node-id>.production-orch-<orch>.neo4j.io
   and the application will then connect to one of the Neo4j cluster nodes. Since the Aura instance will get updated periodically, the node-id is subject to change. Manually maintaining DNS entries for every change is impractical.