Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm having DNS lookup problems on my internal network. I'm using an internal DNS server with the ip

If I use nslookup everything works like it should:

hawk:~ user$ nslookup publicwebserver.domain.local



Name: publicwebserver.domain.local


My problem is that no other program seems to be able to lookup the dns name:

hawk:~ user$ ping publicwebserver.domain.local

ping: cannot resolve publicwebserver.domain.local: Unknown host

It's like this for all command line programs and e.g. Firefox. If I fire up Network Utility, I get the same problem on the Lookup tab (probably since it uses nslookup or host on the back-end).

Has any of you seen this issue before?

share|improve this question

2 Answers 2

up vote 2 down vote accepted

It seems as if this is due to me pointing to both internal and external dns servers on my client, as mentioned here. After I removed all external DNS servers from my list of servers, everything works as it should.

share|improve this answer

I have the same problem on OS X Yosemite beta, and switching to Google's fixed the problem for me.

share|improve this answer

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.