Skip to content

March 17, 2011

22

nslookup Default Server: UnKnown Windows 2008 R2

The problem looks like this:

This was really annoying one. I checked my DNS settings maybe 1000 times and everything looked ok.

Then I realised that mysterious ::1 is local host address in IPv6. Now the fix was easy. Just clear the IPv6 DNS settings in the adapter settings and set to automatic.

 

 

OK that’s it! Now the DNS name resolution should be working fine!

Read more from Desktop Support
  • jamdev12

    You know how long it took me to find this answer? A long time and I’m glad I did, because I had redone the DC half a dozen times and I could not figure out why the nslookup issue. Thanks for helping me solve it. Now for some pizza!!!

  • don

    really thanks

  • lulu

    Thanks… it’s working

  • Javaid

    I am unable to receive external email, and would appreciate your help. please contact me at javaid7@hotmail.com

    Thank you,

  • SABARISH

    thank you very much for your comment

  • Pingback: nslookup Default Server: UnKnown Windows 2008 R2 - Yuval Sinay

  • Jase989

    Thanks you, fixed the problem. Good to know this nugget of information.

    Yes your right it was annoying when I started nslookup and saw ‘Default Server: Unknown’.
    I though it was because I had the loopback address (127.0.0.1) in the network adaptor setting at first. But that is fine for and DC that is also a DNS server. I was also going to disable IPv6 altogether, then I though IPv6 will be needed in the future so this can’t be right.

  • Patrick

    2 days of racking my brain!! THANK YOU SO MUCH!!!!

  • Anonymous

    hey…i am still having the problem despite of setting it to automatic…can you please help

  • Raycarterrapid

    its showing 3 ip address in nslookup what can i do

  • Mrunal444

    Thanks buddy….

  • na

    worked like a charm

  • Shajeerclt

    That was wonderful. Thanks for your time in updating this solution.

  • Madmaxwedge63

    Thanks for this great solution.

  • Technical

    thanks its works

  • Sdfgsdg

    was the same problem… thanks

  • Playboy58mm

    Thank you. this is worked!

  • anand

    What if we have not selected the IPv6 and still getting the ipv6 on pinging localhost. Even nslookup is still not working..??

  • Noori

    Hi, thanks for your useful solution and it works. If the problem still exist do 2 things:
    1. start – run – cmd – ipconfig /flushdns
    2. clear or delete all browsing history and data of your internet browser (IE, Firefax, Chrome . . . . . )
    Thanks,

  • Cad

    thanks dude

  • Walter

    Have you ever found how the IPV6 got with this weird ::1 configured ? Just wondering what process created this wrong behaviour.

    I had exectly the same issue, it was after applying some hotfixes, but can´t understand exactly what make this config to be wrong.

  • seraphim

    That’s just what i needed. Thank you so much.

Weboy
WordPress Themes