Warning: fsockopen() [function.fsockopen]:

php

 

_net

 work_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /inc.xmlrpc.

php

  on line 357

Warning: fsockopen() [function.fsockopen]: unable to connect to blogsearch.google.com:80 (Unknown error) in /inc.xmlrpc.

php

  on line 357

apparently, this is an issue that others have identified as it relates to

PHP

  and the configuration of your name servers on the box you are on. As I am on a virtual server, not sure what I need to ask my provider to change, or what I need to set up in my etc files to configure name server correctly. Is there a way in

PHP

  I can set the name server to use for resolving names?i

That means the the box cannot resolve the address for one reason or another. If you can SSH to the box (or whatever the windows equivalent is) try to ping out and see if it can do it... it might be that the box has some things set so that you cannot (by default) get out.

I agree with Perk, this is either a temporary failure or a deliberate attempt to block you. If it is not a temporary failure and you want to get around it you could try something like http://

pear

 .

php

 

.net

 /manual/en/package

.net

 working

.net

 -dns.

php

  to do your name resolution and then feed the IP adddress itself to your socket functions. As it is a VS you may need to do a local install of

pear

  as per http://

pear

 .

php

 

.net

 /manual/en/installation.shared.

php

  or maybe get your hosts to do it for you (lol, don't tell them why you need it, lol)

HTH,
td

thanks guys i will get on it!

If your host is being cagey about allowing you to use DNS for certain functions, you can set up a local caching nameserver on your VS.  It requires little overhead, and if you are hitting the same hosts a lot, it will speed things up.  It will also protect you against short outtages (depending on how long you set the cache timeout) of your hosts name servers.  It also reduces

net

 work overhead if you have a lot of name service lookups.

There's not a lot of downside with it unless you are really up against the wall wrt resources on your box, be it VS or actual hardware.

I used to run one myself in @ my house when I had a wireless broadband provider, because their name servers crapped out periodically with no warning, even though my link was AOK.

=RT=

good idea, hadnt thought about that