Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > Is This Normal DNS Behavior on a Server2003 SP2 Domain Controller

Reply
Thread Tools Display Modes

Is This Normal DNS Behavior on a Server2003 SP2 Domain Controller

 
 
mcintoshs
Guest
Posts: n/a

 
      07-18-2009

On all server 2003 SP2 domain controllers, when I run the netstat -ano
command, I see that the dns.exe process is listening on hundreds of ports
between the port range of 49178 to 65533. Is this normal?

If not, how do I address this?
Thanks,
Scott
 
Reply With Quote
 
 
 
 
Ace Fekay [MCT]
Guest
Posts: n/a

 
      07-18-2009
"mcintoshs" <> wrote in message
news:CD64141D-8C5F-4928-93BA-...
> On all server 2003 SP2 domain controllers, when I run the netstat -ano
> command, I see that the dns.exe process is listening on hundreds of ports
> between the port range of 49178 to 65533. Is this normal?
>
> If not, how do I address this?
> Thanks,
> Scott



Yep, it is, because of the DNS update from 7/2008. Read the following for an
explanation:

================================================== ================================================== ==
The DNS Exploit patch explained
By Ace Fekay, MCT
Last updated: 9/2008
---

Protection against the Microsoft DNS Cache Poisoning Vulnerability (953230)

The DNS patch released in July, 2008, reserves 2500 ephemeral UDP ports.

It is a security update to prevent spoofing. Attackers know that normally,
without the update, a random ephemeral response ports (service ports), which
is normally UDP 1024 and above. They are the response ports used by all
Windows communications (not just DNS). An attacker may guess/randomize a
port attack at DNS attempting to gain access to create records into the DNS
Cache, by injecting records using specially crafted commands, therefore
poisoning the DNS cache with records of their choosing, which will allow a
remote attacker to redirect legitimate network traffic intended for systems
on the Internet to the attacker's own systems or elsewhere, of their
choosing.

By reserving the port, or creating this socket pool, it reduces the chance
of a randomization attack, which attackers are using against Windows and
other major DNS services, to prevent Cache Poisoning.

When you run a netstat -ab, it will display the 2500 UDP ports that have
been reserved, but not necessarily in use. This is part of the increased
memory consumption that you may. I've noticed the following (your mileage
may vary):

dns.exe Before After
Mem usage 9,758K 36,232K
Peak Mem 10,208K 36,584K
Paged Pool 71K 798K
NP Pool 17K 4,833K
Handles 238 5,217
Threads 20 20

MS08-037: Description of the security update for DNS in Windows Server 2003,
in Windows XP, and in Windows 2000 Server (client side): July 8, 2008:
http://support.microsoft.com/?id=951748

MS08-037: Vulnerabilities in DNS could allow spoofing
http://support.microsoft.com/default.aspx/kb/953230

How to reserve a range of ephemeral ports on a computer that is running
Windows Server 2003 or Windows 2000 Server
http://support.microsoft.com/kb/812873

You experience issues with UDP-dependent network services after you install
DNS Server service security update 953230 (MS08-037)
http://support.microsoft.com/default.aspx/kb/956188

Some Services May Fail to Start or May Not Work Properly After Installing
MS08-037 (951746 and 951748)
http://blogs.technet.com/sbs/archive...nd-951748.aspx

SBS Services failing after MS08-037 - KB951746 and 951748
http://msmvps.com/blogs/thenakedmvp/...nd-951748.aspx

There can also be issues with various applications installed and running on
a DNS server where the RPC Endpoint Mapper has run out of ports to use
because all available ports are being consumed by the app:

It sounds like you're running out of available ports for the RPC endpoint
mapper to use. Take a look at the following article:

839880 Troubleshooting RPC Endpoint Mapper errors using the Windows Server
2003 Support Tools from the product CD
http://support.microsoft.com/default...b;EN-US;839880

Run "netstat -ano" in a command line. It should provide a listing of ports
that are in use as well as the PID of the process that owns that port.
Possibly you're running an application on this server that isn't releasing
ports when it's done with them. You can also extend the available ports
used by RPC but I'd recommend looking into what's consuming them first.
================================================== ================================================== ==

--
Ace

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

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

 
Reply With Quote
 
Ace Fekay [MCT]
Guest
Posts: n/a

 
      07-18-2009

"Ace Fekay [MCT]" <> wrote in message
news:OZGA%...

After re-reading my post and blog, it appears I've never proofed it. I
re-worded it to make better sense, and have re-posted it below. Sorry about
the incovenience.

================================================== ================================================== ==
The DNS Exploit patch explained
By Ace Fekay, MCT
Last updated: 7/2009
---

Protection against the Microsoft DNS Cache Poisoning Vulnerability (953230)

The DNS patch released in July, 2008, reserves 2500 ephemeral UDP ports.

It is a security update to prevent spoofing. Attackers know that normally,
without the update, a random ephemeral response port (service port), which a
port is chosen randomly using UDP 1024 and above, is used in response to the
querying client resolver. These response or service ports, are used by all
Windows communications (not just DNS). An attacker may guess/randomize a
port attack at DNS attempting to gain access to create records into the DNS
Cache, by injecting records using specially crafted commands, therefore
poisoning the DNS cache with records of their choosing, which will allow a
remote attacker to redirect legitimate network traffic intended for systems
on the Internet to the attacker's own systems or elsewhere, of their
choosing.

By pre-reserving the port, or creating a socket pool, as the DNS patch
performs, reduces the chance of a randomization attack, which attackers are
using against Windows and other major DNS services, to prevent Cache
Poisoning.

When you run a netstat -ab, it will display the 2500 UDP ports that have
been reserved, but not necessarily in use. This is part of the increased
memory consumption that you may notice. I've noticed the following when I've
looked at Task Manager before and after the DNS patch was installed (your
mileage may vary):

dns.exe Before After
Mem usage 9,758K 36,232K
Peak Mem 10,208K 36,584K
Paged Pool 71K 798K
NP Pool 17K 4,833K
Handles 238 5,217
Threads 20 20
---

More info on the patch and the DNS exploit issue is explained in the
following links.

MS08-037: Description of the security update for DNS in Windows Server 2003,
in Windows XP, and in Windows 2000 Server (client side): July 8, 2008:
http://support.microsoft.com/?id=951748

MS08-037: Vulnerabilities in DNS could allow spoofing
http://support.microsoft.com/default.aspx/kb/953230

How to reserve a range of ephemeral ports on a computer that is running
Windows Server 2003 or Windows 2000 Server
http://support.microsoft.com/kb/812873

You experience issues with UDP-dependent network services after you install
DNS Server service security update 953230 (MS08-037)
http://support.microsoft.com/default.aspx/kb/956188

Some Services May Fail to Start or May Not Work Properly After Installing
MS08-037 (951746 and 951748)
http://blogs.technet.com/sbs/archive...nd-951748.aspx

SBS Services failing after MS08-037 - KB951746 and 951748
http://msmvps.com/blogs/thenakedmvp/...nd-951748.aspx

---
There can also be issues with various applications installed and running on
a DNS server where the RPC Endpoint Mapper has run out of ports to use
because all available ports are being consumed by the app. If this is the
case, it could be that the system is running out of available ports for the
RPC endpoint mapper to use.

Run "netstat -ano" in a command line. It should provide a listing of ports
that are in use as well as the PID of the process that owns that port.
Possibly you're running an application on this server that isn't releasing
ports when it's done with them. You can also extend the available ports
used by RPC but I'd recommend looking into what's consuming them first.

Take a look at the following article for more info on the Endpoint mapper:

839880 Troubleshooting RPC Endpoint Mapper errors using the Windows Server
2003 Support Tools from the product CD
http://support.microsoft.com/default...b;EN-US;839880
================================================== ================================================== ==

Ace



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Annoying 360 Some of you may know that I got a virus a few days ago (it's gone now) and it's messed up a few things. One of these things being my xbox 360 controller. Before, all the buttons on the controller did the normal thcontroller problem Bob Windows Vista Hardware 0 09-20-2009 01:44 AM
Normal PDC Emulator behavior? (time related) Jorge d''Argence Windows Server 0 03-22-2006 04:40 PM
Normal PDC Emulator behavior? (time related) Jorge d''Argence Active Directory 0 03-22-2006 04:16 PM
2003 SBS--Odd or Normal Behavior?? JJPomraning Windows Small Business Server 3 10-05-2005 08:45 AM
win98 cant se server2003 domain controller dave Active Directory 11 01-22-2004 05:39 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59