Support for other processes having specific IP bound port 53 sockets along side a 0.0.0.0:53 bind

[ghost]

Not sure I'm describing this quite right.

Basically, I am trying to run a local resolver on say 127.0.0.1, port 53. I also want to have this dns library listen on all other, non-explicitly bound ports. When I try to start my resolver after this is running, it can't bind. If I start this after the resolver, it can't bind either.

However, gdnsd works along side it just fine. Is this a sideeffect of SO_REUSEPORT like in #654, or another socket option?

Appreciate any suggested workarounds, though I'd rather not have this dns library bind specific IPs.

For a code example, I'm calling this library from here: https://github.com/teran-mckinney/hostnameomatic/blob/master/hostnameomatic.go#L27

Thank you!

[ghost]

Hi,

Not sure why you closed this. Did you add support for SO_REUSESOCKET?

Thanks,

Teran