How to Fix “default server unknown nslookup”

Hello everybody, today I’m going to teach you how to fix a very common problem. When you have established a new Domain Controller, by default, you will get an error notification when you try running  “NSLOOKUP” from any computer in your domain,. I’m sure many of you have experienced this. It happens because you have not created a Reverse Lookup Zone (PTR record).

As described in my old article  (DNS records explanation) in order to work with NSLOOKUP and get all the correct queries and information, you should create the PTR record and point it to your DC.

The Error is:

Default Server unknown

and IP :1:


or

Default server unknown nslookup

Go to “Reverse Lookup Zone ” and Create new Zone:

Default server unknown nslookup

Allow “Primary Zone and Store the Zone in AD” and proceed:

Default server unknown nslookup

Next:

Default server unknown nslookup

Allow “IPv4 Reverse Lookup Zone“:

DNS

You have to type your ID Network (Subnet):

DNS

Allow Dynamic Updates (Automatically DNS records registration):

DNS

Finish:

Default server unknown nslookup

If your DC didn’t create the PTR record, please go to “Reverse Lookup Zone” and create the record manually with the following steps:

DNS

Select your DC’s record

Default server unknown nslookup

 

Another way to create this record is

Allow PTR record of DC’s record through your zone:

Default server unknown nslookup

 

Alright, so the purpose of this article was to show you how to fix the “Default server unknown nslookup” issue but we also alloweded automatic PTR registration on our DNS, the next NSLOOK you run will be like this:

 

Default server unknown nslookup

Leave a Comment

Your email address will not be published.

In the news
Load More