Re: Installfest this Saturday - PLUG website dead?
On Mon, 2010-03-01 at 14:32 -0700, Stephen wrote: This is actually something i have been planning for a few weeks now... More incentive to set this up, but it will likely go on its on VM on my server than locally. Im not sure if i want to use DHCP on my server or DHCP on myGateway yet. I have yet to see any appliance DHCP server approach the feature set you get on a full ISC DHCP server including... dynamic dns, retention of lease addresses (so they don't keep moving around), Windows specific features, etc. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- 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
Re: Installfest this Saturday - PLUG website dead?
It seems to me that the gateway is a more logical place to put dhcp, thinking of your gateway as a network server (which provides network services). To be honest though, I can't think of a reason why it would really matter one way or another. Stephen wrote: This is actually something i have been planning for a few weeks now... More incentive to set this up, but it will likely go on its on VM on my server than locally. Im not sure if i want to use DHCP on my server or DHCP on myGateway yet. On Sun, Feb 28, 2010 at 10:34 AM, Eric Shubert e...@shubes.net wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
uptime etc... and the extra features is why im thinking about it. however my gateway does dyndns, but im still wnating to replace it with a real firewall and some of those features. but i dont have a graceful replacement of the wireless part of it yet. so im kind of stuck with it. (and i dont mind replacing it with tomato/DDwrt but i want a backup plan first in case i brick it) On Mon, Mar 1, 2010 at 2:42 PM, Eric Shubert e...@shubes.net wrote: It seems to me that the gateway is a more logical place to put dhcp, thinking of your gateway as a network server (which provides network services). To be honest though, I can't think of a reason why it would really matter one way or another. Stephen wrote: This is actually something i have been planning for a few weeks now... More incentive to set this up, but it will likely go on its on VM on my server than locally. Im not sure if i want to use DHCP on my server or DHCP on myGateway yet. On Sun, Feb 28, 2010 at 10:34 AM, Eric Shubert e...@shubes.net wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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 -- A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button. Stephen --- 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
Re: Installfest this Saturday - PLUG website dead?
IPCop has worked well for me for a number of years. I started with an old 333MH celeron pc, added a couple nics, and was good to go. You wouldn't need that much power though. A plain ol' Pentium (win95 box) would do nicely. I run IPCop as a VM these days. I have my wireless router (wrt54G stock) attached to the orange (dmz) network, so wireless is isolated from my lan. Stephen wrote: uptime etc... and the extra features is why im thinking about it. however my gateway does dyndns, but im still wnating to replace it with a real firewall and some of those features. but i dont have a graceful replacement of the wireless part of it yet. so im kind of stuck with it. (and i dont mind replacing it with tomato/DDwrt but i want a backup plan first in case i brick it) On Mon, Mar 1, 2010 at 2:42 PM, Eric Shubert e...@shubes.net wrote: It seems to me that the gateway is a more logical place to put dhcp, thinking of your gateway as a network server (which provides network services). To be honest though, I can't think of a reason why it would really matter one way or another. Stephen wrote: This is actually something i have been planning for a few weeks now... More incentive to set this up, but it will likely go on its on VM on my server than locally. Im not sure if i want to use DHCP on my server or DHCP on myGateway yet. On Sun, Feb 28, 2010 at 10:34 AM, Eric Shubert e...@shubes.net wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
VMware Server, CentOS 5. Stephen wrote: Running as a vm, what platform do you run it on? (virtualbox, xen, vmware) On Mon, Mar 1, 2010 at 3:42 PM, Eric Shubert e...@shubes.net wrote: IPCop has worked well for me for a number of years. I started with an old 333MH celeron pc, added a couple nics, and was good to go. You wouldn't need that much power though. A plain ol' Pentium (win95 box) would do nicely. I run IPCop as a VM these days. I have my wireless router (wrt54G stock) attached to the orange (dmz) network, so wireless is isolated from my lan. Stephen wrote: uptime etc... and the extra features is why im thinking about it. however my gateway does dyndns, but im still wnating to replace it with a real firewall and some of those features. but i dont have a graceful replacement of the wireless part of it yet. so im kind of stuck with it. (and i dont mind replacing it with tomato/DDwrt but i want a backup plan first in case i brick it) On Mon, Mar 1, 2010 at 2:42 PM, Eric Shubert e...@shubes.net wrote: It seems to me that the gateway is a more logical place to put dhcp, thinking of your gateway as a network server (which provides network services). To be honest though, I can't think of a reason why it would really matter one way or another. Stephen wrote: This is actually something i have been planning for a few weeks now... More incentive to set this up, but it will likely go on its on VM on my server than locally. Im not sure if i want to use DHCP on my server or DHCP on myGateway yet. On Sun, Feb 28, 2010 at 10:34 AM, Eric Shubert e...@shubes.net wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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 -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluff br...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff --- 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 --- 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
Re: Installfest this Saturday - PLUG website dead?
I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff --- 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 --- 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 --- 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
Re: Installfest this Saturday - PLUG website dead?
Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) Brian Cluff wrote: I've always found that cox's DNS server have been less that desirable. I was actually surprised to find that I was using their dns at all. I've usually setup my own, to get around their DNS problems. Now with cox hijacking all the typos, I would recommend more than ever that people setup their own DNS servers. Brian Cluff On 02/28/2010 07:53 AM, Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluffbr...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion listplug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
On Sun, 2010-02-28 at 10:34 -0700, Eric Shubert wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) in the configuration of your network adaptor, you can turn off DHCP client changes to /etc/resolv.conf PEERDNS = no various ways to accomplish this depending upon whether you are using NetworkManager or not, which distro, etc. I thought ipcop provided dns forwarding to the DNS servers set up within ipcop and didn't actually provide any DNS resolution by itself so if you use DHCP on ipcop on a Cox connection, you are back on Cox's name servers. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- 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
Re: Installfest this Saturday - PLUG website dead?
Craig White wrote: On Sun, 2010-02-28 at 10:34 -0700, Eric Shubert wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) in the configuration of your network adaptor, you can turn off DHCP client changes to /etc/resolv.conf PEERDNS = no various ways to accomplish this depending upon whether you are using NetworkManager or not, which distro, etc. Sweet. I thought ipcop provided dns forwarding to the DNS servers set up within ipcop and didn't actually provide any DNS resolution by itself so if you use DHCP on ipcop on a Cox connection, you are back on Cox's name servers. Craig That occurred to me after I posted the message. You're right. IPCop alone wouldn't typically fix the problem. I guess I'm not seeing the problem because I'm on DSL. ;) For those on cox, might I suggest using opendns resolvers? 208.67.222.220 208.67.222.222 You'll need to do the PEERDNS = no thing to keep your settings from getting wiped out. Thanks Craig. :) -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
Good question. Did the sequence field perhaps not get updated on the authoritative DNS record? Steven A. DuChene wrote: Yes, I am using cox but I guess the bigger question is WHY is cox reporting an incorrect IP for the plug web server? -Original Message- From: Brian Cluff br...@snaptek.com Sent: Feb 28, 2010 1:56 AM To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff --- -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
Pretty much all DNS servers forward requests upstream. The critical configuration is what is upstream. If you want true results, the safest is to set the root nameserver anycasts as the upstream, but that's not nice, as it adds unwarranted load to the root servers, which are a limited global resource. You can connect any system (DNS in IpCop, NAT router, local DNS server, or just the resolv.conf) to a variety of DNS services. The tricky part is finding a reliable and trustworthy resolver besides the root nodes. Most people connect to their ISP because DHCP sets it up. If you're willing to type it in, though, there are several anycast DNS services available. Google, for instance, runs a lighting fast public DNS at 8.8.8.8 and 8.8.4.4 anycast that returns absolutely compliant results (including NXDOMAIN for failed lookups, instead of false results). There are many other open resolvers. Most do the same redirect-failure-to-ads trick that Cox is doing now, however. Craig White wrote: On Sun, 2010-02-28 at 10:34 -0700, Eric Shubert wrote: Running your own caching resolver is pretty trivial on RHEL/Fedora. Just need to install the caching-nameserver package (which pulls in deps when you use yum to install it). You then need to have: nameserver 127.0.0.1 first in your /etc/resolv.conf file so it gets used. If your computer is directly attached to the cox modem, that'll be a pain as dhcp resets your resolv.conf file. If you're using cox, you really should have a router with nat between your computer and the cox modem though, so your computer isn't sitting on a public address. I don't know off hand how to set up a local resolver on Ubuntu. I don't really need one myself because my IPCop is my resolver. ;) in the configuration of your network adaptor, you can turn off DHCP client changes to /etc/resolv.conf PEERDNS = no various ways to accomplish this depending upon whether you are using NetworkManager or not, which distro, etc. I thought ipcop provided dns forwarding to the DNS servers set up within ipcop and didn't actually provide any DNS resolution by itself so if you use DHCP on ipcop on a Cox connection, you are back on Cox's name servers. Craig signature.asc Description: OpenPGP digital signature --- 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
Re: Installfest this Saturday - PLUG website dead?
Eric Shubert wrote: Craig White wrote: On Sun, 2010-02-28 at 10:34 -0700, Eric Shubert wrote: For those on cox, might I suggest using opendns resolvers? 208.67.222.220 208.67.222.222 You'll need to do the PEERDNS = no thing to keep your settings from getting wiped out. Thanks Craig. :) OpenDNS is also redirecting failures to their ad servers now, which makes them the same as COX. signature.asc Description: OpenPGP digital signature --- 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
Re: Installfest this Saturday - PLUG website dead?
Joseph Sinclair wrote: Pretty much all DNS servers forward requests upstream. The critical configuration is what is upstream. If you want true results, the safest is to set the root nameserver anycasts as the upstream, but that's not nice, as it adds unwarranted load to the root servers, which are a limited global resource. You can connect any system (DNS in IpCop, NAT router, local DNS server, or just the resolv.conf) to a variety of DNS services. The tricky part is finding a reliable and trustworthy resolver besides the root nodes. Most people connect to their ISP because DHCP sets it up. If you're willing to type it in, though, there are several anycast DNS services available. Google, for instance, runs a lighting fast public DNS at 8.8.8.8 and 8.8.4.4 anycast that returns absolutely compliant results (including NXDOMAIN for failed lookups, instead of false results). There are many other open resolvers. Most do the same redirect-failure-to-ads trick that Cox is doing now, however. Thanks for the explanation, Joseph. Could you elaborate about the redirect-failure-to-ads trick? I don't know what you mean by that. Also, do you happen to know if Qwest is also doing this? Thanks again. -- -Eric 'shubes' --- 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
Re: Installfest this Saturday - PLUG website dead?
Eric Shubert wrote: Could you elaborate about the redirect-failure-to-ads trick? I don't know what you mean by that. Also, do you happen to know if Qwest is also doing this? Thanks again. Most ISP and commercial DNS providers, when a domain name isn't found, do not return the mandated a NXDOMAIN response. Instead they return the IP address of a server that just dumps a page full of ads based on the (presumably mistyped) domain name. The immediate problem is that a completely innocent typo can then result in ads for almost anything (which can be *really* bad if a kid is doing the typing). It's a dirty trick to try to turn DNS into a profit center, and I find it completely despicable. DNS has to trustworthy or the whole trust model of the net fails, and any service that's willing to change NXDOMAIN responses for profit could just as easily start redirecting other traffic for even more profit (imagine if www.gnu.org got redirected to a MS anti-FOSS site when accessed from a Windows machine). I don't know if QWest is doing that, but I would be mildly surprised if they aren't. signature.asc Description: OpenPGP digital signature --- 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
Re: Installfest this Saturday - PLUG website dead?
On 02/28/2010 02:27 PM, Joseph Sinclair wrote: Most ISP and commercial DNS providers, when a domain name isn't found, do not return the mandated a NXDOMAIN response. Instead they return the IP address of a server that just dumps a page full of ads based on the (presumably mistyped) domain name. The immediate problem is that a completely innocent typo can then result in ads for almost anything (which can be *really* bad if a kid is doing the typing). It's a dirty trick to try to turn DNS into a profit center, and I find it completely despicable. There is also the completely annoying side effect that your simple typo, that is probably only off by one letter, that could previously be easily corrected, now has to be completely re-typed from scratch. For that reason alone, I would like to strangle the guy at cox who's bright idea it was to hijack typos. It now means that when I'm trying to get someone to type in an address over the phone and they miss type it, we get to start completely over again... Yeay!. It was already super fun getting them to not automatically add WWW to the beginning of the address. Brian Cluff --- 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
Re: Installfest this Saturday - PLUG website dead?
Your browser should be giving you an address not found message. If bing is factoring into it, then your dns is being hijacked, or you have some sort of plugin that is redirecting your results. Attached is what I get when I try putting in something with a bad address. Brian Cluff On 02/28/2010 03:24 PM, Steve Phariss wrote: Who does cox redirect to? I get the bing search page, and if it is not found (i.e. truely a bad search) then BING gives me a not found page On Sun, Feb 28, 2010 at 2:27 PM, Joseph Sinclair plug-discuss...@stcaz.net mailto:plug-discuss...@stcaz.net wrote: Eric Shubert wrote: Could you elaborate about the redirect-failure-to-ads trick? I don't know what you mean by that. Also, do you happen to know if Qwest is also doing this? Thanks again. Most ISP and commercial DNS providers, when a domain name isn't found, do not return the mandated a NXDOMAIN response. Instead they return the IP address of a server that just dumps a page full of ads based on the (presumably mistyped) domain name. The immediate problem is that a completely innocent typo can then result in ads for almost anything (which can be *really* bad if a kid is doing the typing). It's a dirty trick to try to turn DNS into a profit center, and I find it completely despicable. DNS has to trustworthy or the whole trust model of the net fails, and any service that's willing to change NXDOMAIN responses for profit could just as easily start redirecting other traffic for even more profit (imagine if www.gnu.org http://www.gnu.org got redirected to a MS anti-FOSS site when accessed from a Windows machine). I don't know if QWest is doing that, but I would be mildly surprised if they aren't. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us mailto: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 --- 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 attachment: coxcrap.png--- 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
Re: Installfest this Saturday - PLUG website dead?
Yes, but you will notice they call that an Enhanced Error Results Page so that must be OK! :-) -Original Message- From: Brian Cluff br...@snaptek.com Sent: Feb 28, 2010 8:13 PM To: Main PLUG discussion list plug-discuss@lists.plug.phoenix.az.us Subject: Re: Installfest this Saturday - PLUG website dead? Your browser should be giving you an address not found message. If bing is factoring into it, then your dns is being hijacked, or you have some sort of plugin that is redirecting your results. Attached is what I get when I try putting in something with a bad address. Brian Cluff On 02/28/2010 03:24 PM, Steve Phariss wrote: Who does cox redirect to? I get the bing search page, and if it is not found (i.e. truely a bad search) then BING gives me a not found page On Sun, Feb 28, 2010 at 2:27 PM, Joseph Sinclair plug-discuss...@stcaz.net mailto:plug-discuss...@stcaz.net wrote: Eric Shubert wrote: Could you elaborate about the redirect-failure-to-ads trick? I don't know what you mean by that. Also, do you happen to know if Qwest is also doing this? Thanks again. Most ISP and commercial DNS providers, when a domain name isn't found, do not return the mandated a NXDOMAIN response. Instead they return the IP address of a server that just dumps a page full of ads based on the (presumably mistyped) domain name. The immediate problem is that a completely innocent typo can then result in ads for almost anything (which can be *really* bad if a kid is doing the typing). It's a dirty trick to try to turn DNS into a profit center, and I find it completely despicable. DNS has to trustworthy or the whole trust model of the net fails, and any service that's willing to change NXDOMAIN responses for profit could just as easily start redirecting other traffic for even more profit (imagine if www.gnu.org http://www.gnu.org got redirected to a MS anti-FOSS site when accessed from a Windows machine). I don't know if QWest is doing that, but I would be mildly surprised if they aren't. --- 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
Re: Installfest this Saturday - PLUG website dead?
On 02/28/2010 09:26 PM, Steven A. DuChene wrote: Yes, but you will notice they call that an Enhanced Error Results Page so that must be OK! :-) A... hadn't noticed that wording... everything is OK now... everyone, false alarm! False alarm everyone... This is an enhanced error page. I totally missed that before, which is probably forgivable since I was too busy feeling skull #@(%) by cox to notice that it was actually a good thing. Glad you pointed that out. I feel so much better now. :) Brian Cluff --- 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
Re: Installfest this Saturday - PLUG website dead?
I have been trying to get to the web site this morning to find more information about the install fest but the PLUG website seems to be DOA. -Original Message- From: Dazed_75 Sent: Feb 25, 2010 11:49 PM To: Main PLUG discussion list Subject: Installfest this Saturday We will be in room 204 http://plug.phoenix.az.us/ for details -- Dazed_75 a.k.a. Larry The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive. - Thomas Jefferson --- 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
Re: Installfest this Saturday - PLUG website dead?
Are you using IE6? Seems like a lot of web sites are seeming DOA to IE6 lately. I've gone to the plug website several times per day the last three days and from different computers with no problems including just now using the link in your email from the part which quoted my previous reply. On Sat, Feb 27, 2010 at 10:03 AM, Steven A. DuChene linux-clust...@mindspring.com wrote: I have been trying to get to the web site this morning to find more information about the install fest but the PLUG website seems to be DOA. -Original Message- From: Dazed_75 Sent: Feb 25, 2010 11:49 PM To: Main PLUG discussion list Subject: Installfest this Saturday We will be in room 204 http://plug.phoenix.az.us/ for details -- Dazed_75 a.k.a. Larry The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive. - Thomas Jefferson --- 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 -- Dazed_75 a.k.a. Larry The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive. - Thomas Jefferson --- 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
Re: Installfest this Saturday - PLUG website dead?
It looks like the cox name server at 68.105.29.12 is reporting back the wrong address for the plug server. If you simply remove that nameserver from your resolv.conf, you should be able to get to the server again. Brian Cluff --- 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
