Checking CNAME DNS records

A regular work day

I have been working on leveraging the backup and restore capability of APIConnect when deployed on OpenShift. To do this I need to simulate that the OpenShift cluster has been lost and that I needed to restore it in a newly created cluster.

You can read more about this strategy directly on the IBM Docs website.

I don’t have a load balancer at hand to test this so I was simply creating CNAME records that pointed to the cluster but I needed to find a way to test if my machine (or router) cache had already been refreshed with the updated DNS records.

Solution

My most used command during this exercise:

dig -t CNAME gw.domain.com

Source and more

It’s always nice to keep this handy when working with DR or HA scenarios.