Added Limitation about MongoDB IPv4 address in connection string (#6331)

Co-authored-by: Jon Harrell <[email protected]>

content/300-accelerate/500-known-limitations.mdx

@@ -31,3 +31,16 @@ For queries that cannot be optimized or pared down, we recommend one of two solu
 2. **Separate analytics queries**: Our preferred solution is to separate your analytics queries into a separate application. This separate application can then use a direct connection so that it can run heavy queries without impacting the performance or cost of your Accelerate-powered application.
 
 If you have a use case that requires running extremely heavy or long-running queries and Prisma Accelerate, please reach out to us.
+
+## Not compatible with direct IPv4 addresses in MongoDB connection strings
+
+Accelerate does not support direct IPv4 addresses in MongoDB connection strings. When an IPv4 address is provided, Accelerate converts it to an IPv6 format to route through its NAT gateway. This conversion may cause the connection string to be considered invalid due to the formatting of the port value.
+
+**Workaround**: To resolve this issue, create a DNS record that points to your IPv4 address and use that DNS record in your connection string instead of the direct IP.
+
+### Example
+
+- **IPv4 connection string** (not supported): `mongodb://user:[email protected]:27017/db_name`
+- **DNS record connection string** (supported): `mongodb://user:[email protected]:27017/db_name`
+
+For additional details on Accelerate’s IPv6-first design, refer to our [blog post](https://www.prisma.io/blog/accelerate-ipv6-first).