Hi,
I've seen quite a few reports that some people are seeing a CentOS test
page when going to http://lxr.php.net. I, however, don't. If anyone
reading this sees this, can you reply and let me know what your DNS
resolves lxr.php.net as? Ideally, the output from dig or dnstracer would
be handy. It should be resolving as a CNAME to sp2.php.net.
--
Cheers,
Michael
On Fri, 31 Dec 2010 19:37:14 -0000, Michael Maclean
michael@no-surprises.co.uk wrote:
Hi,
I've seen quite a few reports that some people are seeing a CentOS test
page when going to http://lxr.php.net. I, however, don't. If anyone
reading this sees this, can you reply and let me know what your DNS
resolves lxr.php.net as? Ideally, the output from dig or dnstracer would
be handy. It should be resolving as a CNAME to sp2.php.net.
ns6.easydns.net seems to be giving a bad response.
$ dig +noall +trace +answer lxr.php.net
[snip]
php.net. 172800 IN NS ns1.easydns.com.
php.net. 172800 IN NS ns2.easydns.com.
php.net. 172800 IN NS remote1.easydns.com.
php.net. 172800 IN NS remote2.easydns.com.
php.net. 172800 IN NS ns3.easydns.org.
php.net. 172800 IN NS ns6.easydns.net.
;; Received 255 bytes from 192.26.92.30#53(c.gtld-servers.net) in 145 ms
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
php.net. 86400 IN NS ns2.easydns.com.
php.net. 86400 IN NS ns1.easydns.com.
php.net. 86400 IN NS remote2.easydns.com.
php.net. 86400 IN NS remote1.easydns.com.
;; Received 218 bytes from 72.52.2.1#53(ns2.easydns.com) in 58 ms
$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote2.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns3.easydns.org lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns6.easydns.net lxr.php.net
lxr.php.net. 86400 IN A 94.23.222.92
--
Gustavo Lopes
On Fri, 31 Dec 2010 19:37:14 -0000, Michael Maclean
michael@no-surprises.co.uk wrote:Hi,
I've seen quite a few reports that some people are seeing a CentOS test
page when going to http://lxr.php.net. I, however, don't. If anyone reading
this sees this, can you reply and let me know what your DNS resolves
lxr.php.net as? Ideally, the output from dig or dnstracer would be handy. It
should be resolving as a CNAME to sp2.php.net.ns6.easydns.net seems to be giving a bad response.
$ dig +noall +trace +answer lxr.php.net
[snip]php.net. 172800 IN NS ns1.easydns.com.
php.net. 172800 IN NS ns2.easydns.com.
php.net. 172800 IN NS remote1.easydns.com.
php.net. 172800 IN NS remote2.easydns.com.
php.net. 172800 IN NS ns3.easydns.org.
php.net. 172800 IN NS ns6.easydns.net.
;; Received 255 bytes from 192.26.92.30#53(c.gtld-servers.net) in 145 mslxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
php.net. 86400 IN NS ns2.easydns.com.
php.net. 86400 IN NS ns1.easydns.com.
php.net. 86400 IN NS remote2.easydns.com.
php.net. 86400 IN NS remote1.easydns.com.
;; Received 218 bytes from 72.52.2.1#53(ns2.easydns.com) in 58 ms$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218glopes@nebm:~$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote2.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns3.easydns.org lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns6.easydns.net lxr.php.net
lxr.php.net. 86400 IN A 94.23.222.92
ns6 is also returning bogus results for prototype.php.net..
I bet it has something to do with my awesome syntax error in the file
coupleof days ago - ans ns6 isn't smart enough to retrieve the update.
Wise guys tell me bumping the serial after fixing the syntax isn't
always enough, and you actually have to add a new entry.. I'll try
that :)
-Hannes
On Fri, Dec 31, 2010 at 15:00, Hannes Magnusson
hannes.magnusson@gmail.com wrote:
ns6 is also returning bogus results for prototype.php.net..
I bet it has something to do with my awesome syntax error in the file
coupleof days ago - ans ns6 isn't smart enough to retrieve the update.
Wise guys tell me bumping the serial after fixing the syntax isn't
always enough, and you actually have to add a new entry.. I'll try
that :)
Make the TTLs all 1 while you're in there. May as well go from
one extreme to the other and DoS ourselves.
--
</Daniel P. Brown>
Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/
On Fri, Dec 31, 2010 at 21:00, Hannes Magnusson
hannes.magnusson@gmail.com wrote:
On Fri, 31 Dec 2010 19:37:14 -0000, Michael Maclean
michael@no-surprises.co.uk wrote:Hi,
I've seen quite a few reports that some people are seeing a CentOS test
page when going to http://lxr.php.net. I, however, don't. If anyone reading
this sees this, can you reply and let me know what your DNS resolves
lxr.php.net as? Ideally, the output from dig or dnstracer would be handy. It
should be resolving as a CNAME to sp2.php.net.ns6.easydns.net seems to be giving a bad response.
$ dig +noall +trace +answer lxr.php.net
[snip]php.net. 172800 IN NS ns1.easydns.com.
php.net. 172800 IN NS ns2.easydns.com.
php.net. 172800 IN NS remote1.easydns.com.
php.net. 172800 IN NS remote2.easydns.com.
php.net. 172800 IN NS ns3.easydns.org.
php.net. 172800 IN NS ns6.easydns.net.
;; Received 255 bytes from 192.26.92.30#53(c.gtld-servers.net) in 145 mslxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
php.net. 86400 IN NS ns2.easydns.com.
php.net. 86400 IN NS ns1.easydns.com.
php.net. 86400 IN NS remote2.easydns.com.
php.net. 86400 IN NS remote1.easydns.com.
;; Received 218 bytes from 72.52.2.1#53(ns2.easydns.com) in 58 ms$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218glopes@nebm:~$ dig +noall +answer +norec @ns1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote1.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @remote2.easydns.com lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns3.easydns.org lxr.php.net
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
glopes@nebm:~$ dig +noall +answer +norec @ns6.easydns.net lxr.php.net
lxr.php.net. 86400 IN A 94.23.222.92ns6 is also returning bogus results for prototype.php.net..
I bet it has something to do with my awesome syntax error in the file
coupleof days ago - ans ns6 isn't smart enough to retrieve the update.
Wise guys tell me bumping the serial after fixing the syntax isn't
always enough, and you actually have to add a new entry.. I'll try
that :)
...And that seems to have fixed both the lxr and the prototype issues :)
-Hannes
You have to wait unzil the TTL is over
Jesus why is the TTL so hughe?
lxr.php.net. 61221 IN A 94.23.222.92
[harry@srv-rhsoft:~]$ dig A lxr.php.net @NS2.EASYDNS.COM
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218
BTW:
What poor setup to display software-information on a non-configured hostname
even calling ip-address directly instead mod_security blocking such calls
Am 31.12.2010 20:37, schrieb Michael Maclean:
Hi,
I've seen quite a few reports that some people are seeing a CentOS test page when going to http://lxr.php.net. I,
however, don't. If anyone reading this sees this, can you reply and let me know what your DNS resolves lxr.php.net
as? Ideally, the output from dig or dnstracer would be handy. It should be resolving as a CNAME to sp2.php.net.
You have to wait unzil the TTL is over
Jesus why is the TTL so hughe?lxr.php.net. 61221 IN A 94.23.222.92
[harry@srv-rhsoft:~]$ dig A lxr.php.net @NS2.EASYDNS.COM
lxr.php.net. 86400 IN CNAME sp2.php.net.
sp2.php.net. 86400 IN A 173.236.52.218BTW:
What poor setup to display software-information on a non-configured hostname
even calling ip-address directly instead mod_security blocking such calls
Blame the CentOS default configuration for that one.
--
</Daniel P. Brown>
Network Infrastructure Manager
Documentation, Webmaster Teams
http://www.php.net/
What poor setup to display software-information on a non-configured hostname
even calling ip-address directly instead mod_security blocking such calls
The IP of the machine displaying the CentOS page is no longer mine, nor
does it have anything to do with PHP, so there's nothing we can do.
--
Cheers,
Michael