> On Sat, 2013-09-14 at 12:14 -0700, Todd And Margo Chester wrote:
>> On 09/13/2013 04:36 PM, Joseph Areeda wrote:
>>> My first guess is a DNS issue are they both using the same DNS
server as
>>> their first choice?
>>
>> Hi Tom,
>>
>> XP may have its DNS Caching service activated. (If so,
>> you should turn it off, as it is a security hazard.)
>>
>> Along Joe's lines, try looking up google.com's
>> I.P. address, instead of its name and see if you
>> get an improvement.
>>
>> -T
>>
>> $ host google.com
>> google.com has address 74.125.239.98
>> google.com has address 74.125.239.104
>> google.com has address 74.125.239.102
>> google.com has address 74.125.239.101
>> google.com has address 74.125.239.103
>> google.com has address 74.125.239.96
>> google.com has address 74.125.239.99
>> google.com has address 74.125.239.100
>> google.com has address 74.125.239.110
>> google.com has address 74.125.239.105
>> google.com has address 74.125.239.97
>
>
>
On 09/14/2013 01:18 PM, Tom Rosmond wrote:
T,
Yes, using an IP address rather than 'google.com' give MUCH faster SL
response. Unfortunately the problem isn't just for Google, I get slow
loading of any URL. So clearly I have a nameservice problem with SL
that isn't present with XP. Are you saying that the reason XP avoids
this is because of DNS caching that is a security problem. I am all for
security, but the cost in browser response seems very high.
T. Rosmond
Hi Tom,
Now we fix your DNS. Are you using a local caching DNS or
are you using your router or one on the Internet?
Which Ethernet port are you using to connect to the Internet?
I use eth1. You probably use eth0.
Here is my /etc/sysconfig/network-scripts/ifcfg-eth1:
# cat ifcfg-eth1
DEVICE=eth1
HWADDR=00:25:90:20:3b:2b
#NM_CONTROLLED=yes
NM_CONTROLLED=no
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
USERCTL=yes
#PEERDNS=yes
PEERDNS=no
IPV6INIT=no
DNS1=127.0.0.1
#DNS1=208.67.222.222
#DNS2=208.67.220.220
If you want to use your router's or an Internet DNS,
you will want to modify
PEERDNS=yes
DNS1=208.67.222.222
DNS2=208.67.220.220
Change the DNS address to the one you use.
192.168.0.1 (this would be your router)
216.177.225.9
The ones you see in the example are Open DNS.
You have to restart your interface to get this to take:
ifdown ethx (eth0 etc.)
ifup ethx
If you are using a caching named server, this is my forward
section of /etc/named.conf,
options {
directory "/var/named";
# the following forwarders is for Open DNS
# forwarders { 208.67.222.222; 208.67.220.220; };
# the following forwarders is for frontier.com's Nevada DNS servers
# forwarders { 216.67.192.3; 74.40.37.242; };
# forwarders { 74.40.74.40; 74.40.74.41; };
forwarders { 8.8.8.8; 208.67.222.222; };
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
Love to know how it works,
-T
