Re: Telnet/Winblows. Benefits of DNS etc.

[Matthew John Palmer <nospam [at] uow.edu.au>]

On Sun, 5 Mar 2000, Martin P Holland wrote:

> Not really. I similarly have a "forward only"
> setup and reconfigure named.conf at connect time to set the forwarders to
> whatever nameservers usepeerdns advises. This seems to be the best thing to do
> on an intermittent link with the current version of bind. 

Yeah, it's easier to kill named than most everything else on the system.

> If you want to go "forward first" then I guess you should just add a little
> script to ip-up that will fetch the latest root hints on a monthly basis.
> (Maybe ip-down would be better.) Of course if you do this you should still
> restart named at ip-up and down so that you have a blank root hints file
> offline to avoid those irritating network timeouts. 

Most assuredly.  This doesn't really come into the class of a proper fix,
unfortunately - I'd only class it as a workaround.  Perhaps the time has
come to do a little work to BIND to produce a temp-link friendly version.

> named.conf to make all (tcp) traffic come into port 35. But I guess if port 35
> is open you should chroot named and I couldn't be bothered to do that.

Isn't it 53?  I wouldn't run maned any other way on a public system.

> Actually, I forgot to say the biggest advantage of using named in my original
> post. You can log lookups and this is only way you can be really _sure_ that
> you stopped sendmail doing lookups ;-) 

The other way is tcpdump.


-- 
-----------------------------------------------------------------------
#include <disclaimer.h>
Matthew Palmer
mjp16@uow.edu.au

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.