How to fix NSLOOKUP Default Server: UnKnown?

Issue : "Default Server:  UnKnown" error on NSLOOKUP from Windows Server 2008 DNS Server.


Note : To show the server name a Reverse DNS Zone should be configured. If you do not have a reverse DNS configured please look in to my below post which is related to reverse DNS configuration.
http://www.randika.info/2013/01/how-to-fix-nslookup-unknown-cant-find.html

This issue is not a critical one. Even under this error your DNS resolution can work smoothly. But it's embarrassing when there are issues like this. Right?. Yes I know! me too. :D

The reason for this is your DNS server does not posses a record for the server itself. Or simply it does not know what is it's own name. By creating a PTR static entry we can fix this and let DNS server know it's own name.


1. Open the DNS management console in the Server 2008
        Start > Administrative Tools > DNS

2. Go to the your Reverse Lookup Zone icon and right click on it and select "New Pointer(PTR)".




3. In the New PTR window enter the  IP address of DNS server and enter(or select) the host name of the server.



4. Now click OK and restart the DNS server service.

Now check to see if it is working.

34 comments:

  1. Quick and easy. Thank you for posting.

    ReplyDelete
    Replies
    1. I agree it was very helpfull and fixed a small issue.

      Delete
  2. thnaks bother today i have learnt new thing and fixed my problem too

    ReplyDelete
  3. Thank you very much!
    It's helped me right now !

    ReplyDelete
  4. EXCELLENT ! Many many thanks ! The best article on this, simple and effective ! Keep up the good work ! Thanks for sharing ! Makoto Shimizu

    ReplyDelete
  5. Thanks so much. Rack my brain trying to figure it out. Duh!!

    ReplyDelete
  6. thx! a little tut that solved a big problem i was having!

    ReplyDelete
  7. valid with 2012r2 DNS! thanks for the gold!

    ReplyDelete
  8. Thanks Bro its really good..and Helpfull..

    ReplyDelete
  9. Thanks for this. It helped me out!

    ReplyDelete
  10. sorry my guy this did not fix mine. In my environment I am using a different subnet as secondary IP and that is my DNS.

    ReplyDelete
  11. Works fine! Thanks!
    p.s. for different subnet repeat that step with you ip octet, if you dont have zone - created it first

    ReplyDelete
  12. Thank you man. This was the transitional fossil for me.

    ReplyDelete
  13. Thanks a lot to share this, finally I got solution.

    ReplyDelete
  14. This comment has been removed by the author.

    ReplyDelete
  15. Good post. Easy to understand. Solved my issue

    ReplyDelete
  16. this record already existed for me, adding an addtional record did not resolve the problem. so still get the Default server: unknown message.

    ReplyDelete
  17. Very useful, that help me solved the problem

    ReplyDelete