LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] Where is slackware.com ??
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 4 of 5 « First 23 4 5
  Search this Thread
Old 12-31-2010, 12:59 PM   #46
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,897

Rep: Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019

Quote:
Originally Posted by trademark91 View Post
it works if you go to www.slackware.com

but if you just go to slackware.com and dont type in the www at the beginning, it goes to the for sale page.
that probably just means you had www.slackware.com cached. They'll probably both go to the sales page if you start with an empty cache.
 
Old 12-31-2010, 01:43 PM   #47
kingbeowulf
Senior Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware
Posts: 1,266
Blog Entries: 11

Rep: Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744
LOL. I get "Expiration Date: 25-dec-2015" but still a network solutions placeholder via OpenDNS. Good to know the site is OK and not compromised and is just a DNS issue.
 
Old 12-31-2010, 02:39 PM   #48
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, OpenSuSE
Posts: 1,839

Rep: Reputation: 242Reputation: 242Reputation: 242
I too get the network solutions page, when I try to open http://www.slackware.com, and I am NOT running a local caching proxy like squid. So the problem must be somewhere farther up in the DNS hierarchy...

This happens also, when I try to open an URL, such as http://www.slackware.com/getslack/.

And also, when I click on one of the hits when I do an internet search for "Slackware mirrors".


gargamel
 
Old 12-31-2010, 02:45 PM   #49
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 231Reputation: 231Reputation: 231
Nothing sinister... just an over-sight on somebody's part.

Should be all taken care of apart from the odd stale DNS record still floating around.



Code:
;; QUESTION SECTION:
;slackware.com.                 IN      ANY

;; ANSWER SECTION:
slackware.com.          84830   IN      NS      ns1.cwo.com.
slackware.com.          84830   IN      NS      ns2.cwo.com.
slackware.com.          84830   IN      A       64.57.102.34
Code:
;; QUESTION SECTION:
;www.slackware.com.             IN      ANY

;; ANSWER SECTION:
www.slackware.com.      84820   IN      CNAME   slackware.com.
Last edited by mRgOBLIN; 12-31-2010 at 02:47 PM.
 
Old 12-31-2010, 02:55 PM   #50
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,897

Rep: Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019
back to normal here now too.
 
Old 12-31-2010, 03:25 PM   #51
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875

Rep: Reputation: 282Reputation: 282Reputation: 282
Quote:
Originally Posted by bathory View Post
That doesn't make sense
Cache should expire at the same time for all.
Nope.

An expiry time value stored in the DNS record is a time in seconds that you can cache that record.

When you do the lookup on your own DNS server it gets the record from the authoritative server and then caches that record from that point until the timer expires.

So domain A has 3 hours for expiry
At 1am server B looks up A and caches the record, this will expire at 4am
At 2am server C looks up A and caches the record, this will expire at 5am

At 3 am domain A changes IP
Just after 4am people who use server B can get the new IP but people using server C have to wait until after 5am
 
1 members found this post helpful.
Old 12-31-2010, 03:38 PM   #52
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
[UNSOLVED] Where is slackware.com?
Slackware.com is unavailable to the general public.

Many dns names servers in California still give the wrong ip address for slackware.com

Since slackware.com is using name servers at cwo.com it looks to me like the CWO.COM dns servers have been hacked.

ns1.cwo.com
ns2.cwo.com
 
Old 12-31-2010, 03:48 PM   #53
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 231Reputation: 231Reputation: 231
I don't think so...
Querying their servers directly...

Code:
host www.slackware.com ns1.cwo.com
Using domain server:
Name: ns1.cwo.com
Address: 64.57.100.2#53
Aliases: 

www.slackware.com is an alias for slackware.com.
slackware.com has address 64.57.102.34
slackware.com mail is handled by 1 mail-mx.cwo.com.


host slackware.com ns1.cwo.com 
Using domain server:
Name: ns1.cwo.com
Address: 64.57.100.2#53
Aliases: 

slackware.com has address 64.57.102.34
slackware.com mail is handled by 1 mail-mx.cwo.com.
 
Old 12-31-2010, 04:21 PM   #54
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
I beg to differ, for me www.slackware.com is still down
Here is my result:

Code:
host www.slackware.com ns1.cwo.com
Using domain server:
Name: ns1.cwo.com
Address: 64.57.100.2#53
Aliases: 

www.slackware.com has address 209.62.105.19
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
 
Old 12-31-2010, 04:57 PM   #55
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
Ok, I "fixed" it by changing name servers ...
I edited /etc/resolv.conf and use these nameservers from OpenDNS.com:

nameserver 208.67.222.222
nameserver 208.67.220.220
 
Old 12-31-2010, 05:02 PM   #56
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875

Rep: Reputation: 282Reputation: 282Reputation: 282
Please refrain from using host as it is incapable of giving the details necessary to determine what is wrong.

Again ns1.cwo.com & ns2.cwo.com are fine

Code:
; <<>> DiG 9.7.2-P3 <<>> @ns1.cwo.com www.slackware.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5488
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.slackware.com.             IN      A

;; ANSWER SECTION:
www.slackware.com.      86400   IN      CNAME   slackware.com.
slackware.com.          86400   IN      A       64.57.102.34

;; AUTHORITY SECTION:
slackware.com.          86400   IN      NS      ns2.cwo.com.
slackware.com.          86400   IN      NS      ns1.cwo.com.

;; ADDITIONAL SECTION:
ns1.cwo.com.            3001    IN      A       64.57.100.2
ns2.cwo.com.            3001    IN      A       64.57.100.3

;; Query time: 197 msec
;; SERVER: 64.57.100.2#53(64.57.100.2)
;; WHEN: Sat Jan  1 08:59:52 2011
;; MSG SIZE  rcvd: 137
Code:
; <<>> DiG 9.7.2-P3 <<>> @ns2.cwo.com www.slackware.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10149
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.slackware.com.             IN      A

;; ANSWER SECTION:
www.slackware.com.      86400   IN      CNAME   slackware.com.
slackware.com.          86400   IN      A       64.57.102.34

;; AUTHORITY SECTION:
slackware.com.          86400   IN      NS      ns2.cwo.com.
slackware.com.          86400   IN      NS      ns1.cwo.com.

;; ADDITIONAL SECTION:
ns1.cwo.com.            3001    IN      A       64.57.100.2
ns2.cwo.com.            3001    IN      A       64.57.100.3

;; Query time: 197 msec
;; SERVER: 64.57.100.3#53(64.57.100.3)
;; WHEN: Sat Jan  1 08:59:48 2011
;; MSG SIZE  rcvd: 137
Code:
; <<>> DiG 9.7.2-P3 <<>> +trace www.slackware.com
;; global options: +cmd
.                       12199   IN      NS      h.root-servers.net.
.                       12199   IN      NS      i.root-servers.net.
.                       12199   IN      NS      m.root-servers.net.
.                       12199   IN      NS      e.root-servers.net.
.                       12199   IN      NS      a.root-servers.net.
.                       12199   IN      NS      c.root-servers.net.
.                       12199   IN      NS      j.root-servers.net.
.                       12199   IN      NS      g.root-servers.net.
.                       12199   IN      NS      f.root-servers.net.
.                       12199   IN      NS      d.root-servers.net.
.                       12199   IN      NS      b.root-servers.net.
.                       12199   IN      NS      l.root-servers.net.
.                       12199   IN      NS      k.root-servers.net.
;; Received 488 bytes from 192.168.10.254#53(192.168.10.254) in 19 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
;; Received 495 bytes from 202.12.27.33#53(m.root-servers.net) in 147 ms

slackware.com.          172800  IN      NS      ns2.cwo.com.
slackware.com.          172800  IN      NS      ns1.cwo.com.
;; Received 107 bytes from 192.43.172.30#53(i.gtld-servers.net) in 192 ms

www.slackware.com.      86400   IN      CNAME   slackware.com.
slackware.com.          86400   IN      A       64.57.102.34
slackware.com.          86400   IN      NS      ns1.cwo.com.
slackware.com.          86400   IN      NS      ns2.cwo.com.
;; Received 137 bytes from 64.57.100.3#53(ns2.cwo.com) in 197 ms
Last edited by wildwizard; 12-31-2010 at 05:05 PM.
 
Old 12-31-2010, 05:20 PM   #57
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
Quote:
willysr@vlab-ti:~$ whois slackware.com

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Domain Name: SLACKWARE.COM
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com
Referral URL: http://www.networksolutions.com
Name Server: NS1.CWO.COM
Name Server: NS2.CWO.COM
Status: clientTransferProhibited
Updated Date: 31-dec-2010
Creation Date: 26-dec-1995
Expiration Date: 25-dec-2015
Quote:
Administrative Contact:
Bruce, Robert A. rab@CDROM.COM
Walnut Creek CDROM
4041 PIKE LN STE D
CONCORD, CA 94520-1207
US
(510) 674-0783 fax: (510) 674-0821

Technical Contact:
Volkerding, Patrick volkerdi@SLACKWARE.COM
Slackware Linux, Inc.
3623 Sanford St
Concord, CA 94520
US
(925) 674-9124 fax: 999 999 9999


Record expires on 25-Dec-2015.
Record created on 26-Dec-1995.
Database last updated on 31-Dec-2010 17:54:05 EST.

Domain servers in listed order:

NS1.CWO.COM
NS2.CWO.COM
I guess it's definitely DNS problem as the domain itself has been renewed until 2015
 
Old 12-31-2010, 05:26 PM   #58
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875

Rep: Reputation: 282Reputation: 282Reputation: 282
Quote:
Originally Posted by willysr View Post
I guess it's definitely DNS problem as the domain itself has been renewed until 2015
DNS expiry is 24 hours for slackware.com
The whois data changed in the last 12 hours

Give it another 12-24 hours before assuming you have a problem
 
Old 12-31-2010, 10:44 PM   #59
acummings
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 615

Rep: Reputation: 50
Still needs 12 to 24 hours here in Sacramento, California U.S.A.

Via the IP the traceroute goes quickly there to the right place. But via name translation the traceroute keeps on trying and did it find a search engine?

Code:
al@P5Q:~$ traceroute 64.57.102.34
traceroute to 64.57.102.34 (64.57.102.34), 30 hops max, 38 byte packets
 1  home (192.168.1.254)  1.728 ms  1.228 ms  0.473 ms
 2  bras4-l0.scrmca.sbcglobal.net (151.164.185.16)  46.022 ms  46.100 ms  45.405 ms
 3  dist1-vlan50.scrm01.pbi.net (64.171.152.66)  45.069 ms  42.697 ms  43.455 ms
 4  151.164.98.64 (151.164.98.64)  45.140 ms  43.491 ms  43.291 ms
 5  69.220.8.31 (69.220.8.31)  48.894 ms  47.689 ms  45.261 ms
 6  198.32.176.29 (198.32.176.29)  179.355 ms  45.399 ms  45.583 ms
 7  tg9-4.cr02.sntdcabl.integra.net (209.63.115.129)  51.009 ms  52.818 ms  49.295 ms
 8  tg13-1.cr02.rcrdcauu.integra.net (209.63.114.169)  51.197 ms  51.261 ms  51.221 ms
 9  209.63.99.166 (209.63.99.166)  49.223 ms  49.494 ms  53.079 ms
10  208.186.199.158 (208.186.199.158)  51.143 ms  52.932 ms  49.705 ms
11  sac-main.cwo.com (209.210.78.20)  52.871 ms  51.283 ms  53.099 ms
12  slackware.com (64.57.102.34)  51.430 ms  53.497 ms  52.994 ms
Code:
al@P5Q:~$ traceroute www.slackware.com
traceroute to slackware.com (209.62.105.19), 30 hops max, 38 byte packets
 1  home (192.168.1.254)  3.772 ms  1.382 ms  0.465 ms
 2  bras4-l0.scrmca.sbcglobal.net (151.164.185.16)  47.228 ms  46.668 ms  45.420 ms
 3  dist1-vlan60.scrm01.pbi.net (64.171.152.130)  45.131 ms  41.794 ms  43.249 ms
 4  151.164.41.106 (151.164.41.106)  41.429 ms  41.679 ms  41.357 ms
 5  151.164.101.210 (151.164.101.210)  45.289 ms  46.686 ms  45.315 ms
 6  asn3356-level3.eqsjca.sbcglobal.net (151.164.251.246)  55.122 ms asn3356-level3.eqsjca.sbcglobal.net (151.164.250.138)  56.628 ms  56.746 ms
 7  vlan89.csw3.SanJose1.Level3.net (4.68.18.190)  63.118 ms vlan69.csw1.SanJose1.Level3.net (4.68.18.62)  68.324 ms vlan89.csw3.SanJose1.Level3.net (4.68.18.190)  56.566 ms
 8  ae-72-72.ebr2.SanJose1.Level3.net (4.69.134.213)  63.102 ms ae-62-62.ebr2.SanJose1.Level3.net (4.69.134.209)  69.117 ms  70.363 ms
 9  ae-2-2.ebr2.LosAngeles1.Level3.net (4.69.132.14)  61.210 ms  64.480 ms  57.117 ms
10  ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78)  98.675 ms  99.925 ms  90.848 ms
11  ae-71-78.ebr1.Dallas1.Level3.net (4.69.146.74)  92.452 ms  98.067 ms  90.752 ms
12  ae-1-13.bar1.Houston1.Level3.net (4.69.137.137)  96.407 ms  96.081 ms  96.595 ms
13  ae-0-11.bar2.Houston1.Level3.net (4.69.137.134)  96.532 ms  96.153 ms  94.549 ms
14  THE-PLANET.bar2.Houston1.Level3.net (4.78.10.30)  92.654 ms  94.240 ms  94.389 ms
15  e1-3.ibr01.hstntx2.networklayer.com (70.87.253.154)  94.717 ms  94.274 ms  96.350 ms
16  te2-1.dsr02.hstntx2.networklayer.com (74.55.252.150)  94.592 ms te2-2.dsr02.hstntx2.networklayer.com (74.55.252.38)  94.006 ms te2-1.dsr02.hstntx2.networklayer.com (74.55.252.150)  96.214 ms
17  po2.car3.hstntx2.networklayer.com (74.55.252.106)  94.448 ms po1.car03.hstntx2.networklayer.com (74.55.252.74)  96.282 ms  94.347 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
--
Alan.
 
Old 12-31-2010, 10:49 PM   #60
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097

Rep: Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275Reputation: 7275
It seemed "repaired" for a few hours, but now the same page is back, as I posted earlier, and Alien Bob's pages are also routed to the same page. Please see post #37, for the image.
Last edited by cwizardone; 12-31-2010 at 10:58 PM.
 
  


Reply
Page 4 of 5 « First 23 4 5



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NDISwrapper works for Slackware 13.0 x86 but not Slackware 13.0 x64 - Belkin F5D8053 thewizkid Slackware 0 01-14-2010 06:18 AM
LXer: Making Slackware and Slackware Derivative Linux Distros Speak Your Language LXer Syndicated Linux News 0 01-29-2009 12:30 AM
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 09:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:15 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration