DNS nslookup error timeout was 2 second

Question

_{Monday, March 16, 2009 6:44 AM}

Dear Sir

after installation of 2008 server and dns when i typed a command of nslookup dos prompt i  m  facing error 

ip address          192.168.0.1 
subnet mask       255.255.255.0

preferred  Dns    192.168.0.1

DNS request timed out. timeout was 2 seconds

**Default Server: Unknown
address: fe80: : b9bc:6516:36ec:84f3
**
why its not showing me ip address

but at the client side its showing me

Default Server: abc
Address:  192.168.0.1

thanks in advance

windows server and exchange server isa server problem

All replies (18)

_{Saturday, March 21, 2009 11:52 AM ✅Answered | 4 votes}

Thanks All

                problem is solved just go on lan card properties and un check  the Internet protocol (TCPIP/IPV6)
and NSLOOKUP IS WORKING ON SERVER (windows server read first TCPIP/IPV6 Thats y i showing me 2 second delay

thanks bro

Kamran Ashfaq

MCTS- MCITP (SA)- MCITP (EA)
windows server and exchange server isa server problem

_{Tuesday, March 17, 2009 9:02 AM}

When we use NSLOOKUP it first try to do reverse lookup entry, check if you have reverse lookup zone configured and you have record for 192.168.0.1 IP assoicated with correct name.

hope this helps.

_{Tuesday, March 17, 2009 9:03 AM}

Just to add....

it showing IPv6 link local IP, starts with Fe80............which are not registered in DNS which mean it is result of LLMNR protocol introduced in vista and 2008 server

_{Tuesday, March 17, 2009 1:49 PM | 1 vote}

hi there,

you need to create a revese lookup zone in your dns for supporting IPV6 sainath Windows Driver Development

_{Wednesday, March 18, 2009 8:41 AM}

dear

        can anyone explain some steps for resolve this problem
windows server and exchange server isa server problem

_{Wednesday, March 18, 2009 11:32 AM}

dear

        can anyone explain some steps for resolve this problem windows server and exchange server isa server problem

_{Friday, March 20, 2009 5:43 AM | 2 votes}

1.  Create reverse lookup zone for 192.168.0.X

2. Create PTR record for DNS server name and IP.

If you have this, you will be good to go.

_{Friday, March 20, 2009 6:41 AM}

 I already did this but still on server nslookup is not responding but on client its working good
windows server and exchange server isa server problem

_{Saturday, March 21, 2009 1:27 AM}

I still feel something is misconfigured. If you look at client response, it says abc instead of abc.mydomain.com. idly it should return with FQDN.

• Try to ping IP address along with -a syntax
  Ex - ping -a 192.168.0.1  - check what response you get? Check if you have multiple names associated with 192.168.0.1 IP address, if that's the case remove wrong records.

• When you type NSLOOKUP and hit enter, request goes to TCPIP stack, reads first IP address and try to do query for PTR record to get name which can be displayed at command prompt.

If you have third party app running on server, try to disable or remove it while testing.

_{Tuesday, May 29, 2012 1:16 PM | 1 vote}

yes bro its working because DNS is looking for 1st protocol IPV 6 only 

_{Tuesday, May 29, 2012 3:30 PM | 1 vote}

Just to point out, Microsoft does not recommend disabling IPv6 due to the operating system's underlying requirements of it and possibly breaking stuff.

The better way to do it is make IP4 the default by the following: Go in to the Network Connection screen. If the menu bar is not present, press the ALT button to display the menu. Then click on "Advanced" in the menu, then under it, "Advanced." Then change the binding order so that IPv4 is above IPv6. Reboot the server.  The default protocol will now be IPv4.

.

The Cable Guy - Support for IPv6 in Windows Server 2008 R2 and Windows 7, by Joseph Davies, Microsoft, Inc.
Quoted by Joseph Davies, MSFT:
"IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. "Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be."
http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspx 

.

Arguments against disabling IPv6
Demoire, [MSFT], 24 Nov 2010 12:37 AM
http://blogs.technet.com/b/netro/archive/2010/11/24/arguments-against-disabling-ipv6.aspx 

.

Should I disable IPv6? No. **Microsoft no longer recommendeds disabling IPv6. **
This article also contains information on how to Disable RSS TCP Chimney Feature and removing IPv6, if desired.
How to remove "::1" IPv6 DNS address that shows up in an ipconfg /all
How to change the Protocol order so IPv4 is the preferred protocol over IPv6
Published by Ace Fekay, MCT, MVP DS on May 27, 2010 at 10:43 AM  650  0
http://msmvps.com/blogs/acefekay/archive/2010/05/27/how-to-disable-rss-tcp-chimney-feature-and-ipv6.aspx

.

Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008/R2, Exchange 2007 & Exchange 2010, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

This post is provided AS-IS with no warranties or guarantees and confers no rights.

_{Saturday, November 2, 2013 10:50 AM}

The better way to do it is make IP4 the default by the following: Go in to the Network Connection screen. If the menu bar is not present, press the ALT button to display the menu. Then click on "Advanced" in the menu, then under it, "Advanced." Then change the binding order so that IPv4 is above IPv6. Reboot the server.  The default protocol will now be IPv4.

So what's the solution when IPv4 is already set to default i.e. above IPv6 in Adapters and Bindings (has been since server was installed) and yet still getting this 2 second timeout running NSLOOKUP and other stranage problems. For example, unable to validate forwarders when adding/editing them, but then the forwarder list shows correct name resolution and DNS appears to be working normally.

Adam@Regis IT

_{Wednesday, December 17, 2014 2:02 PM | 1 vote}

Thank you so muuuuuch!!!!!! This helped me a lot. I have been battling for days, trying to join my lab svr into my vm DC. aaaaaaah! Thank you 

nchiliza

_{Tuesday, June 23, 2015 3:11 PM}

I signed up to thank you. You save me a lot of time trying to know what was wrong.

Thank you very much

_{Thursday, July 23, 2015 6:47 PM}

I have done everything you have said and I am still getting this delay in nslookup…its driving me crazy. Any other ideas?

Thanks in advance,

Ray

_{Wednesday, August 12, 2015 2:28 PM}

Hey Ray, I found this issue and it didnt resolve my issue either. I ended up double checking my DNS servers on the NIC and they were off. Someone put in 10.244 instead of 10.243 for the IP address on the server for their DNS. Once I corrected that it started working fine. I also re-enabled my IPV6 re-tested and it worked also.

Hope that helps,

Matt

_{Tuesday, May 3, 2016 4:13 AM}

Dear Sir
Instead of disabling IPv6 from LAN Card Properties, you can change your interfaces settings form DNS Management Console:
Just go to properties of your server and under Interfaces tab change "listen on" option to "Only the following IP addresses" and uncheck IPv6 check box.

_{Wednesday, March 21, 2018 11:17 PM}

Hi Sir,

This Solution Works absolutely fine.

Thank you

Gows