IPAM News

blog navigation

IP Address Management service announcements and updates.

blog posts

  • Immediate Fixed Addresses feature

    On Thu Jun 22, we will be temporarily re-enabling the "Immediate Fixed Addresses" feature which is known to cause some long-term instability for the DHCP service. It is anticipated that sometime after this (possibly weeks later), one or both of the main campus DHCP servers will experience a crash event (in the worst case causing a 30-minute outage), after which we will disable the feature again to restore full stability. The goal is to provide the vendor with diagnostic information that they can use to implement a fix, so that we will eventually be able to re-enable the feature long-term.

    (see full post for details)

  • IPAM Upgrade: Oct 4, 2016

    On Tue Oct 4 between 5:00-7:00am, the production IP Address Management appliance grid will be upgraded to a new software release from the vendor (7.2.12).

    Important Reminder for Perl API (PAPI) Users

    After the upgrade, you will need to update your installation of the Infoblox PAPI perl modules on any client systems from which you run PAPI scripts.  Do not apply this change to a production environment ahead of time, as the modules are not backward-compatible.

    RESTful Web API (WAPI) users do not need to take any action.

  • IPAM Upgrade: March 24, 2016

    On Thu Mar 24 between 5:00-7:00am, the production IP Address Management appliance grid will be upgraded to a new software release from the vendor (7.2.7).

    Important Reminder for Perl API (PAPI) Users

    After the upgrade, you will need to update your installation of the Infoblox PAPI perl modules on any client systems from which you run PAPI scripts.  Do not apply this change to a production environment ahead of time, as the modules are not backward-compatible.

  • Best Practice for Stand-alone CNAME Records

    We have recently updated the IPAM service documentation to reflect a new best practice recommendation for deciding between Host Aliases and stand-alone CNAME records.

  • Dev IPAM Grid

    The development IPAM grid, formerly located at ipam-dev.illinois.edu, will be down for the next several days to facilitate a hardware transition.  When it returns, it will have a new hostname: https://dev.ipam.illinois.edu

  • Automatic renewal of non-.edu domains

    Effective immediately, non-.edu DNS domains registered through CITES will be automatically renewed by the registrar 60-90 days before they are scheduled to expire.  The Primary and Administrative domain contacts will receive a notification email prior to each auto-renewal, but will not need to respond affirmatively in order for the auto-renewal to proceed.

    If you do NOT wish to renew a domain, you must notify hostmgr NO LESS THAN 91 DAYS PRIOR TO ITS EXPIRATION DATE (or sooner if that deadline would fall on a non-business day) to ensure that the change can be processed before the next auto-renewal occurs.

    Transitional note: for non-.edu domains currently scheduled to expire before Mar 2, 2015, you must notify hostmgr no later than Dec 1, 2014 if you do not wish to renew these domains.  Individual reminder notices for these domains will be sent out within the next week.

  • IPAM Upgrade: July 24, 2014

    On Thu Jul 24, 2014 between 10:00pm-12:00 midnight, the production Infoblox grid for the campus IPAM (DNS and DHCP) service will be upgraded from its current software version (6.5.0) to the latest release from the vendor (6.10.6).

    Important Reminder for API Users

    After the upgrade date, you will need to update your installation of the Infoblox API perl modules on any client systems that you use to run Infoblox API scripts against the production grid. Note that this upgrade cannot be applied to your production environments ahead of time; see the service documentation (http://www.cites.illinois.edu/ipam/api.html) for further explanation.

  • Authoritative DNS Improvements: update

    As of today, the transition announced in the previous post (Authoritative DNS Improvements) is complete: dns3.illinois.edu has replaced dns1.iu.edu as our off-site authoritative nameserver (in case of an Urbana campus outage), and our authoritative zones have been removed from dns1.iu.edu.

  • Authoritative DNS Improvements

    CITES Networking is pleased to announce two upcoming changes to our authoritative DNS infrastructure: dns3.illinois.edu will replace dns1.iu.edu as our off-site authoritative nameserver (in case of an Urbana campus outage), and IPv6 addresses will be added to our authoritative nameservers dns1.illinois.edu and dns2.illinois.edu.

    For most customers, no action is required. However, action will be required for IT Pros who maintain slaved delegation zones.

  • Known Issue with CSV Import

    When using the CSV Import mechanism to add or modify Host records, your DNS changes may not propagate from IPAM to the main nameservers dns1.illinois.edu and dns2.illinois.edu. A workaround is available; please see Known Issues for details. This bug has been reported to the vendor.