Yikes! That looks quite strange. In my paranoia, here is what I did:
[jwhite] whois winehq.org | grep 'Name Server:' Name Server:FOGHORN.CODEWEAVERS.COM Name Server:WINE.CODEWEAVERS.COM [jwhite] host www.winehq.org wine.codeweavers.com www.winehq.org A 209.46.25.134 [jwhite] host www.winehq.org foghorn.codeweavers.com www.winehq.org A 209.46.25.134 That suggests everything is good here. But that is still rather freaky; do you suppose someone is hijacking your DNS records somehow? Cheers, Jeremy Kirill K. Smirnov wrote: > Hi, > > I've noticed very strange thing today: www.winehq.org resolves to > http://searchportal.information.com/index.mas?epl=00630086VFAXVE0DWlgVVRBeVwtAVw5ZB14NW1YMBAhCUVZRWRQbWxBfHwRsXQUNU1oBVFc > > This site claims to be winehq.org. > > "Winehq.org - What you need, when you need it" > > I cannot perform "git fetch"!! > > Quick workaround I found is to use winehq.com, but how can I explain this to > git? > > Does anybody except me suffer the same mystery thing? > Some info (I do not understand everything, but it may be useful): > [EMAIL PROTECTED]:~/wine$ dig www.winehq.org > > ; <<>> DiG 9.3.1 <<>> www.winehq.org > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54611 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 > > ;; QUESTION SECTION: > ;www.winehq.org. IN A > > ;; ANSWER SECTION: > www.winehq.org. 94739 IN A 66.151.179.147 > > ;; AUTHORITY SECTION: > winehq.org. 82437 IN NS wine.codeweavers.com. > winehq.org. 82437 IN NS foghorn.codeweavers.com. > > ;; ADDITIONAL SECTION: > wine.codeweavers.com. 94780 IN A 209.46.25.134 > foghorn.codeweavers.com. 94780 IN A 216.251.189.130 > > ;; Query time: 18 msec > ;; SERVER: 195.19.225.253#53(195.19.225.253) > ;; WHEN: Tue Apr 10 22:55:48 2007 > ;; MSG SIZE rcvd: 136 > > [EMAIL PROTECTED]:~$ nslookup 66.151.179.147 > Server: 195.19.225.253 > Address: 195.19.225.253#53 > > ** server can't find 147.179.151.66.in-addr.arpa: NXDOMAIN > > > Thanks in advance, > -- > Kirill > > P.S. This message may be posted to wrong list, but it is... > >
