HOME

PIXUP

BLOGS

PROFILES

WIKI

RADIO

4826  members 15  members online 25  guests visiting 25,224  threads 1,186,795  posts

Forums > Site Feedback/Help > Outage 4th January 2010 - Jumba DNS issue

First Post: 04-Jan-2010, 10:54 pm Last Post: 06-Jan-2010, 3:23 am

Posts: 12 Views: 576

Outage 4th January 2010 - Jumba DNS issue

| 1 |

User #331     53782 posts Johnny Bravo Doomed Senior Moderator posted 04-Jan-2010, 10:54 pm	Due to a Jumba DNS issue, MCL is unreachable until they fix it	quote roast | froth | filter | anchor reply to this post | fling coaster
User #350     35221 posts The Lizard King Golani Sheli MCL Ninja posted 04-Jan-2010, 10:55 pm edited 04-Jan-2010, 10:56 pm	Expected fix time?	quote roast | froth | filter | anchor reply to this post | fling coaster
User #331     53782 posts Johnny Bravo Doomed Senior Moderator posted 04-Jan-2010, 10:56 pm	about now	quote roast | froth | filter | anchor reply to this post | fling coaster
User #331     53782 posts Johnny Bravo Doomed Senior Moderator posted 04-Jan-2010, 10:59 pm edited 04-Jan-2010, 11:14 pm	OpenDNS servers are right NOW googleDNS are not right yet - edit: OK now other propagations will take anything up to 24 hours! depending on many factors	quote roast | froth | filter | anchor reply to this post | fling coaster
User #721     4284 posts bruce MCL Addict posted 05-Jan-2010, 2:37 am	Can anyone from TPG access MCL? I'm still out-in-the-cold but all the DNS are returning the same IP - am logged in via vtunnel atm c:>nslookup mycoffeelounge.net 208.67.222.222 Server: resolver1.opendns.com Address: 208.67.222.222 Non-authoritative answer: Name: mycoffeelounge.net Address: 174.143.37.19 c:>nslookup mycoffeelounge.net 203.12.160.35 Server: dns1.tpgi.com.au Address: 203.12.160.35 Non-authoritative answer: Name: mycoffeelounge.net Address: 174.143.37.19 c:>nslookup mycoffeelounge.net 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: mycoffeelounge.net Address: 174.143.37.19 I've flushed my DNS cache and rebooted the modem - is that the right IP address?	quote roast | froth | filter | anchor reply to this post | fling coaster
User #1214     20610 posts skidmark Miss IT 1995 3.0 Beta Tester posted 05-Jan-2010, 2:56 am	iiNet here ok now was fucked tonight though	quote roast | froth | filter | anchor reply to this post | fling coaster
User #721     4284 posts bruce MCL Addict posted 05-Jan-2010, 3:07 am	It's just come good. Thanks.	quote roast | froth | filter | anchor reply to this post | fling coaster
User #331     53782 posts Johnny Bravo Doomed Senior Moderator posted 05-Jan-2010, 9:42 am	procyon50 writes... It's just come good. Thanks. TPG DNS = slow updates (that's why I opendns)	quote roast | froth | filter | anchor reply to this post | fling coaster
User #720     9133 posts Synta squwark MCL Post Whore posted 05-Jan-2010, 10:14 am	Johnny Bravo writes... TPG DNS = slow updates (that's why I opendns) "please restart your modem"	quote roast | froth | filter | anchor reply to this post | fling coaster
User #721     4284 posts bruce MCL Addict posted 06-Jan-2010, 1:14 am	Johnny Bravo writes... procyon50 writes... It's just come good. Thanks. TPG DNS = slow updates (that's why I opendns) Me too for some months now. Still curious why it wouldn't work - I opened firefox and MCL loaded. Back to Opera and MCL loaded.	quote roast | froth | filter | anchor reply to this post | fling coaster
User #331     53782 posts Johnny Bravo Doomed Senior Moderator posted 06-Jan-2010, 1:29 am	procyon50 writes... Still curious why it wouldn't work someone at jumba hit the wrong button, "sync all", causing "incorrect" records for most of jumba hosted domains that use jumba dns the first restore they performed was old data - hence why mcl pointed to the old IP address (a few months back I believe) they finally restored a backup from 31 december or something but it takes time to propagate through the DNS system MCL DNS entries have a 4 hour TTL - which means the average DNS server will consider any data it has cached for looking up "mycoffeelounge.net" to be valid if less than 4 hours old - so in theory it can take up to 4 hours for an IP change to be reflected in your chosen DNS server what adds to this, is that your local machine also "caches" dns lookups (in windows, clear this using ipconfig/flushdns, and I also suspect some browsers may do so (within a session, i.e. restart browser, cleans it's dns "cache") that could be why when you went back to opera (assuming you stopped opera all together) MCL worked - you didn't HAVE to try in firefox, the timing was such that the (previously wrong) information was "stale" in both your PC's dns cache, and in your selected DNS servers cache	quote roast | froth | filter | anchor reply to this post | fling coaster
User #721     4284 posts bruce MCL Addict posted 06-Jan-2010, 3:23 am	procyon50 writes... c:>nslookup mycoffeelounge.net 208.67.222.222 Server: resolver1.opendns.com Address: 208.67.222.222 Non-authoritative answer: Name: mycoffeelounge.net Address: 174.143.37.19 I've flushed my DNS cache and rebooted the modem Thanks for the info JB - the curious thing is that from my post above you'll see that opendns was returning the correct IP, and that was after I had flushed the DNS cache, rebooted the modem, and had also restarted Opera, yet Opera still barfed. I left Opera open, started Firefox and MCL loaded. Closed FF and MCL loaded in Opera. Time to cue the twilight zone music.	quote roast | froth | filter | anchor reply to this post | fling coaster

| 1 |

Forums > Site Feedback/Help > Outage 4th January 2010 - Jumba DNS issue

First Post: 04-Jan-2010, 10:54 pm Last Post: 06-Jan-2010, 3:23 am

Posts: 12 Views: 576

QUICK POST

PixUp: click here to upload a pic into your post with PixUP! (opens in new window) Smileys2 This thread is in an On-Topic forum. This means that posts that are not related to the topic, may be removed. Excessive removal of your posts may result in your account being banned from posting in this forum. Special rules also may apply to this forum.