: One of our DNS servers is hosted by our old host and one by the new. The old doesn't have the correct values and can't be changed Because of misbehavior of our old hoster justhost.com, our

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 176.9.146.215.

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 74.220.195.44
ns2.kleinburdhost.com. 172800 IN A 69.89.16.124

Note that it has returned the wrong IPs.

These IPs are from their nameserver:

$ dig @74 .220.195.44 ns1.kleinburdhost.com
...
ns1.kleinburdhost.com. 60 IN A 74.220.199.15

$ dig @74 .220.195.44 kleinburdhost.com
...
kleinburdhost.com. 60 IN A 74.220.199.15

Note that two last dig queries to your nameserver return wrong IPs.

When resolving the IP for ns1.kleinburdhost.com the nameserver 74.220.195.44 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.

10.01% popularity Vote Up Vote Down

: When you move a site via a 301 redirect should you setup a robots.txt disallowing robots to crawl the old address? A site I am working on moved a subdomain to another subdomain via a 301

@Annie201

Posted in: #Redirects #RobotsTxt #Seo

3 Comments

: Adding Schema.org’s "WPHeader" with Microdata I'd like to add Schema.org data, and am trying to follow instructions given to me about how to do so. The instructions indicate that I should

@Annie201

Posted in: #Headers #Microdata #SchemaOrg #Seo

1 Comments

: Can't add preferred version to Google Webmasters / Search Console When I select example.com as my preferred site version like below. It gives me an error as seen in the image. The site was

@Annie201

Posted in: #GoogleSearchConsole

1 Comments

: Can a user or a crawler see the source of a page that has been redirected via a 301? Is it possible for a user or a web-crawler to see the contents/source code of a webdocument that is

@Annie201

Posted in: #301Redirect #Redirects #Seo #WebCrawlers

1 Comments

Login to post a comment!

1 Comments

Sorted by latest first Latest Oldest Best

@Chiappetta492

ns2.kleinburdhost.com is a glue inside .com registry, registered by eNom with IP 176.9.146.219, same for ns1 with IP 176.9.146.215

If this is not the IP you want you will need to go through eNom to make this value be changed at the registry. But this seems to be correct IPs now based on your question.

Note that using glues, why not super advanced DNS mastery, is still prone to errors, so this should be used carefully.

10% popularity Vote Up Vote Down

Feed

: One of our DNS servers is hosted by our old host and one by the new. The old doesn't have the correct values and can't be changed Because of misbehavior of our old hoster justhost.com, our

More posts by @Annie201

: When you move a site via a 301 redirect should you setup a robots.txt disallowing robots to crawl the old address? A site I am working on moved a subdomain to another subdomain via a 301

: Adding Schema.org’s "WPHeader" with Microdata I'd like to add Schema.org data, and am trying to follow instructions given to me about how to do so. The instructions indicate that I should

: Can't add preferred version to Google Webmasters / Search Console When I select example.com as my preferred site version like below. It gives me an error as seen in the image. The site was

: Can a user or a crawler see the source of a page that has been redirected via a 301? Is it possible for a user or a web-crawler to see the contents/source code of a webdocument that is

Login to post a comment!

1 Comments

Back to top | Use Dark Theme