[Bug]: dvl.to cannot be resolved
ilianiv opened this issue · 8 comments
Have you already looked into this bug?
- I have checked the Troubleshooting Guide
- I have checked Release notes for potential migration steps
- I have checked existing issues for similar bugs
- I have googled this bug already with no luck
- 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
The problem is not hereConfig: docker-compose.override.yml
No response
Config: ./check-config.sh
The problem is not hereLog: docker-compose logs
The problem is not here(Optional) Additional information
No response
Looks like the dvl.to domain has expired. I've registered and set DNS on the slightly cheaper dbox.dev, feel free to use it 🙂 (note .dev domains are https only).
Looks like the dvl.to domain has expired. I've registered and set DNS on the slightly cheaper dbox.dev, feel free to use it 🙂 (note .dev domains are https only).
How you make this type of domain ?
Oh, is this what happened? I noticed about a month ago that none of my dvl.to domains were resolving anymore unless I put them manually in my windows hosts file (as you had to prior to the v3 beta)
e.g.
How can we make use of dbox.dev?
Is this the cause for very slow connectivity to other domains? I'm running Devilbox on a M1-MacBook and feel that as soon as I add the Devilbox DNS looking up other domains becomes very slow.
Another popular alternative is localtest.me
dbox.dev doesn't work for me, but localtest.me does.
In case anyone is wondering how to use this, you have to change this in the devibox .env file.
#TLD_SUFFIX=dvl.to
TLD_SUFFIX=localtest.me
I then had some issues with some of my domains, so followed the official troubleshooting steps to recreate the containers. I still had some issues so restarted the WSL2 instance, as well as did an empty cache and hard refresh for the domains in the browser.
Just for more alternatives, I'm using localhost.tv which works like a charm. Perhaps a list of possible alternatives in the .env template could make this even easier.
Examples in the .env would be good. But the project seems to be abandoned...