Using nslookup tool from DNS it opens prompt stating "Default Server: Unknown"

Whenever I launch the nslookup from the DNS console (Launch DNS) it always appears with Default Server:  UnKnown
Address:  fe80::8d22:fe83:fbd3:9ec5

But when I go to the command prompt and type nslookup everything displays fine.
C:\Users\Administrator.CBSSC>nslookup
Default Server:  scdc2.cbssc.com

I have checked PTR records, IPs and everthing looks fine. Is there a problem with DNS? Configuration?
chilli727Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
chilli727Connect With a Mentor Author Commented:
Thank you guys. Will do.
0
 
PapertripCommented:
To be clear, you have a reverse zone and PTR record for the ipv6 address as well?

Aside from that, do queries still work via the console after you get that error?
0
 
chilli727Author Commented:
I do have a reverse zone and the IPv6 records do show up in there. I see both "A" and "AAAA" records.

Queries still work via the console eventhough it shows "Default Server:  UnKnown"

Also, a little more information if it helps. This is a transitioning from Windows 2003 domain. I had two 2003 DC w/ DNS. I migrated from one to a new 2008 R2 DC w/DNS and still have one more 2003 DC. I'm just not sure if this is normal and continue with the migration.
0
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

 
PapertripCommented:
I do have a reverse zone and the IPv6 records do show up in there. I see both "A" and "AAAA" records.

You see A and AAAA records in the reverse IPv6 zone?
0
 
chilli727Author Commented:
I do not have a separate reverse zone for IPv6 zone. I do see the A and AAAA in my regular reverse zone which is my lan network.

0
 
PapertripConnect With a Mentor Commented:
A and AAAA records are for forward zones, they have no place in reverse zones.  Reverse zones contain PTR records.

The underlying problem here is that you have no reverse record for fe80::8d22:fe83:fbd3:9ec5

This is not a fatal error but rather an informative message.  You can continue with your migration, however any reverse lookups for addresses in your IPv6 range are going to fail.
0
 
abhijitwaikarConnect With a Mentor Commented:
Hi,

This is not actually a problem as suggested above, It is just that server unable to get PTR record as the Reverse Lookup Zone is not configured on DNS server.

As your posted result, It looks like the you have only Reverse Lookup Zone for IPv4 and to correct this warning info you need to create the Reverse Lookup Zone for IPv6 as well.

Also you can ignore this, but check below Security Considerations for the Presence of a Reverse Lookup Zone
Being able to make NSLookup work against your DNS servers is not the only, or most important, reason why you should configure reverse lookup zones. Applications on your internal network, such as DNS clients that are trying to register PTR records in a reverse lookup zone, can “leak” information about your internal network out to the Internet if they cannot find a reverse lookup zone on the intranet. To prevent this information from leaking from your network, you should configure reverse lookup zones for the addresses in use on your network

IPv4 and IPv6 Reverse Lookup Zone Configuration: http://abhijitw.wordpress.com/2011/09/05/ipv4-and-ipv6-reverse-lookup-zone-configuration/

Regards,
Abhijit Waikar.
----------------------------
MCSA|MCSA:Messaging|MCTS|MCITP:SA
My Blog: http://abhijitw.wordpress.com
This posting is provided AS IS with no warranties, and confers no rights.
0
 
PapertripCommented:
This is not actually a problem as suggested above, It is just that server unable to get PTR record as the Reverse Lookup Zone is not configured on DNS server.

As your posted result, It looks like the you have only Reverse Lookup Zone for IPv4 and to correct this warning info you need to create the Reverse Lookup Zone for IPv6 as well

That is exactly what I said...
0
 
chilli727Author Commented:
T
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.