SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, i can confirm that via IP 64.57.102.34 I get the slackware site whereas via name I end up on an advertisment-site of Network-Solutions. I'm in Germany.
Hi, i can confirm that via IP 64.57.102.34 I get the slackware site whereas via name I end up on an advertisment-site of Network-Solutions. I'm in Germany.
Markus
Same here, in the UK. The thread says "[SOLVED]", but what's going on?
Hi, it is definitely a DNS-issue. It depends on the DNS-server which I insert in my /etc/resolv.conf.
The problem is that I don't know if/how I can flush the DNS-cache of my router (which normaly is my nameserver). Restarting the router did not help.
But if I insert an external DNS-server in my resolv.conf I can open slackware.com via it's name.
So it seems that definitely slackware.com is not down.
Markus
Last edited by markush; 12-31-2010 at 10:46 AM.
Reason: typo
You can use the google name servers 8.8.8.8 or 8.8.4.4
They still resolve slackware.com to the right IP
Hi bathory,
Not from here they don't:
Code:
eric@ericvs-laptop:~$ dig @8.8.8.8 slackware.com
; <<>> DiG 9.7.1-P2 <<>> @8.8.8.8 slackware.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61324
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;slackware.com. IN A
;; ANSWER SECTION:
slackware.com. 4474 IN A 209.62.105.19
;; Query time: 56 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Dec 31 18:19:40 2010
;; MSG SIZE rcvd: 47
eric@ericvs-laptop:~$ dig @8.8.4.4 slackware.com
; <<>> DiG 9.7.1-P2 <<>> @8.8.4.4 slackware.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49449
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;slackware.com. IN A
;; ANSWER SECTION:
slackware.com. 4465 IN A 209.62.105.19
;; Query time: 75 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Fri Dec 31 18:19:48 2010
;; MSG SIZE rcvd: 47
Looks like every DNS server and cache is catching up. The only thing I get when surfing to www.slackware.com is the main page, when clicking on any link I also get the 'other site'.
Looks like your Google DNS Cache is still not updated like the rest of us You're falling behind bathory...
That doesn't make sense
Cache should expire at the same time for all.
Anyway PV must be notified somehow, because the domain is still in "Pending Renewal or Deletion" since a week ago. Quoting from NS Domain Deletion Policy
Quote:
We currently endeavor to provide a grace period that extends 35 days past the expiration date, to allow the renewal of domain name registration services. During this period a customer can renew a domain name registration; however, a grace period is not guaranteed and can change or be eliminated at any time without notice. Consequently, every customer who desires to renew his or her domain name registration services should do so in advance of the expiration date to avoid any unintended domain name deletion.
there is a risk that someone else could buy the domain.
That doesn't make sense
Cache should expire at the same time for all.
Hi,
I know it doesn't make any sense but there possibly is a delay in expiration. I recently changed jobs, administering a global content delivery network, and we run our own DNS (PowerDNS). I'm still in the process of learning a lot but believe me, I already have seen some strange behavior between the regional DNS servers we have set up. As you say they should expire/update at the same time but they just not always do. I guess that's Murphy knocking at the door.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
You're falling behind bathory... 
