On 22/09/2010 19:56, Pete Carah wrote: > My unbound resolver was unable to resolve RIPE reverse addresses for > most of yesterday (flagging all queries for xxx.in-addr.arpa. in ripe > zones as key expired) until I had flushed the cache several times and > finally stopped and restarted unbound. I didn't notice this with any of > my bind instances. I don't know if this is a unbound error, or a > problem with the way that RIPE introduced their new key (or an > interaction of both?)...
Hello Pete, We had some problems yesterday with some of our signed zones, and we've posted an announcement about it here: http://www.ripe.net/news/status.html Regards, Anand Buddhdev DNS Services Manager, RIPE NCC _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
