Ask HN: Vultr resolving non-existent domains?

1 point

7 years ago

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!

7 comments