From: Tom <si...@tr...> - 2008-09-29 18:15:54
|
Andy Staudacher wrote: > If you have non standard DNS settings, this one can fail. E.g. routing > a fallback / wildcard to some host instead letting the DNS system > behave like there is no such hostname. That's the case when you use > opendns has DNS hosts, maybe that's also the case with your host > settings. > I wasn't aware of the opendsn thing. I'll add that to the note in the matrix. Yea, DSN resolves to my IP for any hostname with my domain on the end. I was testing WP-MU for a while and I was using hostnames on my site. I don't mess with them anymore. I have to send email to my ISP to change my DNS records so I've left it that way until I got more experience with Apache and hostnames. > All this test exercises is that G2 receives a proper error from > fsockopen when it tries to connect to a hostname which doesn't resolve > to an IP. Obviously your system maps that hostname to an IP. That's what I thought. So it's noted correctly in the matrix I say close it. It passes on other systems so we know the code is good. > > +1 for closing the bug since we can't reproduce it on other systems > and you've admitted to having special DNS settings on that box. > Me too, unless anyone else has an issue. -Tom |