[SOLVED] ns1/ns2.niftyhost.us stopped working

[Piotr GRD]

Hi

At the moment for ns1/ns2.niftyhost.us there are following DNS records:

Code:

ns1.niftyhost.us.    30    IN    CNAME    NS1.MAXIMUMHOST.NET.
ns2.niftyhost.us.    30    IN    CNAME    NS2.MAXIMUMHOST.NET.

and while ns1/ns2.maximumhost.net did point correctly to the 72.55.147.241 IP everything worked fine.

However yesterday maximumhost.net domain name has expired. So the registrar did change the DNS records for this domain name and obviously ns1/ns2.maximumhost.net do NOT point to 72.55.147.241 IP anymore and because of this ns1/ns2.niftyhost.us do not point in there, either. DNS change of above mentioned CNAME's at CloudFlare is required.

Piotr GRD

[trainhappy]

Hello,
Yes it does appear ns2.niftyhost.us stoped working. However, ns1.niftyhost.us is working. Did you try clearing your dns and chache?

Code:

ipconfig /flushdns

[Piotr GRD]

@ trainhappy
Did you note that I have posted my warning 9 and a half days before your answer?... : )


----------------------------------

Anyway...
Within ~16-17 hours after my previous post the DNS records has been change. At the moment (for over 12 days already) there are following records:

Code:

ns1.niftyhost.us.    300    IN    CNAME    NS1.supremebytes.com.
ns2.niftyhost.us.    300    IN    CNAME    NS2.supremebytes.com.

which points ns1 and ns2.niftyhost.us to 64.191.78.120 and 199.115.229.24

These two nameservers are functional and works, though do not return any records for the domain names hosted on 72.55.147.241 (at least not for these domain names that I know about).

The DNS server on 72.55.147.241 itself works fine, so in my opinion this should be enough to change the mentioned above CNAME's into:

Code:

ns1.niftyhost.us.    300    IN    A    72.55.147.241
ns2.niftyhost.us.    300    IN    A    72.55.147.241

and everything should work again just like it worked before maximumhost.net domain has expired.

Unless the 72.55.147.241 server and domains hosted on it are not maintained anymore or I don't know about some other changes, other servers etc.

[HiddenKnowledge]

Just confirming, this is solved, right?

[Serial Thrilla]

Yes, this is solved :).

I tested it on my domain and it works.