---
title: Verify VPC Peering Connectivity
description: Use the procedures on this page to verify that a VPC peering
connection is working correctly and help troubleshoot connectivity issues.
pubDate: 2026-08-17T09:53:44.266Z
antora:
editUrl: https://github.com/couchbase/docs-capella/edit/main/modules/clouds/pages/vpc-peering/verify-troubleshoot.adoc
xref: xref:cloud:clouds:vpc-peering/verify-troubleshoot.adoc[]
---
[Consult the llms.txt file for a full list of contents](/llms.txt)
[View original HTML](/cloud/clouds/vpc-peering/verify-troubleshoot.html)
# Verify VPC Peering Connectivity
> Use the procedures on this page to verify that a VPC peering connection is working correctly and help troubleshoot connectivity issues.
## [](#verify-connectivity)Verify VPC Peering Connection
With a new VPC Peering connection, check that applications connecting from the application VPC are using the private network correctly.
### [](#hostname-resolution)Check Hostname Resolution
When an application connects to a Capella cluster, its first step is to resolve the hostnames of all nodes in the cluster. Use the following procedure to check that hostname resolution is working correctly:
1. In the Capella UI, retrieve the DNS SRV record for your cluster by clicking the **Connect** tab.
2. With the DNS SRV record, use `nslookup` to resolve the hostname. For example:
```console
nslookup -type=SRV _couchbases._tcp.cb.a-lxzt-gdkzoqfuu.cloud.couchbase.com
```
```console
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
_couchbases._tcp.cb.a-lxzt-gdkzoqfuu.cloud.couchbase.com service = 0 0 11207 9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com.
_couchbases._tcp.cb.a-lxzt-gdkzoqfuu.cloud.couchbase.com service = 0 0 11207 jkzlapnfpklgjhtl.a-lxzt-gdkzoqfuu.cloud.couchbase.com.
_couchbases._tcp.cb.a-lxzt-gdkzoqfuu.cloud.couchbase.com service = 0 0 11207 4ncgebm6lmtbxmkr.a-lxzt-gdkzoqfuu.cloud.couchbase.com.
```
3. Use `nslookup` to resolve one of the hostnames returned from the SRV record. For example:
```console
nslookup 9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com
```
```console
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: 9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com
Address: 10.0.18.110
```
4. When the DNS resolution is working correctly, `nslookup` returns the private IP of the Capella node—an IP from the cluster's CIDR block. If the `nslookup` returns the public IP for this node and you're using AWS, check that you have:
* Enabled DNS resolution
* Enabled DNS hostnames
* Associated the hosted zone with your VPC
For more information, see [Create a VPC Peering Connection with AWS](peer-aws.md).
### [](#check-network-connectivity)Check Network Connectivity
If DNS resolution is working correctly, use the following procedure to check the network connectivity between your application instances and your Capella cluster:
1. To check that the routing works for your VPC, use `traceroute` with one of the nodes in your cluster that you resolved when [checking DNS resolution](#hostname-resolution). For example:
```console
traceroute -T 9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com -p 18091
```
```console
traceroute to 9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com (10.0.18.110), 30 hops max, 60 byte packets
1 ip-10-0-18-110.us-west-2.compute.internal (10.0.18.110) 0.303 ms 0.288 ms 0.302 ms
```
2. The result from this `traceroute` should return quickly. If it's slow, this can indicate issues with your routing. Validate the route table associated with the VPC to check that you have associated the correct CIDR block with the VPC peering connection.
3. Use `curl` to validate that Couchbase Server is responding correctly over the private network:
```console
$ curl -k https://9qvj8x-f2oxhahtz.a-lxzt-gdkzoqfuu.cloud.couchbase.com:18091
```
```console
301 Moved PermanentlyMoved Permanently
The document has moved