# client: Fix an issue where non-IP proxy URLs didn’t resolve correctly \(\#32664\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/bc68455320f1be3f3a135ea1c0de24c026990286)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: bc68455320f1be3f3a135ea1c0de24c026990286

Requested commit: bc68455320f1be3f3a135ea1c0de24c026990286

Commit: bc68455320f1be3f3a135ea1c0de24c026990286

Tree: ea00b9a16f24c40a6154d7f5c0e74b1f908de158

Author: 张小白

Committer: GitHub

## Message

```
client: Fix an issue where non-IP proxy URLs didn’t resolve correctly (#32664)

If the proxy URL is in the form of `example.com` instead of a raw IP
address, and `example.com` isn't a well-known domain, then the default
URL resolution can fail.

The test setup:

A Linux machine runs a CoreDNS server with a custom entry: `10.254.7.38
example.com`. On a Windows machine, if the proxy URL is set to
`example.com`, the resolved address does **not** end up being
`10.254.7.38`.

Using `hickory_resolver` for more advanced DNS resolution fixes this
issue.


Release Notes:

- Fixed proxy URL resolution when using custom DNS entries.
```

## Parents

- [20793fc251df78e035761b6d9232a5ab6ebb4f23](https://git.cafe/gitcafe/zed/commit/20793fc251df78e035761b6d9232a5ab6ebb4f23?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/bc68455320f1be3f3a135ea1c0de24c026990286?format=markdown)