Because of misbehavior of our old hoster justhost.com, our domains including victorporton.com do not act as they should.
But justhost.com ignores our queries saying that they can't help because our account with them is terminated. (They forgot to remove our DNS information, however.)
The correct IP to which the DNS must point is 220.127.116.11.
I wrote to Verisign asking to take an action against justhost, but my email was not answered. What else can be done?
Below there is a description of technical conditions:
Our nameservers are pointing to ns1.kleinburdhost.com and ns2.kleinburdhost.com.
When we try to resolve the domain victorporton.com the following happens:
$ dig @a.gtld-servers.net victorporton.com
ns1.kleinburdhost.com. 172800 IN A 18.104.22.168
ns2.kleinburdhost.com. 172800 IN A 22.214.171.124
Note that it has returned the wrong IPs.
These IPs are from their nameserver:
$ dig @126.96.36.199 ns1.kleinburdhost.com
ns1.kleinburdhost.com. 60 IN A 188.8.131.52
$ dig @184.108.40.206 kleinburdhost.com
kleinburdhost.com. 60 IN A 220.127.116.11
Note that two last dig queries to your nameserver return wrong IPs.
When resolving the IP for ns1.kleinburdhost.com the nameserver 18.104.22.168 uses its parent server kleinburdhost.com (which has a wrong IP in this response) and when resolving the IP for kleinburdhost.com it uses the nameserver ns1.kleinburdhost.com or ns2.kleinburdhost.com (which also have wrong IPs in this response).
Thus it happens a vicious circle: The top level domain servers such as a.gtld-servers.net use nameservers ns1.kleinburdhost.com or ns2.kleinburdhost.com with wrong IPs to resolve kleinburdhost.com and to resolve ns1.kleinburdhost.com or ns2.kleinburdhost.com servers it uses their parent kleinburdhost.com with wrong IPs is used. This leads to the fact that both ns1.kleinburdhost.com, ns2.kleinburdhost.com, and kleinburdhost.com are queried with wrong IPs.