I hope this makes it out. Service has been spotty over the last few hours.
pdxlinux.org is hosted on Wil Cooley's server, nakedape.cc , and nameservice is via ns1.nakedape.cc . Nameservers for ns1.nakedape.cc include ns1.everydns.net through ns5.everydns.net . dyn.com somehow acquired everydns.net, and is discontinuing it, encouraging users of this free dns service to migrate to dyn.com for the low low price of $5, aka more than free. And they are encouraging the migration by rerouting dns to a nag page telling people to move. This happened earlier this evening when I was trying to get to the pdxlinux.org website, and may be screwing up your postings to the list. Intentionally poisoning DNS, and terminating DNS early because a company doesn't feel like honoring commitments of a hosting service they bought out, is heinous. I expect I will migrate my dozen domains away from dyn.com, unless I hear about the firing of the dipsh*ts who thought this was a good idea. There are plenty of unemployed honest people to take their place. Meanwhile, dyn.com is in the midst of poisoning everydns.net. We should block that URL with our own dns servers. That may affect other sites we use, besides pdxlinux.org . So, the question: What is the easiest robust way to block a domain by url with dns? Is there a way to do so on a linux firewall machine, so I do not have to do it for every machine behind it? Keith -- Keith Lofstrom [email protected] Voice (503)-520-1993 KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon" Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
