Skip to content

private link feedback #1059

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fiquick wants to merge 2 commits into
base: console
Choose a base branch
from
Open

private link feedback #1059

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b8ceb97
private link feedback
fiquick Jun 24, 2026
c0f9b87
Merge branch 'console' into private-link-feedback
fiquick Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 17 additions & 2 deletions modules/ROOT/pages/security/secure-connections.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,9 @@ These are different in your AuraDB Virtual Dedicated Cloud environment.

. The application initializes a driver connection to neo4j+s://abcd1234.production-orch-0000.neo4j.io.
. The network layer then queries the DNS server to resolve the fully qualified domain name (FQDN) (in this case, abcd1234.production-orch-0000.neo4j.io) to its corresponding IP address.
. The Cloud Virtual Network private DNS is queried, and it resolves the FQDN to 10.10.10.10, based on the wildcard DNS A record created: *.production-orch-0000.neo4j.io -> 10.10.10.10
. The Cloud Virtual Network private DNS is queried, and it resolves the FQDN to 10.10.10.10, based on the wildcard DNS A record created: *.production-orch-0000.neo4j.io -> → <IP address of your cloud provider Private Link/Private Endpoint>
. For example: *.production-orch-0000.neo4j.io → 10.10.10.10
. The wildcard record must point to the IP address of the [your/the customer's] Private Link/Private Endpoint, not to the Aura Private URI or any Aura-managed endpoint.
. The application's connection is directed to 10.10.10.10, which is the private link endpoint.
From there, the private link endpoint forwards the network connection to the private ingress through the private link.
. The private ingress extracts the dbid from the FQDN and directs the connection to the appropriate Aura instance (dbid: abcd1234).
Expand Down Expand Up @@ -273,13 +275,26 @@ This breaks routing for custom endpoints located in the other regions, and there

== Test connectivity through the private endpoint

Use the `nslookup` command to confirm whether the Fully Qualified Domain Names (FQDNs) of your Aura instances are directed to the IP address of the PrivateLink endpoint (usually represented by an internal IP address, such as 10.0.0.0).
Verify DNS resolution before testing application connectivity.
If DNS resolution fails, Private Link connectivity will not work regardless of the network configuration.

Use the `nslookup` command (or `dig` on Linux/macOS) to confirm whether the Fully Qualified Domain Names (FQDNs) of your Aura instances are directed to the IP address of the PrivateLink endpoint (usually represented by an internal IP address, such as 10.0.0.0).

[source,bash]
----
nslookup <dbid>.production-orch-<orchestra>.neo4j.io
----

Alternatively, you can use:

[source,bash]
----
dig <dbid>.production-orch-<orchestra>.neo4j.io
----

Both commands should resolve the hostname to the private IP address of your cloud provider's Private Link/Private Endpoint.
If they do not, verify that your private DNS service is configured correctly and that the wildcard record (*.production-orch-<orchestra>.neo4j.io) points to the Private Link endpoint IP address.

Use cURL from a VM instance or a container located in the related VPC network.

[source,bash]
Expand Down