Dns records are not dynamically updating death of spouse dating
This is the policy I am using for External DNS on my cluster: At this point, External DNS should be up, running, and ready to create DNS records from Ingress resources.
Let’s see this work with the same example used in the External DNS documentation for GKE.
The Ingress consists of a set of rules, based on host names and paths, that define how requests are routed to a backend Service.
When you make a request through your browser to make a connection to yahoo.com, your browser and computer initiate a service request that goes to a DNS (DOMAIN NAME SERVER) associated with your Internet Service Provider (ISP).
A service called DYNAMIC DNS allows users anywhere on the Internet to find your website(s) and/or mail server(s) with their constantly changing IP address.
The function of a DNS is to provide a FIXED name for your website to "home to" with a fixed address for remote users on the internet to use to find your Dynamically Changing IP address.
External DNS is a relatively new Kubernetes Incubator project that makes Ingresses and Services available via DNS.
It currently supports AWS Route 53 and Google Cloud DNS.