You are hereForums / NoBMoB News / Site outage - Major D'oh!
Site outage - Major D'oh!
So... someone let the NoBMoB domain expire. It was renewed just now (Sunday morning) but a lot of people might well still see an outage.
It might be too late to mention this, but you can access all the NoBMoB content (and that from other Global Riders sites) on the below URL:
This site is kindof 'test' status and needs some work on the homepage and theme, but it gets the job done.
Of course, you could just login to any of the other Global Riders sites and so long as you have 'Always view content from nobmob.com' check in your profile (access and content) will be able to see all that content too.
Apologies for this. The head hamster will be taken out on a bike ride and fed to the first carpet Python we come across! 
- Login to post comments
- Bookmark & share
That's okay Rob, the organisation I work for almost let two entire Class B (/16) IP ranges slip a couple of years ago. I wonder what the street value of that would have been?
Thanks for bringing the site back up as I was suffering from withdrawal symtons .
Is anyone on iinet able to connect?
My home pc is on iinet and no that is still not working this morning. I guess their dns has not updated yet.
It should update eventually...
I'll send them an email now asking them to flush and update the entry.
cheers
Jon
It was down for me at home on Optus and at work. I flushed the DNS at work, and web proxy and all good now.
Phew - panic over
what are doing to us Rob ? you are taking away my umbilical cord , I need nobmob to stay away from the wife & tv , I can survive I know you will get things sorted soon .:)-
Still not working from my home iinet connection.
I received a reply from iinet support stating "The website www.nobmob.com is resolving from our DNS server now." however it doesn't look like they bothered to open it in a browser or check the IP address.
nslookup www.nobmob.com using the iinet dns server 203.0.178.191 gives the IP address 209.62.105.19 which is the Network Solutions page.
Other dns servers are resolving www.nobmob.com to 59.167.234.161.
I've replied to iinet asking them to check again and confirm the IP address.
cheers,
Jon
just checked again as of 20:20 still a no-show for us iinet users
goes to some other site
Wow... I thought iiNet were good guys. Pingability says everything is good and has done all day:
http://pingability.com/zoneinfo.jsp?domain=nobmo...
Does someone on their network feel like posting up what
dig nobmob.comgives?I do notice we have a rather short TTL - some ISPs might not like that and ignore it, replacing with their own (much) longer one?
; <<>> DiG 9.6.0-APPLE-P2 <<>> nobmob.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5325
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;nobmob.com. IN A
;; ANSWER SECTION:
nobmob.com. 6748 IN A 209.62.105.19
;; Query time: 2 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Mon Oct 18 21:45:32 2010
;; MSG SIZE rcvd: 44
Hi Rob
I'm on the phone to iinet now.
They're trying to fob me off saying they have no one available now who can help so I've asked for it to be escalated to someone senior.
See what happens next
iiNet support have been good in the past - today they are shocking!
@danielschipper
Looks like you've got 6748 seconds to wait
Ahhh... Perhaps this is what's going on: when the registrar record expired and the domain was delegated to a 'expired' domain holder they put up default DNS records to make all hosts resolve to their servers so that you get their 'expired' message when you try and load a page.
The DNS records for the 'expired' holder would naturally have massive TTL times on them because there would be loads of expired domains and these people want to lighten the load on their servers.
Thus, if you were unlucky to hit nobmob.com between the registrar being 'expired' and it being fixed sometime on Sunday (or perhaps only today - I'm not sure how long registrar updates take) then you will have caused your ISP to lookup the DNS record, get the 'expired' IP address and cache that for it's super long TTL. Now, everyone on that ISP will be getting expired records, even though a lot of other people won't.
Well - it's one theory anyhow?
@loki: to be honest, this probably isn't iiNet's fault - don't be too tough on them
6748 seconds is only 112 minutes. If the domain registration was corrected Sunday morning then that TTL of 6748 seconds has well and truly expired by now.
As for iiNet support - just got off the phone from them and they've basically said that there is no one available at this time of day to provide the level of support required to fix this problem, and it will have to wait until business hours tomorrow. (Probably Perth business hours too...)
I asked "What if it was a problem affecting a site such as google.com" to which they responded they would call an after-hours engineer to fix it. So I guess good old nobmob is not as important as google to get third level support involved outside of business hours
I told them I understood but was disappointed that the fault I logged this morning was not investigated and rectified properly in the first place, resulting in this problem now.
cheers
Jon
I can no longer see it on optus. This comment is made through bmorc.com.
@Loki - that number is the number of seconds remaining (out of what was probably 86400 - 24 hours).
When you 'dig' a domain if this isn't in the cache of the DNS server you hit, it loads from it's parent (or the top level parent) and caches it, for what should be the TTL (time to live) of the domain name record (5 minutes in the case of NoBMoB). On the first 'dig' this number will therefore be the total TTL.
If you 'dig' a few seconds later this number should have dropped by a few seconds as you're getting the cached record now and it will report the number of seconds before it will contact the parent (or top level parent) again.
So basically, it looks like iiNet got the 'old' (expired) DNS record sometime Sunday night (because registrar renewals themselves take some time to propagate and they could have still been talking to the 'expired' DNS servers) and will cache it for a day. Hopefully iiNet is therefore all good again now. Can anyone confirm?
Erm... I think
All working ok from iinet this morning
FWIW, the usage on nobmob.com was probably about half what you'd expect on Sunday, but on Monday (yesterday) was almost normal.
Optus is ok this morning.