I've set up a better SURBL name server status page at:
http://www.surbl.org/nameservers-output.html
which is also linked from the main page.
It shows some latency in zone file propagation, and it also shows one of the name servers down. (Bjorn is that coming back eventually?)
We may want to ask all the public name servers to rsync every 10 minutes.... Would that be OK Raymond?
Currently I have the DNS timeout set to 10 seconds with two retries. What kind of values are more typical or standard for resolvers?
I will use the scripts that generate the page to send notifications (probably to myself at first) once things stabilize. Since events don't happen very often, it's probably not necessary to show a history on the page.
Comments?
Jeff C.
On Tuesday, August 24, 2004, 4:43:33 AM, Jeff Chan wrote:
Currently I have the DNS timeout set to 10 seconds with two retries. What kind of values are more typical or standard for resolvers?
I should add that the queries are non-recursive and require authority. Non-authoritative responses will show up in red as "Not Authoritative".
Jeff C.
OK I can already see I'll need to rethink this. Any time a new zone file is more than two hours newer than the previous version, there would be an alarm.
Obviously that's not the right logic since the name servers can't update at exactly the same time, and there can legitimately be periods longer than an hour or two of no new data.
Jeff C.
Hi!
OK I can already see I'll need to rethink this. Any time a new zone file is more than two hours newer than the previous version, there would be an alarm.
;)
Obviously that's not the right logic since the name servers can't update at exactly the same time, and there can legitimately be periods longer than an hour or two of no new data.
I updated the reload interval for 130.161.128.108 and 130.161.128.109, those are synced up faster, lets try to at least get a 'green' page the next comming days and contact the server admins to check if they can also raise the interval on their end.
Bye, Raymond.