We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hello:
I found something wrong when confihured forward in Corefile, like:
forward
.:53 { errors health k8s_gateway test.exampe.com { resources Ingress ttl 30 kubeconfig kubeconfig/kube.config } hosts data/hostsfile { fallthrough } forward . 192.168.1.3:53 log reload }
and I exec command dig console.test.example.com , it reply nothing, and log shows
dig console.test.example.com
[ERROR] plugin/errors: 2 console.test.exampe.com, A: read udp 172.16.10.101:48199 -> 192.168.1.3:53: i/o timeout
when I remove forward . 192.168.1.3:53, and it works
forward . 192.168.1.3:53
The text was updated successfully, but these errors were encountered:
most likely this means that there was no response from 192.168.1.3. can you "dig @192.168.1.3 console.test.example.com" from your local shell?
Sorry, something went wrong.
No branches or pull requests
hello:
I found something wrong when confihured
forward
in Corefile, like:and I exec command
dig console.test.example.com
, it reply nothing, and log showswhen I remove
forward . 192.168.1.3:53
, and it worksThe text was updated successfully, but these errors were encountered: