Share via

DNS SocketPoolSize Update

Anonymous
2025-02-04T09:51:47+00:00

Hello,

On Windows 2016 domain controllers, the Best Practices Analyzer reports that the value configured for the SocketPoolSize dns (currently 312) is below Microsoft standards.

When attempting to change this value to 2500 via the command “dnscmd /config /socketpoolsize 2500” and restarting the DNS Server service, the service restarts, resetting the value to 312. I don't know how to correct this problem.

Thanks for your help.

Best regards,

Abraham Gaou KOIVOGUI

Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-02-05T07:36:28+00:00

    Hello,

    The SocketPoolSize registry is created automatically with a value lower than default when system TCP/UDP Dynamic Port range is too small

    Default value of socket pool size in DNS parameters is 2500 and it does not show by default on the registry. In this case, the registry key was created on its own and kept changing to a lower value:

    HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters\SocketPoolSize

    Use NETSH to reset the system TCP/UDP Dynamic to its default value based on the OS version

    netsh int ipv4 set dynamicport tcp start=49152 num=16384

    netsh int ipv4 set dynamicport udp start=49152 num=16384

    Best Regards

    ZUnhui

    Was this answer helpful?

    0 comments