5 ms·
Ask HN: Vultr resolving non-existent domains?
Hello, everyone! By chance, I happened to notice that my vultr server, and many new ones deployed solely to test this, resolve non-existent domains as long as the hostname and label end in some TLD (tested .com, .net and .org). This issue does not happen for dotless or blank hostnames.
For instance:
$ ping sjdisdji.net
PING sjdisdji.net.net (34.250.90.28): 56 data bytes
$ ping doasidjaoidja8dy78y7ahduh.org
PING doasidjaoidja8dy78y7ahduh.org.net (23.23.86.44): 56 data bytes
The seemingly random resolution also happens with some CC TLDs, such as uk, fr, ar. Depending on the server it may or may not resolve .com or .org. It happens at least with OpenBSD 6.4, Ubuntu 18.10, and at least choosing London or Amsterdam.
I reported this (OTH-21BCZ) and was pretty disappointed with their response. First they asked me whether the issue persisted upon changing `/etc/reolv.conf` to
nameserver 8.8.8.8
nameserver 8.8.4.4
It did, and their conclusion was that "This is an issue with software running on your instance and not the infrastructure. I have been unable to reproduce this issue on my end on my own instances." Just to be clear, I tried this all on brand new deploys, with nothing on them, so I can't conceive how this could be "an issue with software running on my instance"...
Can you guys check if you see the same thing? If so, please let me know your location and OS.
Thank you very much in advance!
- anonymousiam 8y agoWho is your ISP? Are they redirecting the above google DNS servers to their own? This would be trivial with just a few routing rules.
- ezequiel-garzon 8y agoMy ISP is actually a cell phone carrier in Spain, but I should point out these pings are performed via ssh in the vultr servers. How would my ISP be relevant to this issue?
- wahern 8y agoWhat's in /etc/resolv.conf?
- ezequiel-garzon 8y agoOriginally # Generated by vio0 dhclient nameserver 108.61.10.10 lookup file bind Then I tried nameserver 8.8.8.8 nameserver 8.8.4.4 and nameserver 8.8.8.8 nameserver 8.8.4.4 lookup file bind These changes I only tried on my stable server, running OpenBSD 6.4.
- wahern 8y agoHere's what I get from vultr's Santa Clara location: $ host sjdisdji.net 108.61.10.10 Using domain server: Name: 108.61.10.10 Address: 108.61.10.10#53 Aliases: Host sjdisdji.net not found: 3(NXDOMAIN) $ host doasidjaoidja8dy78y7ahduh.org 108.61.10.10 Using domain server: Name: 108.61.10.10 Address: 108.61.10.10#53 Aliases: Host doasidjaoidja8dy78y7ahduh.org not found: 3(NXDOMAIN)
- ezequiel-garzon 8y agoThanks a lot for replying, and for taking the time. Is your server’s hostname a FQDN? Edit: I just checked, it doesn’t do this with host, but it does with ping. What about ping?
- ezequiel-garzon 8y agoUpdate: I left the issue open a couple days and the Vultr support team has said they were able to reproduce the issue under some circumstances and they will look into it. Now I feel more sane!