Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

NsLookup Issues - Time out


  • Please log in to reply
1 reply to this topic

#1 jeremy450

jeremy450

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:39 PM

Posted 23 December 2015 - 01:48 PM

Hi there

I just setup a Server 2008 R2 with AD and i'm having Nslookup issues. Before i setup AD i wasnt having any issues at all with NsLookup. but since AD been setup its erroring out. IPv6 is disabled. i have tried running "dnscmd /config /EnableEDNSProbes 0" with no luck i have tried " ipconfig /flushdns" and "ipconfig /registerdns" and also disabled all windows firewalls. i'm lost and cos of this i cant setup exchange server, etc. As i said before i setup AD it was working fine. info is below.

Results

PS C:\Users\Administrator> nslookup google.com
Server: server-ad-exc.interline.net.au
Address: 192.168.0.240

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4006:801::200e
216.58.220.110

Adaptor info

PS C:\Users\Administrator> ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SERVER-AD-EXC
Primary Dns Suffix . . . . . . . : interline.net.au
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : interline.net.au

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapte
Physical Address. . . . . . . . . : 00-15-5D-00-01-07
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.240(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.240
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{1C774D1A-3B7C-4EC6-9C9E-F0283E2B2263}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP
Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP
Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Ping Results

PS C:\Users\Administrator> ping google.com

Pinging google.com [216.58.220.110] with 32 bytes of data:
Reply from 216.58.220.110: bytes=32 time=58ms TTL=54
Reply from 216.58.220.110: bytes=32 time=58ms TTL=54
Reply from 216.58.220.110: bytes=32 time=58ms TTL=54
Reply from 216.58.220.110: bytes=32 time=58ms TTL=54

Ping statistics for 216.58.220.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 58ms, Average = 58ms



BC AdBot (Login to Remove)

 


#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,255 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:39 PM

Posted 25 December 2015 - 11:03 AM

Are you having this issue with only external nslookups? I see your DC is referencing itself for DNS information.

 

Make sure the DC has a connection to the Internet. Check you DNS configuration on the DC to make sure root hints are there. If anything, configure a forwarder for all external DNS lookups to point to your ISP's DNS server(s).






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users