-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No updates since June 5th 2017 #11
Comments
Nah, the script is broken and I just haven't had time to fix it yet - will diagnose this weekend and hopefully get it working again! |
that would be great, thanks!
El divendres, 16 de juny de 2017, Matthew Bryant <notifications@github.com>
va escriure:
… Nah, the script is broken and I just haven't had time to fix it yet - will
diagnose this weekend and hopefully get it working again!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEXHlZ_Glka25ZVRQQVhtgq_MQMab2kpks5sEq-CgaJpZM4N468G>
.
--
Enviat amb Gmail Mobile
|
Alright so the cause of this one is actually pretty funny (and is now fixed). Turns out Russia accidentally enabled global zone transfers on two of their core TLD nameservers and the resulting zone data was so big (850+ megabytes of raw zone text!) it filled up all available RAM and caused the program to immediately die. I've done two things to address this:
Hopefully no TLDs will have over 100MB post-gziped zone data. That will hit the limits of Github and may require this project to be moved somewhere else. This whole thing is due for a massive rewrite anyways so I'll add that to my TODO list as well. Thanks for reporting! |
Haha, thanks so much! Look what I found in the .RU zone: https://twitter.com/pforemski/status/876737428307968000 :) |
Hi, I can't see any changes since June 5th, did everyone fix their DNS servers? :)
The text was updated successfully, but these errors were encountered: