Side Gadgets

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.
Posted byPosted at 41 comments
Share
Labels, ,
Kanchana Randika is currently a Lead Systems Engineer at a Dubai-based organization. He shares his knowledge and expertise with the community in his spare time.

Comments

  1. NetsolsticeMarch 17, 2013 at 9:06 PM

    Quick and easy. Thank you for posting.

    ReplyDelete
    Replies
    1. TUrkman805May 18, 2013 at 1:06 AM

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

      Delete
  2. UnknownJune 19, 2013 at 12:22 PM

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

    ReplyDelete
  3. UnknownAugust 13, 2013 at 8:04 AM

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

    ReplyDelete
  4. mxmyllionAugust 31, 2013 at 5:33 AM

    very quick and easy .thanks

    ReplyDelete
  5. VCNovember 14, 2013 at 3:43 AM

    Thanks much for sharing.

    ReplyDelete
  6. AnonymousDecember 6, 2013 at 10:19 AM

    Works on Win 2003 R2 x64. Thank you : )

    ReplyDelete
  7. UnknownFebruary 7, 2014 at 4:05 AM

    Thank you

    ReplyDelete
  8. AnonymousMarch 8, 2014 at 6:24 PM

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

    ReplyDelete
  9. AnonymousJanuary 29, 2015 at 5:23 AM

    thanks!

    ReplyDelete
  10. SaladinMarch 17, 2015 at 9:01 PM

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

    ReplyDelete
  11. HeroBlogMay 22, 2015 at 11:31 AM

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

    ReplyDelete
  12. ittechOctober 20, 2015 at 3:17 AM

    valid with 2012r2 DNS! thanks for the gold!

    ReplyDelete
  13. nayaganOctober 29, 2015 at 8:38 AM

    Thanks Bro its really good..and Helpfull..

    ReplyDelete
  14. KDubNovember 19, 2015 at 5:03 AM

    Thanks for this. It helped me out!

    ReplyDelete
  15. UnknownNovember 20, 2015 at 2:45 PM

    Many thanks!!

    ReplyDelete
  16. AnonymousJanuary 8, 2016 at 3:38 PM

    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
  17. KvarkJanuary 13, 2016 at 6:44 PM

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

    ReplyDelete
  18. Oliver MartinezJanuary 22, 2016 at 8:30 PM

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

    ReplyDelete
  19. AMINEFebruary 8, 2016 at 12:32 PM

    many thanx

    ReplyDelete
  20. UnknownApril 12, 2016 at 8:16 PM

    Thank you.

    ReplyDelete
  21. IT service and communication GyanApril 16, 2016 at 10:26 PM

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

    ReplyDelete
  22. UnknownMay 31, 2016 at 12:27 AM

    Thanks

    ReplyDelete
  23. UnknownAugust 10, 2016 at 2:35 PM

    Many Thanks

    ReplyDelete
  24. UnknownAugust 10, 2016 at 5:57 PM

    It's works.

    ReplyDelete
  25. Ranjeet BadheAugust 16, 2016 at 4:41 PM

    Thanks. It worked

    ReplyDelete
  26. DawaSeptember 16, 2016 at 6:32 AM

    Good post. Easy to understand. Solved my issue

    ReplyDelete
  27. UnknownOctober 25, 2016 at 1:26 PM

    thanks mate !

    ReplyDelete
  28. UnknownDecember 1, 2016 at 2:11 PM

    many thanks

    ReplyDelete
  29. UnknownJanuary 24, 2017 at 10:58 AM

    thank you, this worked for me

    ReplyDelete
  30. UnknownMarch 27, 2017 at 2:26 PM

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

    ReplyDelete
    Replies
    1. XinghaiNovember 25, 2017 at 9:37 PM

      Try to remove uncheck IPV6 within NIC propertities window

      Delete
  31. UnknownApril 18, 2017 at 7:45 PM

    Excellent tip, thanks

    ReplyDelete
  32. UnknownJuly 19, 2017 at 8:39 AM

    Very useful, that help me solved the problem

    ReplyDelete
  33. curiosoOctober 1, 2017 at 4:15 AM

    Muchas Muchas Gracias, tremendo aporte!!!

    ReplyDelete
  34. UnknownOctober 1, 2017 at 12:53 PM

    Let to thanks so much!

    ReplyDelete
  35. UnknownOctober 13, 2017 at 7:03 PM

    Great!. Thanks a lot.

    ReplyDelete
  36. DavudNovember 11, 2017 at 10:52 PM

    Thanks bro so usefull

    ReplyDelete
  37. UnknownJanuary 3, 2018 at 2:05 PM

    Thank A Lot!

    ReplyDelete
  38. UnknownMarch 13, 2018 at 2:41 PM

    thanks it helped me.

    ReplyDelete
  39. sirsimAugust 2, 2018 at 1:52 PM

    Create a Reverse Lookup Zone for your Main ADDC. Works Perfectly.

    ReplyDelete
You are welcome to share your ideas with us in the comments!

Archive

Contact Form

Send