maybe adverseAddr should be used in some places insted of masterAddr

[nexustar]

What did you do?

I try to use DM with TLS (with --masterAddr=0.0.0.0:8261), but worker cannot connect to master, master log shows

[grpclog.go:42] ["grpc: addrConn.createTransport failed to connect to {0.0.0.0:8261  <nil> 0 <nil>}. Err: connection error: desc = \"transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, 192.168.122.25, not 0.0.0.0\". Reconnecting..."] [component="embed etcd"]

It works after I add 0.0.0.0 to alt_names of cert, bit I think it should not be necessary

Then I search the code, I found somewhere, masterAddr was used as endpoint. maybe adverseAddr should be used instead. For example: https://github.com/pingcap/tiflow/blob/master/dm/dm/master/server.go#L214

related issue: pingcap/dm#966

What did you expect to see?

No response

What did you see instead?

No response

Versions of the cluster

v2.0.7 v5.3.0

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)