Issue

[mghq]

Today we experienced an issue. The server itself never went offline however named did. This is what controls nameservers. So if you were using ns1.niftyhost.us and ns2 then your sites appeared down however people using A records like me had sites remain up. So in the end the server never technically went offline.

[Lance]

Ah okay

[mghq]

Yea, i got notified that one of the domains i monitor went down but my other stayed up...

[Piotr GRD]

Am I the only person that found (still continuous) problem with FTP connection since the beginning of this issue?

[Zach]

How do you mean when you say "issues"? FTP may have tripped up when DNS failed.

[Zach]

Oh, haha... I see what you mean when you say issue. Try SFTP for the time being, ok?

[Matt]

Ah, a nameserver daemon failure. Jeez, those are annoying :P

Cheers for responding to the issue in time ;)

[mghq]

Yea, it happened during the middle of the night while I was asleep

[Piotr GRD]

Oh, haha... I see what you mean when you say issue. Try SFTP for the time being, ok?

mghq wrote "issue", so I'm following this. ;)

I do not need to use FTP, but thank you for suggestion. My question was: is this only me having problem with FTP (but I've checked from two different locations so most probably no) or is this global and possibly unnoticed problem on NiftyHost end? If it's for some reason only on my end - I would need to do something with my server monitor.

And my monitoring is DNS independent, I have IPs fixed for it, I'm monitoring servers and access to them, not the functionality of DNS system, otherwise even failure of nameservers at my own ISP could affect the results.

[Zach]

Well, the server was up via IP while the nameservers were out. And mghq is ignoring the FTP issue and not allowing me to fix it for some reason...