If you're experiencing issues, then set up a job to query Cox and Qwest's and whoever's DNS servers at the same time and log it. See if you're seeing a trend. It could just be your connection. On Sun, Aug 10, 2008 at 12:07 AM, Craig White wrote: > On Sat, 2008-08-09 at 23:39 -0700, Technomage Hawke wrote: > > Over the last few weeks, I have noticed an increasing number of > > customer calls about network outages. Now on the surface, this might > > not seem all that relevant, However, these issues are not just windows > > centric. > > > > I have discovered a pattern to the outage problems I have been > > troubleshooting. it seems that cox is filtering dns traffic to anyone > > outside their own ip space. any attempt to use a DNS root server or > > even the ASUdns servers results in many pages not being resolved. as > > soon as I set for the cox dns servers, all seems to work again. > > > > anyone else noticing this "filtering" on cox's part? > ---- > no - it makes no sense, you can always test your theory out at any time > you want by running commands such as dig and host and if you really > care, you could run your own caching dns server which would obviously > need to access other dns servers to be worthwhile. > > Craig > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > -- James McPhee jmcphe@gmail.com