Bug #11058 Updated: php_network_getaddresses: getaddrinfo failed

ID: 11058 Updated by: wez@php.net Reported By: pat@mail.rit.edu Status: Bogus Bug Type: Network related Operating System: OpenBSD 2.6 PHP Version: 4.0.6 New Comment: And that is the cause of the problem (and the reason that this report is set to bogus). You need to tell your SuSE box how to resolve the addresses; the SuSE yast tool should let you set the nameserver in it's network configuration. I can't help you any further here, and this is not the place to discuss this further. I'd suggest looking at the SuSE support database for this: it's bound to be a FAQ. Previous Comments: ------------------------------------------------------------------------ [2002-04-03 15:58:04] g.almasi@gigcity.com another note: I have root to another box (it serves about 20 sites to the web) that is also running PHP 4.0.6 and php_network_getaddresses works fine. Does this function require a nameserver? My SuSE 7.3 box is a development machine on my LAN, so I just use proxies to get to it with a browser. Getting DNS, BIND, and DHCP to work was beyond me when I set it up (still is, actually). So I just use a proxy setting for browsers while I build sites. ------------------------------------------------------------------------ [2002-04-03 14:18:22] g.almasi@gigcity.com So I just tried changing a line in /etc/modules.conf: - From "alias net-pf-10 off" - To "alias net-pf-10 ipv6" I rebooted the box and I still had this problem happening. ------------------------------------------------------------------------ [2002-04-03 14:03:19] g.almasi@gigcity.com Is this setting in /etc/rc.config? ------------------------------------------------------------------------ [2002-04-03 11:34:09] wez@php.net In your OS config that is. ------------------------------------------------------------------------ [2002-04-03 11:32:50] wez@php.net If you have IPV6 support enabled, try turning it off, or vice-versa. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/11058 -- Edit this bug report at http://bugs.php.net/?id=11058&edit=1