This looks like a typical DNS cache poisoning attack[1], which takes advantage of insecure DNS caching servers. Users of those caching servers will be sent to the wrong IP, so it is a successful attack of sorts. But there isn't much the target website can do to prevent it.