Why is .bc.googleusercontent shown when doing nslookup on Liferay Load Balancer IP?

Legacy Knowledge Base

Published Sep. 10, 2025

Why is .bc.googleusercontent shown when doing nslookup on Liferay Load Balancer IP?

Written By

Alfonso Crisci

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

When running a nslookup command against the Load Balancer IP that can be seen at Network > Endpoints > Ingress endpoints, .bc.googleusercontent.com will be appended to the Load Balancer's IP:
```
$ nslookup <LB_IP_ADDRESS>
Server: server.example.com
Address: xxx.xx.xxx.xxx
Name: <LB_IP_ADDRESS>.bc.googleusercontent.com
Address: <LB_IP_ADDRESS>
```

Environment

Liferay Cloud

Resolution

Liferay Cloud uses Google Cloud Platform(GCP) as the infrastructure in the background. Google has an Anycast network, in which their IP addresses all appear to point to Mountain View, California, United States. However, whenever a request is made, the selected route will point to a Google Point of Presence nearest to the origin of the request. It will then be routed internally on Google's global network to our service.