Jun 04 2022 05:53 AM - edited Jun 04 2022 05:53 AM
Hello when i lunch NSLOOKUP via CMD i got error below,However the DNS is correctly configured.is there any solution for this issue. the primary server DC is SRVDCLMV01
Jun 04 2022 02:47 PM
Might be there's no IPv6 reverse zone
Creating a reverse lookup zone | Microsoft Docs
how to configure DNS to support ipv4 and ipv6 (microsoft.com)
Jun 05 2022 12:56 AM
Solution
That's expected when the current server is set to the loopback address (in this case, the IPv6 loopback of ::1.) It's not an error since the server cannot resolve ::1 via DNS itself.
After entering nslookup, if you then specify "server ::1", you'll see the server header change again to "[::1]" meaning it can't look it up.
If you run "server 127.0.0.1", you'll see the server header change once again to the pre-defined value of "localhost".
Here's an example of both of these scenarios from a Server 2016 host.
On Server 2022, the IPv6 loopback (::1) behaves the same way as the IPv4 loopback (127.0.0.1) and displays "localhost".
In any case, as I say, it's not an error.
Cheers,
Lain
Jun 05 2022 12:56 AM
Solution
That's expected when the current server is set to the loopback address (in this case, the IPv6 loopback of ::1.) It's not an error since the server cannot resolve ::1 via DNS itself.
After entering nslookup, if you then specify "server ::1", you'll see the server header change again to "[::1]" meaning it can't look it up.
If you run "server 127.0.0.1", you'll see the server header change once again to the pre-defined value of "localhost".
Here's an example of both of these scenarios from a Server 2016 host.
On Server 2022, the IPv6 loopback (::1) behaves the same way as the IPv4 loopback (127.0.0.1) and displays "localhost".
In any case, as I say, it's not an error.
Cheers,
Lain