Why does DNS.EXE listen on a ephemeral TCP port?
- From: "Brian K. Doré" <bkd@xxxxxxxxxxxxx>
- Date: Sun, 3 Sep 2006 18:23:00 -0500
I noticed my x64 Windows 2003 R2 machines running DNS were listening on
wierd TCP ports. DNS.EXE is the listening process. Restarting DNS changes
the port number. I know DNS uses ephemeral UDP ports, but I can't find
anything that describes the use of TCP in this manner. None of the
Microsoft firewall guides I've seen make allowances for this port to be
used, nor does anything in the security configuration wizard indicate that
inbound TCP connections should be allowed to anything other than 53.
Does anyone know what it's for and how it's used?
Brian
Brian Doré
Office of Information Systems
University of Louisiana at Lafayette
.
- Follow-Ups:
- Re: Why does DNS.EXE listen on a ephemeral TCP port?
- From: Ace Fekay [MVP]
- Re: Why does DNS.EXE listen on a ephemeral TCP port?
- Prev by Date: Re: DNS without Active Directory?
- Next by Date: Re: DNS without Active Directory?
- Previous by thread: DNS hosting software
- Next by thread: Re: Why does DNS.EXE listen on a ephemeral TCP port?
- Index(es):
Relevant Pages
|