I am still unable to get to DU from my workplace, except through proxy.

[Lisa0825]

Some others on a DU Facebook group are still having problems too. Can this really be just an issue of waiting for DNS info to propogate, or is something else going on here? Anyone else still having problems, or know of others who are?

[pipoman]

1. The fact you can get on through a proxy

only bolsters the theory of slow propagation. Skinner said that months after he first changed his whois address it was still not on all dns servers.

[Lisa0825]

2. OK, thanks. I had read where several people said "up to 72 hours,"

so I thought something else might be wrong.

[hlthe2b]

3. I'm sorry to hear that... as that was my fear...

My ISP is problematic in that way, which led me to my little meltdown well into day 3 after the problem started, when every work around I tried failed. I'm :blush: to say I was wrong and it just came back up on its own--which makes me likewise convinced it will eventually work its way out for you as well.

I can really empathize because I know how it felt (and how frustrating it was) to think I might be the only one that couldn't find a resolution. But, fortunately, I was wrong. Hang in there.

[Lisa0825]

4. At least I can get through by proxy, but not all functions work that way.

And at home, I don't think I was ever offline, or at least it was during the workday and back on by the time I got home.

[TreasonousBastard]

5. Your workplace may have it blocked. After all, you're supposed to be working.

[Lisa0825]

7. Nope... they are really lenient. As long as we're not visiting

porn sites or other "offensive" sites, they don't care what we do on our downtime, lunch breaks, etc. They even say so at orientation. As long as we are productive and not causing problems.

[kenny blankenship]

6. You can tell if it's a DNS issue by querying your nameserver

open a console window and type "nslookup www.democraticunderground.com" without any quote marks. You will get something like this, although not exactly the same:

nslookup www.democraticunderground.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
Name: www.democraticunderground.com
Address: 216.158.28.195
Name: www.democraticunderground.com
Address: 216.158.28.197
Name: www.democraticunderground.com
Address: 216.158.28.199
Name: www.democraticunderground.com
Address: 216.158.54.195
Name: www.democraticunderground.com
Address: 216.158.54.197

nslookup will report the server address it used for name lookup - the line may begin with "Default Server ". That will probably be a server operated by your employer. If there is no answer section giving those DU addresses (216.158.xx.xxx) then your nameserver hasn't got the word about DU's current location. It may be possible to add a public nameserver to your system's configuration. But you won't want to replace your employer's nameservers completely. That would be sure to lead to trouble with connecting to services on their network. But it may also be possible that your work system is locked down and you won't be able to change its configuration to add a public nameserver.

If the name www.democraticunderground.com resolves on your nameserver but you still can't get here without going through a proxy, then it may be that your employer is blocking access to this site through their own proxy server.

[Lisa0825]

8. I actually finally got through without the proxy....

and it turns out that sometime since Friday it may have started working, but adding the DU info to the "host" file seemed to be actually causing a problem rather than solving it. Every other day I tried with or without that info which I had read in one of Skinner's posts (go to system32>drivers>... I don't remember the rest right now.... and then add the IP and url to the host file). I had left it in on Friday, and when I took that out today, I finally got connected.