[Bug]: dvl.to cannot be resolved

### Have you already looked into this bug?

- [X] I have checked the [Troubleshooting Guide](https://devilbox.readthedocs.io/en/latest/support/troubleshooting.html)
- [X] I have checked [Release notes](https://github.com/cytopia/devilbox/releases) for potential migration steps
- [X] I have checked [existing issues](https://github.com/cytopia/devilbox/issues) for similar bugs
- [X] I have googled this bug already with no luck
- [X] I have not done any of the above

### (Optional) Error message

_No response_

### What went wrong?

`dvl.to` domain cannot be resolved

### Expected behaviour

`dvl.to` domain be resolvable

### How can we reproduce the bug?

```
$ ping dvl.to
ping: dvl.to: Name or service not known
```

or

https://dnschecker.org/#A/dvl.to
https://mxtoolbox.com/SuperTool.aspx?action=a%3advl.to&run=toolpage

### Host Operating System

Linux

### Host Platform (amd64, arm64, other)

amd64

### (Linux only) Is SELinux enabled?

Yes, SELinux is enabled

### Docker version

24

### Docker Compose version

2

### Devilbox version

3.0.0

### Have you removed stopped containers before starting?

Yes

### Have you pulled latest Docker images before starting?

Yes

### Devilbox start command

docker compose up -d php bind memcd httpd

### Config: .env file

```shell
The problem is not here
```

### Config: docker-compose.override.yml

_No response_

### Config: ./check-config.sh

```shell
The problem is not here
```

### Log: docker-compose logs

```shell
The problem is not here
```

### (Optional) Additional information

_No response_