I can tell that most people still have no access to Freethoughtblogs because of this DNS snafu, so I think I’ll go back to bed for a bit, and then putter off somewhere and tinker on other projects. Yell when you can see this.
Pharyngula
Evolution, development, and random biological ejaculations from a godless liberal
Well, I can see it. I had to edit my hosts file, though.
Waves
Last night I just kept refreshing until the browser connected to the right servers… Seems OK today.
</sigh>
Followed a numerical link from the NatGeo pharyngula site and bookmarked it. Seems to be working for now, Russell’s Teapot be praised!
Freethoughts is accessible to me again this morning. This must have happened within the last six hours or so (while I was sleeping the sleep of the innocent).
Oh, that’s right. You wanted us to yell:
Hey, PZ! It’s back!
All good. :)
Works for me. I haven’t actually noticed an outage. Although I’m mostly connecting in Australia hours (UTC+10).
Looks good now, PZ, thank you. I can see this and post from work, too. Thanks for that as well.
Works for me.
Maybe because i’m in Germany. Who knows.
The “whois” command mentions fastdomain and bluehost.
Name servers used:
I see you!
I can see this fine while logged in through the work server, PZ; thanks for that.
Hmm. Can’t seem to post though, unless this and the two messages before it are held up in moderation.
I seeeee it. This morning was the first time since the whole messup started.
This just appeared in Google Reader…
*waves madly*
Helloooo! Anybody there!
I needs me my fix of PZ…. I needs to pharyngulate regular, like!
(Yells out) “Captain CAAAVVVEEEMMMAAANNN!!!”
I’ve had no problems at all accessing this site since late last night.
Does this mean it’s our turn to hide now?
I prayed to Jebus and Mo and here you are!
It’s a miracle…
I can see it here in California. My results using Whois are the same as Ospalh’s
If I use my ISPs DNS addresses I am unable to see this site. If I use the OpenDNS addresses, (208.67.222.220 and 208.67.222.220) I can.
I can see it
I couldn’t get here on my phone, but I can on my home PC.
Also, I echo your sentiments on the layout of FTB. Its very “grandmom’s got her own blog!” Though, it isn’t terrible, it would be a turn-off if I didn’t already know the content was going to be worth a look.
I have never had a problem with freethoughtblogs yet (New Zealand, Firefox, Archlinux).
This may be because of the time difference, as someone already suggested, but on the other hand it’s 12.34 a.m. local, so maybe not.
YELL.
No problem accessing this morning, needed no technical wizardry or OpenDNS or such nonsense.
“Spooooooooooooon!!!”
You didn’t say what I should yell.
yell
I can see this.
It’ll work for me without a hosts entry in 71208 seconds:
;; AUTHORITY SECTION:
freethoughtblogs.com. 71208 IN NS ns1.bluehost.com.
freethoughtblogs.com. 71208 IN NS ns2.bluehost.com.
or sooner if I flush my local nameserver’s cache.
Works.
Rebel yell!
No problem with from Poland. DNS resolving works fine all the time.
In a related complaint… why is FTB the only site online that will not update when I return to a page? The posts don’t change without a hard F5 refresh. I realize the page is being cached, but shouldn’t firefox notice the page content has changed?
Ooops. Spoke too soon. Flushed the resolver cache and it went back to the bluething thing. I’ll stick with the host file entry for now.
I can’t see it.
Works fine, UK with Opera browser.
No problem here.
I’ve had no problem accessing this site at all, not once (yet…)
In Australia, using Safari on a MacBook.
The entries have been available all along through Google RSS, but the actual site and images hosted there haven’t been accessible. From where I am in Canada that only lasted for about a day, though.
YELL!
Works correctly in the Netherlands.
I can see! It’s a miracle!
::waves:: UK, Firefox, waiting happily for eventual css changes and other tweaks (with some display issues already resolved thanks to the loveliness of people like owlmirror and caine et several alii, to whom much thanks)
I can see clearly now (the rain is gone).
See, I said the problem wasn’t fixed. Part of the problem was fixed but if lots of folks have trouble getting here then the problem is not fixed.
I’m accessing without problems, due to a hosts file entry.
Last night, I checked my ISP’s dns servers. They were giving the wrong answers, and the wrong NS records they were using had a TTL of around 100,000 (a bit more than a day)
I checked again this morning. My ISP’s dns servers appear to all be giving the correct answers.
Note: ISP is AT&T; the particular servers that I see are regional, so not all AT&T customers will see the same servers. All customers may use the same DNS server IPs, but those IPs are for load balancing contraptions.
I see it. No tentacles?
Edited my hosts file.
Still doesn’t work in the UK without a hosts file update
mine is working now. I didn’t do anything.
I can see it.
I seem to need a Ctrl+F5 to get the latest contents though – otherwise, I’m not getting the latest content from the web servers. Guessing these pages need a content expiry flag set to prevent the browser from caching it.
I can see it, no tricks required.
I tinkered with the address box.
I don’t know that that is what got me here.
all my bookmarks from yesterday work after I’m here.
It seems as though the new IP address has not being fully propagated to the DNS servers yet. Some ISPs are known for only updating their DNS servers once or twice a day.
*yelling*
I read you loud and clear! I just never have much to say.
– Bill
This Euro is having no problems at all logging in or viewing. I was particularly pleased to be greeted with an image of the elusive crocoduck upon my arrival as well.
Gooooooooooooaaaaalllll! (From home, anyway.) But I still can’t post here.
Brand new spanking WordPress account, I’m good to go, finally.
My ISP has now updated its DNS servers.
If anyone is still having problems connecting, and they are running Windows try the following command at the command prompt:
nslookup http://www.freethoughtblogs.com
and post the results.
Err, remove the http.
WordPress decided to add that itself!
I can log in OK – but have to zoom the comments in order to read them (good ol’ Opera) which seems strange
Had no problem about 6 am central using Comcast at home. At work, unable to link until a couple of minutes ago.
I can see the page from home, but I had to do a workaround to get it at work.
Also, after this is resolved, there’s possibly another technical issue to look at. The comment system is not forcing logins. All somebody needs to do to impersonate me is put in my username and the email address associated with my WP account, and it will look like a post from me.
On HughesNet:
* http://www.freethoughtblogs.com => parking page
* freethoughtblogs.com => the actual site
* freethoughtblogs.com/pharyngula => Pharyngula II
* http://www.freethoughtblogs.com on Opera Mini => the actual site
I’d suggest omitting the www. prefix before mucking with the hosts file, or, failing that, using Opera and activating the turbo feature.
PZ has already said that it will be required to login before being able to comment, but that he has not implemented that policy yet as he wants to get other stuff working properly first.
Ah! Thank you, Matt. I missed that.
I can see it. The title didn’t show up properly in my RSS though.
Looks good… ish, PZ. I have a strange issue, though, in that if I click on the banner (currently the crocoduck) to get taken to the main pharyngula site on FTB, I get taken to the main site, only the postings start with the “How am I going to fit an MRI in the bedroom?” post. Perhaps it’s a cache thing.
Hooray, it works for me!
@co:
Try a Ctrl+F5 refresh – should dump your cache
Yell!!!
I can read this fine.
I can’t see it.
Works fine for me.
I can see you.
hm, works for me.
I can see you.
The original links were n/g but I connected through the link you last posted on your old site.
I can see it, but not on my phone. More importantly at last I can comment. Yeah
Peek-a-boo, yep I can see you
The new site is working for me this morning. However, I follow Pharyngula through Google Reader and I did have to unsubscribe from the old address and resubscribe using the new address. Once I did that, things seem back to normal.
I can see it, for what it’s worth.
I can see it now!
No problems from here, either.
Yeah! It’s finally back for me. One of my favorite links to sanity in the raving lunacy of ultra conservative, bible thumping west Texas.
We are here, we are here, we are here!
YAWP!
(Blame Cuttlefish. He got me thinking Suess with his Sneetches!)
I had to mess with my hosts file this morning here at work.
BTW, Could someone repeat the OS X (Snow Leopard) .css filename & location for Firefox?
Just managed to get into after running
ipconfig /flushdnsVisible in Louisiana–we’ll see after the creotard sysadmins get out of morning church if it stays up.
I can see it!
Speaking of [sigh] – Goldline ad with Glen Beck’s mug on it? Yeesh.
arg. ns1.codero.com and ns2.codero.com still have the wrong fucking dns records.
They still point to bluehost.
The Chimp’s Raging Id
Just managed to get into after running ipconfig /flushdns
I was going to recommend this.
I can see it.
I finally got through about half an hour ago.
I can see it yet again.
My last few tries, I couldn’t post.
maybe this time
Works now!! I had to delete the bookmark and the tab first to stop the browser from going to bluehost.
Looking good here in Colorado, no problems at all getting in.
I don’t understand any of the technical stuff (css, DNS, IP) but I can see you!
I can see it, and I can even comment – provided I don’t log in
AHA!! I can see you now. *clings* I’ve been missing my Pharyngula fix.
It’s always frustrating to start something new that doesn’t work quite right at first.
But Pharyngula is hands-down worth it. :)
Never missed it (I wasn’t online during the DNS switchover-gone-fubar), and it came up fine last night when I did get back to the computer.
And WarriorGirl thinks the CrocoDuck is AWESOME.
It works for me.
Text size of comments are tiny compared to the post. /Rick
AAaaaaAaaaaAAAaa aaaAaaa aaaAAAAAa aAAAAA AAAAAAA AAAaAAAA aAA AAaAA!
(Catches breath)
AAaaaaAaaaaAAAaaaaaAaaa aaaAAAAAaaAAAAA AAA AA AAAAAAAaaA AaaaaAAAaaaaaAaaa aaaAAAAA AaaaaAAAaaaaaAaaa aaaAAAAAaaAAAAA AAA AA AAAA aaAAAAA AAA AA AAAA AAAAAAAAAAaAAAAaAAAAaAA!
Is that enough yelling? Getting a bit hoarse over here…
12:08 pm Oregon time, I finally could find the site again. Can’t get here from Firefox, it’s glued to Blue host something.
Obligatory yell.
GAAAAAAAAAH!
The hosts file trick mentioned over on the other blog works well for me.
It came up via normal DNS for me at this time (3:55 pm EDT). Pretty sure I tried with no success about 3 hours ago.
I can see this from home but now both Sciblogs AND FTB is blocked at work so I can only respond when home.
However, I do have to thank Richard Austin for helping me get the IP address inserted so I can read this (therefore I don’t know if the DNS is fixed or not)
And obviously stress and getting home from work messes up my grammar.
Ahem. …both Sciblogs AND FTB are blocked at work…
I can see the site, although I could not, in multiple attempts, earlier today. I considered editing my host file, but decided to wait things out.
I switched my gateway’s DNS forwarder over to use OpenDNS’s servers, and the problem goes away.
…Did I mention that I hate my local cable comapny and their crappy internet service?
What is a host file?
I can see it without having changed my “hosts” file.
I’ve been obliged to use an addition to the Mac OS X hosts file since the move, and from my Internet connection here in Melbourne, AU, the DNS was still pointing to Bluehost as of 2:40 UTC on Wednesday, so the propogation of the new address is still trudging along slowly.
A hosts file is a configuration file which tells a computer the specific numerical IP addresses for other computers and their associated domain name. Normally DNS resolution from outside just works, so that the local hosts file residing on your computer only refers to “localhost” – which is your own computer, and which always has an IPv4 address of 127.0.0.1 (and a couple of IPv6 addresses such as ::1). The problem is, external DNS is b0rked and so it’s useful to add a hack to tell the computer to use a specific rule associating FTB to a particular IP address, rather than relying on normal external resolution.
On Macs, it takes a few seconds to add the hack: use the Terminal application in the Utilities folder (Command+Shift+U), type
sudo pico /private/etc/hosts(or substitute your favourite Unix editor – no vi versus emacs wars please!), hit return and add the following line at the end of the file:64.150.191.229 freethoughtblogs.comThen save the file and do a hard reload in your web browser.
(I know the instructions are superfluous here at FTB, but similar posts have been made over at Sb.)
I can see everything okay, but the load times are so long, it’s hardly worth it. Every time TET reaches 400 comments, the thread is damn near impossible to load and gravatar hangs for close to forever.
Present!
re: hosts files
Thank you.
We’ve got lumps of it round the back.
Haven’t had any problems from here in Thailand since you first moved.
In the UK, still kept getting the wrong holding page on a bookmark/favourite til just now for last few days but I then went back to PZ’s old site, followed the link to freethoughtblogs homepage then clicked through to PZ’s new homepage OK.
So try refreshing your browser bookmark/fav by relinking via the old site or FTB’s new site if that loads for you.
No longer redirecting to Bluehost as of ~ 1200 UTC… and commenting seems to have picked up. No surprises there.
The small banners are missing from all but Pharyngula.
The pop-under ads are driving me nuts.
The posts seem out of date and incomplete. Maybe just me.
Never had any problems actually since the first problems thread.