SCIENTIFIC-LINUX-USERS Archives

September 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Shane Voss <[log in to unmask]>
Reply To:
Shane Voss <[log in to unmask]>
Date:
Tue, 17 Sep 2013 22:33:04 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
On 17/09/13 21:24, Tom Rosmond wrote:
> Last weekend I posted the thread 'slow loading browser homepage'.  I got
> useful feedback from several people that helped narrow the problem to
> the order that nameservers are listed in my 'dhclient-eth0.leases' file.
> It has the line:
>
>    option domain-name-servers 192.168.0.1,216.177.225.9;

It looks to me as if your dhcp server is misconfigured.  I presume this is the 
modem.  So the "proper" solution is to persuade that modem not to list itself 
as a DNS server.

One hack that might work around this is to use iptables to prevent yourself 
sending DNS requests to the modem:

    iptables -A OUTPUT -d 192.168.0.1 -p tcp --dport 53 -j REJECT
    iptables -A OUTPUT -d 192.168.0.1 -p udp --dport 53 -j REJECT

The REJECT should result in an immediate response saying that port is not 
available, rather than a delay waiting for it to respond.

If that works, you can make the firewall rules "permanent" thus:

    service iptables save
    chkconfig iptables on

    Shane

-- 
Shane Voss, Computing Officer, School of GeoSciences, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

ATOM RSS1 RSS2