PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB`  oB]c@sdZddlmZddlmZddlmZddlmZeje Z eZ dddd gZ d d Z d Zd S(sf Resolv Conf ----------- **Summary:** configure resolv.conf This module is intended to manage resolv.conf in environments where early configuration of resolv.conf is necessary for further bootstrapping and/or where configuration management such as puppet or chef own dns configuration. As Debian/Ubuntu will, by default, utilize resovlconf, and similarly RedHat will use sysconfig, this module is likely to be of little use unless those are configured correctly. .. note:: For RedHat with sysconfig, be sure to set PEERDNS=no for all DHCP enabled NICs. .. note:: And, in Ubuntu/Debian it is recommended that DNS be configured via the standard /etc/network/interfaces configuration file. **Internal name:** ``cc_resolv_conf`` **Module frequency:** per instance **Supported distros:** fedora, rhel, sles **Config keys**:: manage_resolv_conf: resolv_conf: nameservers: ['8.8.4.4', '8.8.8.8'] searchdomains: - foo.example.com - bar.example.com domain: example.com options: rotate: timeout: 1 i(tlog(t PER_INSTANCE(t templater(tutiltfedoratopensusetrheltsless/etc/resolv.confcCsg}g}d|krqxV|djD]A\}}t|tr)|rZ|j|qj|j|q)q)Wnx||D]}|d|=q|W|jdsi|d/s