Hi Ronald, The duplicate domain objects have been removed and we will add checks to avoid this from happening again.
Regards, Vivek On 6/11/20, 6:46 pm, "[email protected] on behalf of Vivek Nigam" <[email protected] on behalf of [email protected]> wrote: Hi Ronald, We are reviewing these conflicts and will update you as soon as possible. Thank you for bringing this matter to our attention. Regards, Vivek On 6/11/20, 1:37 pm, "[email protected] on behalf of Ronald F. Guilmette" <[email protected] on behalf of [email protected]> wrote: Recently I've been looking at records relating to reverse DNS delegation, as present (and where present) in the WHOIS data bases of the various RIRs, including APNIC. I was rather horrified to find that due to what seems to have been a small software slip-up, there are, at present, a number of cases (40) within the AFRINIC WHOIS data base where the same single subdomain of the .in-addr.arpa domain actually has two different and conflicting records present in the data base. This self-evident consistancy error appears to have crept into the AFRINIC WHOIS data base due to an inadvertant lack of proper format checking of the full name of the particular .in-addr.arpa subdomain in question. More specifically, it seems that AFRINIC allowed into their data base an entry for -both- "<something>.in-addr.arpa" and also a parallel one for "<something>.in-addr.arpa.", the only difference being the presence or absence of a trailing period. I wrote a small Perl script to detect these cases in the AFRINIC data base and I have reported all such cases to AFRINIC for remediation. Anyway, I have just run that exact same script also on a very recently fetched copy of the APNIC WHOIS data base, and it has found that this same syndrome has also infected the APNIC WHOIS data base, but to a substantially lesser degree. As the examples below illustrate, there are two cases in the current APNIC WHOIS data base where the same single reverse DNS delegation is represented by two or more conflicting records, and where the reason these cases were not already detected as duplicates is mostly likely that one record includes a trailing period in the name of the in-addr.arpa subdomain while the other record does not. I would like to respectfully suggest that the APNIC hostmaster take steps to immediately remediate these obvious conflicts and errors in the WHOIS data base, and also, that programming changes be made so as to prevent this same sort of error from creeping back into the data base in the future. Case #1) -------------------------------------------------------------------- domain: 76.145.203.in-addr.arpa. descr: Customer use mobile IP subnet country: HK admin-c: FC509-AP tech-c: FC509-AP zone-c: FC509-AP nserver: red.hutchcity.com nserver: brown.hutchcity.com mnt-by: MAINT-HK-HUTCHMOBILE last-modified: 2010-07-21T00:27:45Z source: APNIC domain: 76.145.203.in-addr.arpa descr: Reverse zone for 203.145.76.0/24 admin-c: FC509-AP tech-c: FC509-AP zone-c: FC509-AP nserver: dnshost1.on-nets.com nserver: dnshost2.on-nets.com mnt-by: MAINT-HK-HUTCHMOBILE last-modified: 2018-10-31T04:06:13Z source: APNIC -------------------------------------------------------------------- Case #2) -------------------------------------------------------------------- domain: 77.145.203.in-addr.arpa. descr: Customer use mobile IP subnet country: HK admin-c: FC509-AP tech-c: FC509-AP zone-c: FC509-AP nserver: red.hutchcity.com nserver: brown.hutchcity.com mnt-by: MAINT-HK-HUTCHMOBILE last-modified: 2010-07-21T00:31:45Z source: APNIC domain: 77.145.203.in-addr.arpa descr: Reverse zone for 203.145.77.0/24 admin-c: FC509-AP tech-c: FC509-AP zone-c: FC509-AP nserver: dnshost1.on-nets.com nserver: dnshost2.on-nets.com mnt-by: MAINT-HK-HUTCHMOBILE last-modified: 2018-10-26T10:37:37Z source: APNIC -------------------------------------------------------------------- _______________________________________________ apnic-talk mailing list [email protected] https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.apnic.net%2Fmailman%2Flistinfo%2Fapnic-talk&data=04%7C01%7C%7C79ae62124ba040b5801f08d882053a50%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637402306278679567%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nn4ncA4tzwn3v1pdIoU0S881KJcoPOxVFwwV%2FtmZ17s%3D&reserved=0 _______________________________________________ apnic-talk mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/apnic-talk _______________________________________________ apnic-talk mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/apnic-talk
