On 09/14/2013 04:00 PM, Tom Rosmond wrote:
T.

Thanks for helping.  I need it.

I am not an expert on DNS issues, so my system is pretty much the
default as set up by the SL install scripts (SL 6.4).  I have an DSL
modem with a fixed IP address that is connected to a separate router,
and my system is connected to the router via DHCP.  See below for my
response to your questions or suggestions.

On Sat, 2013-09-14 at 14:53 -0700, Todd And Margo Chester wrote:
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?

Not sure. Here is the SL "dhclient-eth0.leases" file:

lease {
   interface "eth0";
   fixed-address 192.168.1.100;
   option subnet-mask 255.255.255.0;
   option routers 192.168.1.1;
   option dhcp-lease-time 86400;
   option dhcp-message-type 5;
   option domain-name-servers 192.168.0.1,216.177.225.9;
   option dhcp-server-identifier 192.168.1.1;
   option domain-name "domain_not_set.invalid";
   renew 0 2013/09/15 04:02:33;
   rebind 0 2013/09/15 13:42:29;
   expire 0 2013/09/15 16:42:29;
}

and 'resolv.conf'

; generated by /sbin/dhclient-script
search domain_not_set.invalid
nameserver 192.168.0.1
nameserver 216.177.225.9


Which Ethernet port are you using to connect to the Internet?
I use eth1.  You probably use eth0.

Yes, 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

Here is 'ifcfg-eth0' (Considerable difference from yours!)

DEVICE="eth0"
BOOTPROTO="dhcp"
HWADDR="48:5B:39:B9:FB:74"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="722705b6-87fd-4b51-9fd4-2e59711689bf"
~

Actually, not that different.

Those cheep-assed routers do not use IPv6.  Neither
does XP, so that may be some of your problem.

1) I would rename your /etc/resolv.conf to /etc/resolve.conf.000
It will auto recreate.

2) Go into ifcfg-eth0, and make the following modifications:

DEVICE="eth0"
BOOTPROTO="dhcp"
HWADDR="48:5B:39:B9:FB:74"
IPV6INIT="no"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="722705b6-87fd-4b51-9fd4-2e59711689bf"
PEERDNS=no
DNS1=8.8.8.8
DNS2=8.8.4.4


3) Then do an
      ifdown eth0; ifup eth0
as root

The above are Google's DNS, which are rather fast.
Try your router on DNS1 later to see the speed
difference.

~

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,


I am not running a 'named' server.  What are the implications of that?

None.  Just a bit slower.  Also, configuring a caching name server
is fun.  But, no real big difference for a single workstation.

Security warning: the bad guys know how to shoot through a NAT router
to access ports inside your local network.  But, they are a lazy
sort, or they'd work for a living, and only bother with the common
ports that come with on routers by default.  These are
           192.168.0.0/24
           192.168.1.0/24
The "24" means the number of ones in your netmask (24 = 255.255.255.0)

So, it would be a capital idea to change your network to a higher
range, such as 192.168.200.0/24.  The bad guys are after "Low Hanging
Fruit".

Let us know.

-T

Reply via email to