This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] RDNS checks
- Previous message (by thread): [ncc-services-wg] RDNS checks
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC Training Report 2012 & Plans for 2013
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kaveh Ranjbar
kranjbar at ripe.net
Mon Jan 7 19:10:01 CET 2013
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 at 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 >
- Previous message (by thread): [ncc-services-wg] RDNS checks
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC Training Report 2012 & Plans for 2013
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]