Playing

[Lazybones]

Odd that my other monitors seem to be correct? Any firewall changes on your end?

[Tom]

Odd that my other monitors seem to be correct? Any firewall changes on your end?

No firewalls on those boxes. also it only seems to be affecting those two minecraft boxes. its really strange.

[Lazybones]

Ya it is odd I was monitoring the Overviewer URLs as well and they where worse

[Tom]

Ya it is odd I was monitoring the Overviewer URLs as well and they where worse

Supposedly /some/ of their monitoring boxes were overtaxed. It could explain the oddness. But it may not. I complained to DigitalOcean first, and they found/saw nothing. I also see nothing in the server logs related to any of this. And I've gotten downtime warnings when actually connected to minecraft.

[Tom]

I was playing more last night and this happened:


(I got distracted...)

[IDK]

I was hoping on hoppin on but it seems down for me.

[Tom]

I was hoping on hoppin on but it seems down for me.

Which server? And which version of minecraft were you trying to use? I was just on Planet Bob which is 1.7.2 (so you need to use 1.7.2).

[IDK]

mc2.tomasu.org with 1.7.2

[Tom]

yeah, I was just on there. And just tried connecting again, it seems to work fine.

[Tom]

What happens if you try mc2.svc.tomasu.net or 107.170.226.228 ?

[Lazybones]

Hi Tom I think the problem with both the monitoring and server access are your DNS records

http://dnscheck.pingdom.com/?domain=mc2.tomasu.org&timestamp=1409977929&view=1

I ran some tests from http://mxtoolbox.com as well your DNS is buggered in some way.

[IDK]

Lazybones noted to try accessing it by just inputting the IP.  That worked.

Thanks

[Tom]

Hi Tom I think the problem with both the monitoring and server access are your DNS records

http://dnscheck.pingdom.com/?domain=mc2.tomasu.org&timestamp=1409977929&view=1

I ran some tests from http://mxtoolbox.com as well your DNS is buggered in some way.

The dnscheck error is spurious, its checking a zone, but mc2.tomasu.org is a record, not a zone.

That said, it made me look harder, and svc.tomasu.net IS a zone (and mc*.tomasu.org are CNAMEs to mc*.svc.tomasu.net), and I checked that, and it's settings weren't exactly correct... So if this doesn't fix it, I have no bloody clue what it is.

[Lazybones]

Hi Tom I think the problem with both the monitoring and server access are your DNS records

http://dnscheck.pingdom.com/?domain=mc2.tomasu.org&timestamp=1409977929&view=1

I ran some tests from http://mxtoolbox.com as well your DNS is buggered in some way.

The dnscheck error is spurious, its checking a zone, but mc2.tomasu.org is a record, not a zone.

That said, it made me look harder, and svc.tomasu.net IS a zone (and mc*.tomasu.org are CNAMEs to mc*.svc.tomasu.net), and I checked that, and it's settings weren't exactly correct... So if this doesn't fix it, I have no bloody clue what it is.

well at the very least a 10min TTL is really low unless that is a dynamic ip

[Tom]

Hi Tom I think the problem with both the monitoring and server access are your DNS records

http://dnscheck.pingdom.com/?domain=mc2.tomasu.org&timestamp=1409977929&view=1

I ran some tests from http://mxtoolbox.com as well your DNS is buggered in some way.

The dnscheck error is spurious, its checking a zone, but mc2.tomasu.org is a record, not a zone.

That said, it made me look harder, and svc.tomasu.net IS a zone (and mc*.tomasu.org are CNAMEs to mc*.svc.tomasu.net), and I checked that, and it's settings weren't exactly correct... So if this doesn't fix it, I have no bloody clue what it is.

well at the very least a 10min TTL is really low unless that is a dynamic ip

It was on a dynamic ip. But I've upped it to a day. should be ok. except now changes wont be seen for a day...