What is custom DNS service
Your jobs may access external resources (such as CKafka and TencentDB for MySQL) via domains to facilitate Ops. You can customize DNS service to resolve domains. For the implementation of custom DNS service, see the Kubernetes document Customizing DNS Service. The DNS resolution process is generally completed with one of the following methods. 1. DNS host mapping. As shown below, you can access a CKafka instance (IP: 172.17.0.2) with kafka.example.com.
172.17.0.2 kafka.example.com
172.17.0.3 mysql.example.com
2. DNS resolution. As shown below, assume that your DNS server IPs are 172.17.0.253 and 172.17.0.254. Your requests in a job to access any domain in the form of *.example.com will be resolved using your DNS server. If you set the mapping of 172.17.0.2 kafka.example.com in your DNS server, requests to access kafka.example.com will be resolved to 172.17.0.2.
example.com {
forward . 172.17.0.253 172.17.0.254
}
How to customize DNS service
Customize DNS service for a cluster on its details page. Note: If both host mapping and DNS resolution are configured, DNS resolution will be used.
Directions
2. set the host or domain in the pop-up window, and click Confirm to save the settings (can be modified if necessary).