| DNS weirdness |
[Jun. 23rd, 2009|10:44 am] |
Can anyone out there see: http://mytrapster.com/ or http://pics.mytrapster.com? I can see and ping them both from home, but neither work here at work. Both worked yesterday. Strangely enough, http://blog.mytrapster.com works in both places. It's DNS strangeness I've never seen before.
EDIT: It looks like I'm just going to have to wait for the DNS system at work to propagate. It all works at home. The dudes at Slicehost said everything as okay. I dunno. I'll try again tomorrow.
EDIT 2: Okay, now some of it doesn't work from home, but what doesn't work seems to coincide with my fiddling. It looks as if there might be an hour delay as the DNS settings shift down the line. So...I'm going to stop playing with it for a couple of hours and see what happens. It's frustrating to finally get Pikachoor, the tool I've been dreaming of for a while, built and then not be able to use it because the DNS went out. Grrr.
EDIT 3: Everything's back to normal. Yay! |
|
|
| Comments: |
yup, no issues.
Give 'er an ipconfig /flushdns .
Thanks for checking.
I tried the /flush, thanks for the idea, but no joy. I think it's our network (or DNS server specifically) as a whole, because I can't ping from any of my open shells either.
nslookup mytrapster.com, tell me the results
root@tenth:/home/students/www# nslookup mytrapster.com
Server: 207.157.86.99
Address: 207.157.86.99#53
** server can't find mytrapster.com: SERVFAIL
root@tenth:/home/students/www# nslookup blog.mytrapster.com
Server: 207.157.86.99
Address: 207.157.86.99#53
Non-authoritative answer:
Name: blog.mytrapster.com
Address: 67.207.147.108
Yeah, you've got a local nameserver with an old address stuck in cache. It'll clear itself up in a day or two depending on scavenging settings.
Hooray? :)
Thanks again for looking at it.
Working here, although the first took a strangely long time to come up.
Thank you for checking.
Me thinks Slicehost is having issues.
Edited at 2009-06-23 04:26 pm (UTC) | |