Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.
- From-Host: 126.96.36.199 - Date/Time: Tue Jun 11 17:16:53 2013 SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [domain] 156.9.185.in-addr.arpa domain: 156.9.185.in-addr.arpa descr: SALAY-DEDICATED admin-c: CE1532-RIPE tech-c: CE1532-RIPE zone-c: CE1532-RIPE nserver: rs1.salay.com.tr nserver: rs2.salay.com.tr notify: firstname.lastname@example.org mnt-by: mnt-salay changed: email@example.com 20120302 source: RIPE ***Error: Superfluous name server listed at parent: rs1.salay.com.tr A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Superfluous name server listed at parent: rs2.salay.com.tr A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Total parent/child glue mismatch. The parent lists name servers that the child doesn't know about; see details in advanced. This configuration could actually work but breaks very easily if one of these zones changes slightly. ***Warning: Could not find reverse address for 188.8.131.52 (184.108.40.206.in-addr.arpa.). PTR record(s) for the address could not be found in the .arpa-zone. (ip6.arpa. for IPv6 addresses and in-addr.arpa. for IPv4). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <firstname.lastname@example.org> Generated by RIPE WHOIS Update version 1.66.3 on WHOIS1 Handled sync update (RIPE, 2013-06-11 17:16:53)
Join the community of 500,000 technology professionals and ask your questions.