Archive for August 6th, 2006

SDR Podcast 2006-08-06 Weekend Summary

Play


SDR 125x50 Today’s Headlines Include…


    • Proxy Sites Offer Secret Passage to MySpace
    • VoIP Numbers Stations Finally Explained
    • NSA – A Number One Customer

    Podtrac Player
    Prefer a Direct Download ? (mp3)

    Download today’s show.

    Today’s Artist

    Desert Radio

    Track:Redwood Tree [3:06]
    Comments

    Add to Google
    Weekend Upgrade – of Sorts

    by Andrew McCaskey
    Slashdot Review Podcast

    It’s been over a year since I’ve spent much time describing the trials and tribulations of keeping a podcast service on the air. Sometimes the best of intentions don”t turn out exactly as planned, and this weekend was no exception. Friday night – in the wee hours Saturday, I had the folks at GoDaddy add a dedicated Cisco firewall to the server for SDR, trying to improve the overall reliability of the service. We have been operating over a year without problems The work went smoothly, and I was well prepared with printouts of the FAQ for some minor dust-up work early Saturday morning.

    In the world of storytelling, this is known as foreshadowing. I’ll keep the story short, and let you know that in spite of these well laid plans (which professional Sys-admins refer to as letting children playing with razor blades) my re-configuration of the server went off in the wrong direction and slowed things down this past weekend – delivering late shows to some listeners – and delivering the Plesk log in screen – the equivalent of the old TV test pattern in this digital age – to those trying to view the site at Slashdotreview.com.
    —-

    When they (GoDaddy) installed the firewall sometime after midnight Friday night, the external address was put onto the Cisco box, and the internal 10.0.0.1 was set up. I went in and mapped the physical address on the server using Plesk – but that set each of the domain zone records to 10.0.0.1, and each of the domain records had to be remapped to the external IP.

    Well, that error propagated like crazy. Add some nameserver confusion and after some valiant efforts I got to exercise the premium support line. It was back up within a half an hour , and using OpenDNS all was right within about twenty minutes. However, all was not right in the outer reaches of the system – such remote spots as Verizon and Comcast. I was getting reports from listeners as late as Sunday afternoon that the bad DNS record had gone forth, and the good correction had not yet caught up.

    It looks like there were lots of confused podcatchers left in the dark at some point.

    The good news – if you are hearing this, it’s all fixed. Like it never happened.

    Thanks for your patience.

    Recent Show Notes


    Save $10 on any order of $50 or more at GoDaddy.com!
    Be sure to sign up for our upcoming roundtable. We will be using GoToMeeting. Also, be sure to check out GoToMeeting. Why? Because you can hold meetings right over the Net — from anywhere. Plus, you can hold all the meetings you want for one flat rate. To get your free 30-day trial , visit www.gotomeeting.com/techroundtable.

    Enter your Email


    Powered by FeedBlitz

    468x60_free_email_10.gif