[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems with OpenSSH and BIND



On Mon, Feb 21, 2000 at 06:42:40PM +0100, Andreas Voegele wrote:
> If I connect to another local machine with ssh after named has been
> restarted my system always goes online.
[...]
> When I'm using ssh to connect to host "magellan" from host "columbus"
> the following lines are written to my log file:
> 
> 21-Feb-2000 18:09:29.274 XX+/127.0.0.1/magellan.voegele.local/AAAA/IN
> 21-Feb-2000 18:09:29.274 XX+/127.0.0.1/magellan/AAAA/IN
> 21-Feb-2000 18:09:29.275 XX+/127.0.0.1/magellan.voegele.local/A/IN
> 21-Feb-2000 18:09:29.276 XX+/127.0.0.1/130.106.168.192.in-addr.arpa/PTR/IN
> 21-Feb-2000 18:09:29.280 XX+/127.0.0.1/magellan.voegele.local/AAAA/IN
> 21-Feb-2000 18:09:29.280 XX+/127.0.0.1/magellan.voegele.local.voegele.local/AAAA/IN
> 21-Feb-2000 18:09:29.281 XX+/127.0.0.1/magellan.voegele.local/A/IN
> 
> One of these queries causes the system to dial out. I think, it's the
> one without the domain or the one with the double domain.

	It's either the magellan or 130.106.168.192.in-addr.arpa
	query, I'd say. You can reproduce these manually with
	dig magellan @127.0.0.1 (or actually dig magellan aaaa @127.0.0.1)
	dig -x 130.106.168.192.in-addr.arpa @127.0.0.1
	If you configure your BIND/diald/ISDN/whatever such that
	your internet connection is not started by these two
	digs, then it shouldn't get started on that ssh either.

	Also, if you are not using IPv6, try ssh -4 magellan.

	If you are using 2.3 kernels, try with 2.2.
-- 
tv@{{hq.yok.utu,havoc,gaeshido}.fi,{debian,wanderer}.org,stonesoft.com}
unix, linux, debian, networks, security, | Windows NT crashed.
kernel, TCP/IP, C, perl, free software,  | I am the Blue Screen of Death.
mail, www, sw devel, unix admin, hacks.  | No one hears your screams.


Reply to: