Socket option SO_INCOMING_CPU is set incorrectly to CPU 1

Summary

Socket option SO_INCOMING_CPU is set incorrectly to CPU 1 on certain sockets.

BIND version affected

Steps to reproduce

Run named on a platform that supports the SO_INCOMING_CPU socket option (e.g. Linux).

What is the current bug behavior?

Linux is instructed to process incoming packets on CPU 1.

What is the expected correct behavior?

Linux should be instructed to process incoming packets on the same CPU as named, or the option should not be set.

Relevant configuration files

None, it is enabled by default in the build.

Relevant logs

None.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information