problems reaching linux-noob

[inittux]

I've been having problems reaching linux-noob. It's really random. Sometimes I can just enter the website link: www.linux-noob.com or linux-noob.com and I got the website.

Other times is says the page can't be found, I then google linux-noob and I get the website and sometimes when I google it I also get: page cannot be found. I tried clearing

my cache, but I have this problem with chrome, firefox and IE and I have it when I'm in windows and when I'm running on linux and I have it when I'm at work. All other

websites seem to be loading fine. So since I have the problem at work and at home it can't be on my side. So probably on the server side? I hope you can take a look at

this? If you need anymore info just let me know :) I'll try and see what happens when I only use a proxy to access the website and see if it makes a difference.

[anyweb]

can you reach other sites at the same time ? i havn't noticed any connection problems to the site, thankfully

so are you getting errors with google also ? could you be having connection issues ?

[inittux]

can you reach other sites at the same time ? i havn't noticed any connection problems to the site, thankfully

so are you getting errors with google also ? could you be having connection issues ?

 

 

I am able to reach other websites at the same time, but I'll I'll try it more specifically next time it happens.

But just strange that it happens from both with my home internet connection and at work too.

[inittux]

I've tried and visited the website today at work quite a few times and no problems. Will try again at home this evening. If still have the problem at home it must be that something on my providers side that's causing it.

[Dungeon-Dave]

When it occurs, can you perform a nameserver lookup and see what gets returned?

[inittux]

When it occurs, can you perform a nameserver lookup and see what gets returned?

 

Sure I'll do that, with this?

 

http://whois.domaintools.com/ or http://network-tools.com/

[Dungeon-Dave]

no, just use the "host" or "nslookup" commands - curious to know what your machine resolves the domain name to (rather than what another website resolves it to)

[inittux]

no, just use the "host" or "nslookup" commands - curious to know what your machine resolves the domain name to (rather than what another website resolves it to)

 

At work it seems to be working fine now just at home I get this problem now.

under windows I get this:

 

C:\Users\Maarten>nslookup www.linux-noob.com

Server: dsldevice.lan

Address: 192.168.2.254

 

*** dsldevice.lan kan www.linux-noob.com niet vinden: Server failed

 

C:\Users\Maarten>nslookup http://linux-noob.com

Server: dsldevice.lan

Address: 192.168.2.254

 

*** dsldevice.lan kan http://linux-noob.com niet vinden: Non-existent domain

 

2nd Time under windows:

 

C:\Users\Maarten>nslookup www.linux-noob.com

Server: dsldevice.lan

Address: 192.168.2.254

 

Niet-bindend antwoord:

Naam: www.linux-noob.com

Address: 94.75.228.161

 

C:\Users\Maarten>nslookup http://linux-noob.com

Server: dsldevice.lan

Address: 192.168.2.254

 

*** dsldevice.lan kan http://linux-noob.com niet vinden: Non-existent domain

 

 

seems like the problems is with my dsldevice because 192.168.2.254 is my way to connect to my modem.

 

I have it setup like this. I have my ISP modem(192.168.2.254) downstairs, I pulled a network cable to my upstairs room and I connected it to my linksys router(192.168.1.1), and my router connects to my pc and laptop. Didn't have time to try it on linux last night will try to do it this evening. But will probably get about the same results since it seems like it's my dsldevice causing problems.

[Dungeon-Dave]

It could also be the (local) DNS cache - some platforms cache queries for longer, masking the smaller pool (or delayed lookup) that other devices have.

 

If you want to bypass those problems - particularly for this forum - then consider hard-coding our IP address into your local HOSTS file. This should speed up resolution for this site, but it also means that you've got the added burden of updating the (local) IP if the server moves.

[inittux]

It could also be the (local) DNS cache - some platforms cache queries for longer, masking the smaller pool (or delayed lookup) that other devices have.

 

If you want to bypass those problems - particularly for this forum - then consider hard-coding our IP address into your local HOSTS file. This should speed up resolution for this site, but it also means that you've got the added burden of updating the (local) IP if the server moves.

 

That would mean under linux under /etc/hosts right and under windows I'll be able to find it.

It's a matter how you look at it, don't find it much of a burden. Not being able to access

www.linux-noob.com is a burden :P