Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 daboule commented Permalink

This is the reason why the best practice is to configure the /etc/netsvc.conf file in that way : <div>&nbsp;</div> <div>&nbsp;</div> hosts = local,bind <div>&nbsp;</div> <div>&nbsp;</div> It overrides the default behaviour defined in /etc/irs.conf. <div>&nbsp;</div> <div>&nbsp;</div> http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.files%2Fdoc%2Faixfiles%2Fnetsvc.conf.htm <div>&nbsp;</div> <div>&nbsp;</div> I don't what is the future of the /etc/netsvc.conf file. <div>&nbsp;</div> <div>&nbsp;</div> Maybe big blue will deprecate it, making /etc/irs.conf the central config file for resolving name mechanism. <div>&nbsp;</div>

2 Jim_Carstensen commented Permalink

There's also /etc/netsvc.conf file that sets the lookup order (and _if_ you are doing lookup). http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.files%2Fdoc%2Faixfiles%2Fnetsvc.conf.htm <div>&nbsp;</div> For example, one default we used to use was: <br /> hosts = local, bind4 <div>&nbsp;</div> This prevents hitting DNS for lookups like localhost, and then tries DNS but only for IPv4. (We used to do local4, bind4, but now we have the IPv6 localhost address in /etc/hosts as well. At the very least sendmail sends out a warning if it can't resolve it.)