"localhost" zone: what should we do?
kcd at daimlerchrysler.com
Tue Mar 15 22:31:34 UTC 2005
IMO, "best practice" is to get ftp_connect to use a proper,
fully-qualified domain name (FQDN) instead of something as inherently
ambiguous as "localhost". Unless, of course, it really *needs* to use
the loopback address for whatever it is doing (which seems unlikely), in
which I'd let the server use its /etc/hosts file to resolve the name
"localhost" to 127.0.0.1. No reason to pollute DNS with such junk.
Mariano Cunietti wrote:
>we have some problems with a PHP function (ftp_connect), which requires
>a hostname as an argument. This function looks up our DNS for an address
>resolution of "localhost", instead of using his own localhost. We
>checked out /etc/nsswitch.con file and everything looks OK.
>We need to know which is the *best practice* about creating "localhost"
>entries in a named.conf and in a zone file. We already have a 127.
>inverse zone, but we never created a "localhost" zone and file.
>Should we configure a localhost A record per zone (localhost IN A
>127.0.0.1) or a root localhost zone?
>Everything ran smoothly until today (since 1998).
>Via Stefanardo da Vimercate, 28
>20128 - Milano - Italy
>Tel. +39 02 25514319
>Fax +39 02 25514303
>mcunietti at enter.it
>www.enter.it - www.enterpoint.it
>Gruppo Y2K - www.gruppoy2k.it
More information about the bind-users