ftp.cisco.com broken ?

Jared Mauch jared at puck.Nether.net
Tue Oct 7 18:11:38 UTC 2003


	They've had this broken for weeks now.

	You'll also see (depending on nameserver)

	this in your logs:

Oct  7 14:10:36 unix named[3502]: lame server resolving 'ftp.cisco.com' (in 'ftp.cisco.com'?): 64.102.255.39#53
Oct  7 14:10:36 unix named[3502]: lame server resolving 'ftp.cisco.com' (in 'ftp.cisco.com'?): 128.107.240.86#53
Oct  7 14:10:38 unix named[3502]: lame server resolving 'ftp.cisco.com' (in 'ftp.cisco.com'?): 64.102.255.39#53
Oct  7 14:10:38 unix named[3502]: lame server resolving 'ftp.cisco.com' (in 'ftp.cisco.com'?): 128.107.240.86#53

	Depends on resolver libs, etc..

	I've reported it to them in the past and their IT
folks can't seem to get it fixed :(

	- Jared


On Tue, Oct 07, 2003 at 02:39:43PM -0300, Ezequiel Carson wrote:
> 
> hi,	
> 
> 	can you resolve ftp.cisco.com?
> 	
> [root at localhost /]# ping ftp.cisco.com
> ping: unknown host ftp.cisco.com
> [root at localhost /]#
> 
> 
> something is wrong here....
> 
> ezequiel.
> 
> 	

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.



More information about the NANOG mailing list