12 replies

Not able to connect with WARP due to "port 53 bound"

Hi, I see this issue has been referred many times, but I don't find a good solution yet. I feel there must be a lot of people using WARP on macOS, so I'm wondering how people get around this.

Symtom:
Not able to connect via WARP, got error message "port 53 bound"

mDNSResponder

mDNSResponder

is taking the port 53, I've tried to kill it via

sudo killall -HUP mDNSResponder

sudo killall -HUP mDNSResponder

but that didn't work. Another thing is I believe

mDNSResponder

mDNSResponder

is used for device discovery which is probably depended by many core services (like Airdrop, continuity features?). So, I'm not sure if I really want to sacrifice the feature just to be connected with WARP (I feel there is a better way to handle this)

Help needed