Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

my freebsd server runs a nameserver. the nameserver has information about a single domain. a common, I think, setup for a dedicated server. I also have an upstream nameserver that i would like to forward all requests to that do not concern the domain that I do not serve. below is my /etc/resolv.conf is it correct? I am new to this, and I am not a sysadmin. it seems to work and the names that i do not host get resolved but one thing confuses me that nslookup gives "Non-authoritative answer:" warning:

$ nslookup

Non-authoritative answer:

please advise.

Thanks Konstantin

share|improve this question
Is your question about resolv.conf or is it about the nameserver? – Ignacio Vazquez-Abrams Jul 1 '11 at 17:25
it is about whether what i want to achieve is done the way it should be done? how would an experienced sysadmin do it? I suspect that since nslookup says that the second server is non-authoritative, i might have misconfigured my authoritative server for my domain name. – akonsu Jul 1 '11 at 17:27
There is no way to do it in resolv.conf. You have to configure your dns server to resolve everything – ghm1014 Jul 1 '11 at 17:28
It's... not even looking at the second server. – Ignacio Vazquez-Abrams Jul 1 '11 at 17:28
thank you, how could you tell that it is not looking at the second server? how do i set up my DNS server to resolve everything? – akonsu Jul 1 '11 at 17:30
up vote 4 down vote accepted

"Non-authoritative answer" just means that the response did not come from a nameserver which was authoritative (owner) for the hostname. In this case, not a nameserver.

As long as DNS resolution is otherwise working, you should be fine.

share|improve this answer
thank you. I am confused about the fact that if i remove the second nameserver line from resolv.conf name resolution still works, i do not know why... and since if resolv.conf does not have any nameserver directives, BIND assumes localserver, i could remove both lines and have just the "search" directive, correct? – akonsu Jul 1 '11 at 17:49
Your system is set to look up domains using localhost. It's hitting your local DNS server for the queries. Chances are, everything is setup fine if it's actually working. Your DNS will hit the Internet and look for the domain if it doesn't know it. – Jason Taylor Jul 1 '11 at 17:59
The function of hostname resolution and the BIND service are essentially disparate. Resolution occurs via your computer's resolver (and in Unix typically uses /etc/resolv.conf). BIND is a DNS server that allows you to provide DNS service. If your server is running a nameserver such as BIND on, it will use that if the entry is in resolv.conf. Does that help? – Scott Smith Jul 1 '11 at 18:01
my understanding is that when I type "nslookup" a request is sent to my nameserver first, correct? since it does not know the address of what happens next? what nameserver is queried then? who does it? – akonsu Jul 1 '11 at 18:12
This should answer your question howstuffworks - dns – Scott Smith Jul 1 '11 at 18:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.