Hi, this is not directly an ATLAS issue - but at least a RIPE related question. A friend of mine has problems at the moment with his server hoster. In particular, the PTR record for the server's IP cannot be resolved because the attached nameserver answers with NXDOMAIN. Not a big problem, espacially not a RIPE problem. But here's the response he got from his hoster a few days ago (translated from german). It's a bit... Well... The right word would be: "venturesome": -------- Today at 5:21 PM we got a reply from a RIPE technician who acknowledged that this is a known issue. Not only our IPs are affected by this. The RIPE had a large synchronisation problem between their root name servers which leaded to the situation that the responsible name servers are not connected to the right IPs. The RIPE technician said, the problem could only be solved by a serialized restart of all root name servers, followed by a resync. -------- Funny, eh? A few sentences later: -------- At the moment, the RIPE technicians are busy with preparations for this restart and sync. Actually, the restart of the servers will be done in the night from monday to tuesday. The synchronization process needs about eight more hours to complete. After that, your PTR should be resolved correctly. -------- A RESTART of the ROOT NAME SERVERS? "PTR doesn't work!" - "Have you tried turning it off and on again?" But the best part: -------- We got information that not only our IPs are affected by this, about 27% of all available IP subnets are affected - which is a huge amount. -------- The RIPE status page says: It's all OK, we have no planned maintenances. So I'm very sure the hoster is lying to us and should get a really long wooden nose. But before we make bigger trouble I would like to hear from some others (maybe a RIPE employee?) that the PTR zone was not harmed in the last few days. It's a bit more official, you know... ;-) THANK YOU! -- Greetings from Wuppertal, Germany Max Grobecker