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.
?
-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
@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
...@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
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
: 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
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
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
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
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
...@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
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
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. :)
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,
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
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
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
- 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
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
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
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
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
22 matches
Mail list logo
