[SOLVED] [DNS] DIG can't resolve but HOST and NSLOOKUP can
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As you can see from the dig command output above, you get a REFUSED answer to your query from 172.17.70.1, meaning that you are not allowed to use this nameserver.
As you can see from the dig command output above, you get a REFUSED answer to your query from 172.17.70.1, meaning that you are not allowed to use this nameserver.
Hi! I get that. Since I have 3 DNS servers configured. If the first one fails, it proceeds with the next one (as shown in nslookup output). But why dig fails to resolve without trying the other two nameservers?
A wise man once said: 'If everything else fails, read the man page'.
Code:
+[no]fail
This option indicates that named should try [or not try] the next server if a SERVFAIL is received. The default is to not
try the next server, which is the reverse of normal stub resolver behavior.
A wise man once said: 'If everything else fails, read the man page'.
Code:
+[no]fail
This option indicates that named should try [or not try] the next server if a SERVFAIL is received. The default is to not
try the next server, which is the reverse of normal stub resolver behavior.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.