I received a response from the web host support desk about the problem that is causing the WebProp update scripts to fail to access the WWV solar data. The reply was:
There is nothing we can do to fix this it's a configuration error on their end with their dns. This is occurring because of invalid dnssec configurations at noaa.gov. We will not bypass the dnssec configurations implemented within .gov. The only way to have this corrected is by the dns administrators at noaa.gov signing their zones.
20-May-2010 15:26:00.099 validating @0x827fff000: swpc.noaa.gov SOA: got insecure response; parent indicates it should be secure
20-May-2010 15:26:00.116 validating @0x80284f000: swpc.noaa.gov SOA: got insecure response; parent indicates it should be secure
20-May-2010 15:26:00.159 validating @0xadb055000: swpc.noaa.gov SOA: got insecure response; parent indicates it should be secure
20-May-2010 15:26:00.204 validating @0xad9af8000: www.swpc.noaa.gov A: bad cache hit (www.swpc.noaa.gov/DS)
This is way over my head, but I think they are saying this is due to a problem at NOAA's end not mine.
I will give it a couple more days, but if the problem doesn't go away then I will have to remove WebProp. I know this will be a pain for those who have included it in their websites but there is nothing I can do about it.