grump.

[electricland]

Next time I say "Hey guys, I'm getting a DNS error with site X, can you check it please?" I'd appreciate a more helpful answer than "Well, it works fine from my machine." From the frelling NETWORK ADMINISTRATOR.

Oh well, it's getting fixed tomorrow. (The reason for the problem is probably quite simple if you have more technical knowledge than I do -- apparently they need to update the DNS entry and the firewall so it's visible from outside our network. ?????)

That is all.

[ETA: except, thanks raithen for helping me prove that it was not, in fact, just me.]

Comments

[cretkid.livejournal.com]

speaking as a network administrator, we are told to give such pithy answers: it is part of our training. :-)

no seriously... we had a problem yesterday because some fekkik decided to change his IP address without telling me, thus making HIS dumbass little machine MY server for about 12 hours (as he changed the addy the night before)...

and we have our system set so that only known IP addresses of OUR machines can see our network and print to our printers and whatnot... dealing with firewalls is a pain in the ass :-)

[electricland.livejournal.com]

*sigh* I wouldn't mind except with the flurry of back-and-forth and we're-going-live-with-this-today-guys, you would hope that SOMEONE would think to check to make sure that the site is in fact visible from outside our firewall. (Not to mention that the project is 6 months old and it looks like we had a "temporary" redirect to a different site set up back at the beginning, which isn't working any more.) But apparently not. Oh right, it's my job to think of everything.

Lucky my client's easygoing.

I still don't get why I can't see it, though. I'm right here in the building. Everyone else can see it. Must be some freak setting from somewhere...

*sigh*