I've been getting this the last couple days. Doesn't last long as I'm able to get on after a few minutes, but still....

Not me.

No, but for those experiencing issues, 'Jessica' and her team are 'working the problem'...

No

Okay then, what causes this? Any particular issues to examine at my end? Or is it my ISP?

Try switching DNS settings on your router to something else?

The OpenDNS nameservers are 208.67.222.222 and 208.67.220.220

I think Google's is 8.8.8.8

quote:

Originally posted by bald1:
Okay then, what causes this? Any particular issues to examine at my end? Or is it my ISP?

Is that on a phone or some kind of Samsung device? It's an issue with your ISP or the DNS your ISP/Cellular network is using.

quote:

Originally posted by DonDraper:

quote:

Originally posted by bald1:
Okay then, what causes this? Any particular issues to examine at my end? Or is it my ISP?

Is that on a phone or some kind of Samsung device? It's an issue with your ISP or the DNS your ISP/Cellular network is using.

Yup.... my Samsung cellphone.

I've seen it several times over the last... week? or so.

quote:

Originally posted by bald1:
Okay then, what causes this?

Many possible causes. It's never lasted long enough for me to get to my computer and begin diagnosing it.

quote:

Originally posted by bald1:
Any particular issues to examine at my end?

Not unless you have more tech chops than I suspect (No offence meant, but, DNS issues can be tricky to troubleshoot even for the very tech savvy.)

quote:

Originally posted by bald1:
Or is it my ISP?

Unlikely, since I've seen it, too.

quote:

Originally posted by DonDraper:
It's an issue with your ISP or the DNS your ISP/Cellular network is using.

Nope. See above.

^^^^^^^^^^^^^^^^^^^^

Thanks... not alone on this.

It's a minor irritant all things considered, but ....

And yeah, my "tech chops" have degraded with my advanced age and lack of time/commitment to keeping abreast of things. No offense taken!

quote:

Originally posted by bald1:
Thanks... not alone on this.

Well, the good news is it never seems to last long

My SWAG, based purely upon the symptoms and what I know of how the DNS system works, is temporary failures in SF's host's DNS servers or one-or-more of the routes to their DNS servers, but, as I noted, it's never lasted long enough for me to nail it down.

It's either an ISP or a device problem. Could be your device asks the ISP to visit sigforum.com and then disconnects long enough for whatever reason while waiting for the name to get resolved to an IP address. Could be your ISP having trouble contacting a DNS server in a timely matter (for a number of reasons behind the scenes). On your PC you can create a host file entry for sigforum.com or whatever you're getting to, so you don't need to use DNS.

quote:

Originally posted by DonDraper:

It's either an ISP or a device problem. Could be your device asks the ISP to visit sigforum.com and then disconnects long enough for whatever reason while waiting for the name to get resolved to an IP address. Could be your ISP having trouble contacting a DNS server in a timely matter (for a number of reasons behind the scenes). On your PC you can create a host file entry for sigforum.com or whatever you're getting to, so you don't need to use DNS.

I thought that recently resolved IP addresses were cached locally. Is this not correct?

quote:

Originally posted by V-Tail:

quote:

Originally posted by DonDraper:

It's either an ISP or a device problem. Could be your device asks the ISP to visit sigforum.com and then disconnects long enough for whatever reason while waiting for the name to get resolved to an IP address. Could be your ISP having trouble contacting a DNS server in a timely matter (for a number of reasons behind the scenes). On your PC you can create a host file entry for sigforum.com or whatever you're getting to, so you don't need to use DNS.

I thought that recently resolved IP addresses were cached locally. Is this not correct?

Windows will cache it for at least a day, no idea on a Samsung Android phone though...

quote:

Originally posted by DonDraper:

quote:

Originally posted by V-Tail:

I thought that recently resolved IP addresses were cached locally. Is this not correct?

Windows will cache it for at least a day, no idea on a Samsung Android phone though...

I'm using MacOS. Looking back through this thread, I now realize that OP is using Android.

Hmmm . . . MacOS is based on Sun's release of UNIX, Android is based on Linux, which is a UNIX work-alike, if that's relevant.

quote:

Originally posted by DonDraper:
It's either an ISP or a device problem.

Read the rest of the thread, please.

quote:

Originally posted by V-Tail:
I thought that recently resolved IP addresses were cached locally. Is this not correct?

Yes: For a set amount of time, which is established by a DNS field known as "TTL" (Time To Live).

quote:

Originally posted by DonDraper:
Windows will cache it for at least a day, ...

That is not correct. At least not unless Microsoft is violating the DNS protocol.

quote:

Originally posted by V-Tail:
Hmmm . . . MacOS is based on Sun's release of UNIX, Android is based on Linux, which is a UNIX work-alike, if that's relevant.

It is not relevant, nor is that quite correct. MacOS X is partially based upon BSD Unix which is what SunOS was based upon. (Sun later switched to AT&T System V with Solaris.)

Another data point (which I'd forgotten about): I've lately occasionally seen email sent to my server by SF temporarily rejected because, when my mail server tried to do a reverse DNS check (that's asking for the hostname to which an IP address resolves) of the sending server as part of its validity tests, my DNS server was temporarily unable to obtain an answer.

Just because you experience it too, does not mean it's not his ISP or his device (software or hardware). I've never had the issue, on pure Android, Windows, IOS, various Linux distros.

bald1 do you see that with ONLY sigforum.com?

Only with sigforum and only on my Samsung android phone

Bald1 I occasionally have the same message and issue with my minimac tablet

Samsung here, never any issues.
I don't know if this matters but chrome now leaves all tabs open. Started last spring, so now you have to close all tabs yourself. Maybe this is your issue.

.