Got recursion not available from ... trying next server
Summary
(Summarize the bug encountered concisely.) When a nameserver 10.247.0.10 is configured in the /etc/resolv.conf file, it can be accessed normally by using "nslookup cmfpod". However, after adding a nameserver (10.247.0.11) in /etc/resolv.conf, using "nslookup cmfpod" is not enough to correctly resolve the domain name, and prompts the following error: ";; recursion is not available from 10.247.0.10, try the next server"
BIND version used
9.16.23
Steps to reproduce
When configured as follows:
resolv.conf.txt `[root@ddbsf-pod-5d7b99cc4c-7srpn ~]# nslookup cmfpod Server: 10.247.0.10 Address: 10.247.0.10#53
Name: cmfpod.project-yl175.svc.cluster.local Address: 89.31.0.72`
But When configured as follows: resolv.conf.txt [root@ddbsf-pod-5d7b99cc4c-7srpn ~]# nslookup cmfpod
What is the current bug behavior?
Got recursion not available from 10.247.0.10 trying next server
What is the expected correct behavior?
should parse normally:
nslookup cmfpod
Server: 10.247.0.10
Address: 10.247.0.10#53
Name: cmfpod.project-yl175.svc.cluster.local
Address: 89.31.0.72
Relevant configuration files
Relevant logs and/or screenshots
When configuring nameserver 10.247.0.10 in the configuration file nameserver 10.247.0.11, using nslookup to make a request, the following error is reported: fail.log.rar
When configuring nameserver 10.247.0.10 in the configuration file Use nslookup to request and parse normally: success.log.rar
Possible fixes
(If you can, link to the line of code that might be responsible for the problem.)