
Hello, when I was trying updating some reverse DNS records, I had problem due to RDNS check - and I think there's bug in implementation - RDNS checks should be done against DNS servers listed in *updated* (new, submited) record, not against servers from *current* (old) record from RIPE database. Of course, "old" servers doesn't provide proper answers, but now I'm not able to update the records (by other way than delete/recreate objects)... With regards Daniel

Hello, This should not happen. We will check our logs and the system's behaviour and will contact you for follow up. Thank you for informing us. Kind Regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager On Jan 7, 2013, at 6:30 PM, Daniel Suchy <danny@danysek.cz> wrote:
Hello, when I was trying updating some reverse DNS records, I had problem due to RDNS check - and I think there's bug in implementation - RDNS checks should be done against DNS servers listed in *updated* (new, submited) record, not against servers from *current* (old) record from RIPE database.
Of course, "old" servers doesn't provide proper answers, but now I'm not able to update the records (by other way than delete/recreate objects)...
With regards Daniel
participants (2)
-
Daniel Suchy
-
Kaveh Ranjbar