PHP Network Address Resolution Error: Causes and Solutions for getaddrinfo Failure

Error Phenomenon and Cause Analysis

In PHP development, when using the fsockopen function to establish network connections, developers often encounter the php_network_getaddresses: getaddrinfo failed: Name or service not known error message. The core cause of this error is the system's inability to resolve the provided domain name or service name.

From the Q&A data, we can see that the developer attempted to establish a connection using fsockopen($s['url'], 80, $errno, $errstr, 5), but the $s['url'] parameter value was www.mydomain.net/1/file.php, which is actually a complete URL path. However, the first parameter of the fsockopen function should only contain the hostname portion.

Correct Usage of fsockopen Function

The fsockopen function is designed to establish low-level network socket connections, with strict parameter format requirements. The first parameter should be a pure hostname or IP address, without any path information. The correct usage is as follows:

$hostname = "www.mydomain.net";
$port = 80;
$timeout = 5;

$fp = fsockopen($hostname, $port, $errno, $errstr, $timeout);
if ($fp) {
    // Manually construct HTTP request
    $request = "GET /1/file.php HTTP/1.1\r\n";
    $request .= "Host: " . $hostname . "\r\n";
    $request .= "Connection: close\r\n\r\n";
    
    fwrite($fp, $request);
    fclose($fp);
} else {
    echo "Connection failed: " . $errstr . " (" . $errno . ")";
}

Simpler Alternative: file_get_contents

If the developer's main purpose is to submit GET data to a remote URL and obtain the response, using the file_get_contents function is a more concise and efficient choice. This function can directly handle complete URLs, including paths and query parameters:

$url = "http://www.mydomain.net/1/file.php";
$getData = "?var1=val1&var2=val2";

$response = file_get_contents($url . $getData);
if ($response === false) {
    echo "Request failed";
} else {
    // Process response data
    echo $response;
}

Troubleshooting and Resolving DNS Resolution Issues

Beyond parameter usage errors, the getaddrinfo failed error can also stem from DNS resolution problems. The referenced article shows that even with allow_url_fopen enabled, resolution failures can still occur.

For local testing environments, check the /etc/hosts file to ensure test domains are correctly mapped to local IP addresses:

# Add to /etc/hosts file
192.168.1.1 www.mydomain.net

For production environments, verify DNS server configuration. Try adding reliable DNS servers to /etc/resolv.conf:

nameserver 8.8.8.8
nameserver 4.4.4.4

Network Configuration and Service Restart

In some cases, PHP services may need to be restarted to apply new network configurations. As mentioned in the Q&A data, for environments using php-fpm, you can execute:

service php-fpm restart

Additionally, check firewall and SELinux settings to ensure they don't block PHP processes from making network connections.

Error Handling and Debugging Techniques

In practical development, robust error handling mechanisms are crucial. For network operations, always check function return values and provide meaningful error messages:

function makeHttpRequest($url, $data = '') {
    $fullUrl = $url . $data;
    $context = stream_context_create([
        'http' => [
            'timeout' => 30
        ]
    ]);
    
    $response = @file_get_contents($fullUrl, false, $context);
    
    if ($response === false) {
        $error = error_get_last();
        return "Request failed: " . $error['message'];
    }
    
    return $response;
}

This approach allows for more precise problem identification, whether it's DNS resolution failure, connection timeout, or other network issues.