Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Incidents
[Top] [All Lists]

RE: Win2k Machine contacting Root Server???

Subject: RE: Win2k Machine contacting Root Server???
Date: Fri, 24 Mar 2006 04:49:18 -0500
I believe you will find there is a setting that tells a Win2k server to try TCP 
if UDP fails for DNS resolution. Maybe the UDP was failing and the box was 
doing as it was told.


-----Original Message-----
From:   Alex [mailto:incidents@alex.gotdns.org]
Sent:   Fri 3/24/2006 1:53 AM
To:     incidents@securityfocus.com
Cc:     
Subject:        Win2k Machine contacting Root Server???

Hi,

I recently ran "netstat" on my personal laptop (running Win2k) and was 
shocked to see that it had been making TCP connections to the root servers 
(to their domain port). I know that some DNS queries are performed using 
TCP, but I find it somewhat disturbing that the root servers were 
involved.

I did a little googling and found a few remarks that Win2k machines 
sometimes do this...   But mine has the lastest updates....

So I'm a little concerned.  Is this normal operation for a win2k machine, 
or could something more amiss be going on?    Norton Antivirus and SpyBot 
Search & Destory didn't find anything wrong.

Thanks

-Alex

(I realize this is probably a normal thing,  but I still find it 
disturbing)




<Prev in Thread] Current Thread [Next in Thread>