Info icon
End of Life Notice: For Trend Cloud One™ - Conformity Customers, Conformity will reach its End of Sale on “July 31st, 2025” and End of Life “July 31st, 2026”. The same capabilities and much more is available in TrendAI Vision One™ Cloud Risk Management. For details, please refer to Upgrade to TrendAI Vision One™
Logo of TrendAI
Use the Knowledge Base AI to help improve your Cloud Posture

Remove Dangling DNS Records

TrendAI Vision One™ provides continuous assurance that gives peace of mind for your cloud infrastructure, delivering over 1400 automated best practice checks.

Risk Level: High (not acceptable risk)

Ensure that dangling DNS records are removed from your public Cloud DNS zones in order to maintain the integrity and authenticity of your domains/subdomains and to protect against domain hijacking.

Security

When an ephemeral Google Cloud resource like an external IP address is released, it becomes available for others to use. An attacker could potentially acquire this IP and intercept traffic intended for your domain/subdomain hosted in Cloud DNS, or launch Denial-of-Service (DoS) attacks. Since you have no control over who gets the released IP, it is highly recommended to regularly check for any unused DNS records pointing to these IPs and remove them from your Cloud DNS zones.

Audit

To identify anhy dangling DNS records within your public Cloud DNS zones, perform the following operations:

Using GCP Console

  1. Sign in to the Google Cloud Management Console.

  2. Select the Google Cloud Platform (GCP) project that you want to access from the top navigation bar.

  3. Navigate to Network services console available at https://console.cloud.google.com/net-services.

  4. In the navigation panel, choose Cloud DNS and select the ZONES tab to access the Cloud DNS zones configured for the selected GCP project.

  5. Click inside the Filter box, select Zone type and choose Public, to list only the public DNS zones available for your project.

  6. Click on the name (link) of the public DNS zone that you want to examine.

  7. Click inside the Filter box, select Type and type A, choose OR, and select Type and type AAAA, to list only the A and AAAA records defined for the selected DNS zone.

  8. Click on the name of the DNS record that you want to examine.

  9. In the Routing data section, under Data, copy the external IP address configured for the selected DNS record.

  10. Navigate to VPC network console at https://console.cloud.google.com/networking.

  11. In the navigation panel, choose IP addresses and select the EXTERNAL IP ADDRESSES tab to list the external IP addresses reserved for the selected GCP project.

  12. Click inside the Filter box, select IP address, paste the IP address copied at step no. 9, and press Enter. If the specified IP address is no longer reserved for your GCP project, the Cloud CDN console will return the following message: No rows to display. If the address associated with your DNS record is no longer available within your Google Cloud account, the DNS record pointing to the missing IP becomes a dangling DNS record and can be removed from your Cloud DNS zone.

  13. Repeat steps no. 8 – 12 for each DNS record that you want to examine.

  14. Repeat steps no. 6 – 13 for each public DNS zone that you want to examine.

  15. Repeat steps no. 2 – 14 for each GCP project deployed in your Google Cloud account.

Using GCP CLI

  1. Run projects list command (Windows/macOS/Linux) with custom query filters to list the IDs of the Google Cloud Platform (GCP) projects currently available in your Google Cloud account:

    gcloud projects list
  --format="table(projectId)"

  2. The command output should return the requested GCP project identifiers (IDs):

    PROJECT_ID
cc-main-project-123123
cc-data-project-112233

  3. Run dns managed-zones list command (Windows/macOS/Linux) with the ID of the GCP project that you want to examine as the identifier parameter and custom query filters to describe the name and type of each DNS zone available within the selected project:

    gcloud dns managed-zones list 
  --project cc-main-project-123123 
  --format="table(name,visibility)"

  4. The command output should return the name and type (public or private) of each DNS zone created for your project. A public zone has the VISIBILITY attribute set to public:

    NAME: trendmicro
VISIBILITY: public

NAME: visionone
VISIBILITY: public

  5. Run dns record-sets list command (Windows/macOS/Linux) with the name of the public DNS zone that you want to examine as the identifier parameter and custom output filtering to describe the value (data) for each DNS record created for your DNS zone:

    gcloud dns record-sets list 
  --zone=trendmicro 
  --format="table(type,rrdatas)"

  6. The command output should return the DNS record type and the associated data:

    TYPE: A
RRDATAS: ['35.209.130.67']

TYPE: NS
RRDATAS: ['ns-cloud-a1.googledomains.com.', 'ns-cloud-a2.googledomains.com.', 'ns-cloud-a3.googledomains.com.']

TYPE: SOA
RRDATAS: ['ns-cloud-a1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300']

  7. Run compute addresses list command (Windows/macOS/Linux) with custom filtering to list the external IP addresses reserved for your GCP account:

    gcloud compute addresses list 
  --filter "addressType~EXTERNAL"
  --format="table(name,status,address)"

  8. The command output should return a list with external IP addresses available for consumption:

    NAME: tm-project5-app-ipv4
STATUS: RESERVED
ADDRESS: 35.186.10.46

NAME: tm-web-portal-ipv4
STATUS: RESERVED
ADDRESS: 35.105.56.10

    If one or more IP addresses configured for A and AAAA records, returned at step no. 6, are no longer reserved for your GCP account, they will not be listed by the compute addresses list command at step no. 8. If an IP address associated with a DNS record is no longer reserved for your Google Cloud account, the DNS record pointing to the missing IP becomes a dangling DNS record and can be removed from your Cloud DNS zone.

  9. Repeat steps no. 5 - 8 for each public DNS zone that you want to examine.

  10. Repeat steps no. 3 – 9 for each GCP project deployed in your Google Cloud account.

Remediation / Resolution

To ensure that all dangling DNS records are removed from your public Cloud DNS zones, perform the following operations:

Using GCP Console

  1. Sign in to the Google Cloud Management Console.

  2. Select the Google Cloud Platform (GCP) project that you want to access from the top navigation bar.

  3. Navigate to Network services console available at https://console.cloud.google.com/net-services.

  4. In the navigation panel, choose Cloud DNS and select the ZONES tab to access the Cloud DNS zones configured for the selected GCP project.

  5. Click inside the Filter box, select Zone type and choose Public, to list only the public DNS zones available for your project.

  6. Click on the name (link) of the public DNS zone that you want to configure.

  7. Click inside the Filter box, select Type and type A, choose OR, and select Type and type AAAA, to list only the A and AAAA records defined for the selected DNS zone.

  8. Select the dangling DNS records with missing IP addresses and choose DELETE RECORD SETS.

  9. In the Delete record sets? box, choose DELETE to confirm the removal of the selected DNS records.

  10. Repeat steps no. 6 – 9 for each public DNS zone that you want to configure.

  11. Repeat steps no. 2 – 10 for each GCP project deployed within your Google Cloud account.

Using GCP CLI

  1. Run dns record-sets delete command (Windows/macOS/Linux) to remove the dangling DNS record with missing IP address from your Cloud DNS zone:

    gcloud dns record-sets delete trendmicro.com. 
  --project cc-main-project-123123 
  --type=A 
  --zone=trendmicro

  2. The command output should return the full URI of the deleted DNS record set:

    Deleted [https://dns.googleapis.com/dns/v1/projects/cc-main-project-123123/managedZones/trendmicro/rrsets/trendmicro.com./A].

  3. Repeat steps no. 1 and 2 for each dangling DNS record that you want to delete.

  4. Repeat steps no. 1 – 3 for each public DNS zone that you want to configure.

  5. Repeat steps no. 1 – 4 for each GCP project deployed within your Google Cloud account.

References

Publication date May 1, 2024

Related CloudDNS rules