We help IT Professionals succeed at work.

SBS2011 - When IPV6 is turned on, nslookup can not resolve DNS

I have a new SBS2011 server installed.  When I run nslookup with IPV6 on, it states
'default server unknown'.
Comment
Watch Question

Kent WSr. Network / Systems Admin
CERTIFIED EXPERT

Commented:
Where is  your name server?  On that machine, or another on the network somewhere?  Or, are you using and ISPs name server that was assigned to you?
We're not sure if you are running AD, etc., so where DNS lives is a little ambiguous as this point.
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
"default server unknown" does not mean DNS is not working. It simply means that nslookup was not able to do a reverse lookup of the server name from its IP and display the *name*( of the DNS server it is using. This is normal for SBS as a reverse PTR record is not created by default for the internal server, and will often occur with IPv4 as well. The lookup itself should still succeed.

-Cliff

Author

Commented:
This is a DNS Server and a GC as well.  The settings for IPV6 are to point to itself.

When IPV6 is off, it resolves properly.
David BeveridgeLinux Systems Admin
CERTIFIED EXPERT

Commented:
Do you have public IPv6 Addresses on the machine?
Kent WSr. Network / Systems Admin
CERTIFIED EXPERT

Commented:
last answer notwithstanding, I personally am not worried about the default server unknown,  rDNS config, or lack thereof.  I'm  addressing the *title* issue, "nslookup can not resolve DNS".
By this, I would assume OP can't resolve any DNS, reverse or otherwise, so due to his working, I'm expecting that the lookup itself did not succeed.  Hence, posed questions remain unchanged.  With an additional one - is nslookup the only failing query, or can this machine make no DNS resolution, period?

Author

Commented:
As is stated, when IPV6 is off, the machine resolves properly.  When IPV6 is on, it can ping other machines successfully.

I'm by no means an expert in any of this so your help is appreciated.

When IPV6 is on and I ping another server with IPV6 on, it returns the Private side IP of IPV4 only.

One thing I am noticing is that the General tab of IPV6 is  set to "Use the following IPv6 address" and "use the follwing DNS server addresses".
Linux Systems Admin
CERTIFIED EXPERT
Commented:
And what is the following IPv6 Address and the following DNS Server address?

Is that DNS IP address reachable?

If not there then perhaps you can change to Obtain IP address Automatically.

Author

Commented:
It is the static IPv6 address of the same server I'm running the command on.
David BeveridgeLinux Systems Admin
CERTIFIED EXPERT

Commented:
If that IPv6 address starts with anything except "f", the machine will assume it has IPv6 connectivity to the Global Internet.
eg: Does the IPv6 address begin with a "2" ?
David BeveridgeLinux Systems Admin
CERTIFIED EXPERT

Commented:
Does you server have IPv6 connectivity from your ISP?
David BeveridgeLinux Systems Admin
CERTIFIED EXPERT

Commented:
Does your local DNS server have a PTR record (Reverse DNS) for it's static IPv6 address?
If not, that will cause the server unknown error.

David BeveridgeLinux Systems Admin
CERTIFIED EXPERT

Commented:
Is the reverse zone delegated to your DNS Server?

Author

Commented:
I'm currently working with microsoft on some communication issues on this server and will respond accordingly when I have more info.
jackbensonDirector

Commented:
i would be interested in how you solved this

thanks

jack

Author

Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for creativenetworks's comment http:/Q_27426677.html#37074308

for the following reason:

This issue was resolved by Microsoft and required a hi level technician.
CERTIFIED EXPERT
Top Expert 2013

Commented:
Glad to hear you were able to resolve creativenetworks. I would love to hear any information you have about the solution as it was quite a unique issue.
--Rob

Author

Commented:
No solution was reached.  Server was rebuilt.

Author

Commented:
OK to delete this question?
CERTIFIED EXPERT
Top Expert 2013

Commented:
I thought you mentioned; "This issue was resolved by Microsoft and required a hi level technician. "?

Author

Commented:
Correct.  They could not resolve it and thought it best to rebuild, which we did.  I'll gladly aware points but was told the EE did not want unresolved questions in it's database.
CERTIFIED EXPERT
Top Expert 2013

Commented:
Sorry I wasn't looking for points, but rather it was a very interesting question to which you stated; "This issue was resolved by Microsoft", which one would assume that meant it was fixed. I would be very interested in the solution as I am sure would others. EE is a great place to ask questions, but firstly it is a database of solutions. Whether solved by someone else, yourself, or Microsoft, all answer's are very valuable to those that follow.  It just seems the closing changed from deserted, to Microsoft solved, to rebuilt.

However I won't "beat a dead horse".