News
Just a short reminder that Infoblox is presenting a webinar on June 10th on DNS security and DNSSEC featuring Dan Kaminsky (of cache-poisoning-vulnerability fame) and Scott Rose of NIST, co-author of the most recent set of DNSSEC RFCs.
Can the ibSmart SnapIn be configured in a disaster recovery mode instead of a round robin mode? I want to be able to setup the following:
www.bloxdemo.com goes to 192.168.1.80 unless the web site on 192.168.1.80 is down then www.bloxdemo.com resolves to 192.168.2.80 until the site at 192.168.1.80 is back up
At the moment it appears it only supports a DNS round robin of one name to multiple addresses. (based on the documentation)
-Voltmer
I recently did five talks in Europe on threats to DNS, leading up to the need to deploy DNSSEC. Several audiences asked me for my opinion on the right time to implement DNSSEC. Clearly, the lack of signed parent zones is an impediment for most of us: Unless your zones are children of .se, .cz, .br, .bg, or one of the few other signed TLDs, you'd need to distribute your zone's public key to everyone you'd like to validate your zone data. That doesn't scale, right?
Found a new device that NetMRI does not currently support?
Here is the information we will need in order to develop support for the device:
1. An SNMP Walk (Tools>Device>SNMP Walk) of the device using .1 as the Root OID.
You can also run snmpwalk from the NetMRI CLI and then scp the results from the NetMRI.
2. A Discovery Diagnostic (Tools>Device>Discovery Diagnostic) for the device, making sure to enable the Force Tests option.