No resolve host, no send email (again)

  • Resolved Gil Hardwick

    (@gil-hardwick)


    10 years, 8 months ago

    This very real problem continues to recur. I get WordPress sending email OK, then whenever I update something and reboot the system it all stops working again.

    The people over at CentOS are NOT very helpful, insisting there is something wrong with my settings and I should fix it myself.

    I have Jetpack installed on one of my client’s sites, and it too reports that it is unable to retreive stats because unable to resolve host.

    The error report is as follows:

    We were unable to get your stats just now. Please reload this page to try again. If this error persists, please contact support. In your report please include the information below.

    User Agent: “Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130807 Firefox/17.0”
    Page URL: “http://ethicaladviser.com.au/wp-admin/admin.php?page=stats&noheader&dashboard&width=762”
    API URL: “http://dashboard.wordpress.com/wp-admin/index.php?noheader=true&proxy&blog=54300429&page=stats&chart&unit=1&color=fresh&width=376&height=175&j=1:2.3.1”
    http_request_failed: “Couldn’t resolve host ‘dashboard.wordpress.com'”

    When I try to send a test email through SMTP I get:

    An error was encountered while trying to send the test e-mail.

    SMTP Error: Could not connect to SMTP host.

    SMTP -> ERROR: Failed to connect to server: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution (0)

    Running a verbose host query in the system console, however, produces the following:

    [root@s3 ~]# host -v dashboard.wordpress.com
    Trying “dashboard.wordpress.com”
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22094
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;dashboard.wordpress.com. IN A

    ;; ANSWER SECTION:
    dashboard.wordpress.com. 14238 IN CNAME lb.wordpress.com.
    lb.wordpress.com. 138 IN A 66.155.9.238
    lb.wordpress.com. 138 IN A 76.74.254.120
    lb.wordpress.com. 138 IN A 66.155.11.238
    lb.wordpress.com. 138 IN A 72.233.69.6
    lb.wordpress.com. 138 IN A 72.233.2.58
    lb.wordpress.com. 138 IN A 76.74.254.123

    Received 154 bytes from 8.8.8.8#53 in 76 ms
    Trying “lb.wordpress.com”
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17560
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;lb.wordpress.com. IN AAAA

    ;; AUTHORITY SECTION:
    wordpress.com. 1759 IN SOA ns1.wordpress.com. mmmmmm.gmail.com. 2005071858 14400 7200 604800 60

    Received 87 bytes from 8.8.8.8#53 in 209 ms
    Trying “lb.wordpress.com”
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42995
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;lb.wordpress.com. IN MX

    ;; AUTHORITY SECTION:
    wordpress.com. 1799 IN SOA ns1.wordpress.com. mmmmmm.gmail.com. 2005071858 14400 7200 604800 60

    Received 87 bytes from 8.8.8.8#53 in 520 ms

    I’m running out of tether on this. Is there something broken between WordPress and CentOS? I have both latest versions kept routinely up to date.

    Any help and/or advice very greatly appreciated.

Viewing 1 replies (of 1 total)
  • Thread Starter Gil Hardwick

    (@gil-hardwick)

    10 years, 7 months ago

    Just to update and close this thread, I finally decided that this stupid problem simply isn’t worth the effort being spent on it, for so little gain either immediately or in terms of overall client contact efficiency.

    All my sites are smart phone savvy anyway, even my hand-coded pages, and with so very many people browsing on the move these days, or over a morning coffee or a beer later, rather than bother with the site itself being able to send email via some variety of contact form I merely returned to my older style of embedding <tel:> and <mailto:> links in the relevant pages.

    The prospective client only has to tap one of the little page icons now, and either call directly or email with preset subject: and body: content.

    I don’t see this technique as any sort of work-around for bad or broken code, it simply renders the entire question redundant.

    Thanks anyway.

Viewing 1 replies (of 1 total)
  • The topic ‘No resolve host, no send email (again)’ is closed to new replies.