port 53 would not cause this issue as far as I kno...
# macos
j
port 53 would not cause this issue as far as I know