Re: [sitefinder-tech-discuss] followup from 15oct secsac

[bmanning@karoshi.com]

> > > > 	Hence benign.  More "prickly" are things like wildcard "A"
> > > > 	records.   Ms. Random Disgruntled has zero idea (from the DNS
> > > > 	side of the house) what, if any, services may be hanging off
> > > > 	the IP address on the other side of that A.  For all she knows,
> > > > 	the services can and will change over time...  Was this
> > > > 	ambiguity considered as a design goal?
> 
> Other services as something to be addressed?  Yes -- that's why TCP resets
> and ICMP errors are used to reject connection attempts for other services.
> 
> -Scott-

	that then opens the question of service rollout. hindsight often
	being considered better than foresight, it would have been 
	interesing to see the impact of a wildcard "A" will 
	TCP resets and ICMP errors generated for all services... :)

	presuming that wildcard entries are an acceptable delivery
	vector for service delivery, what would be the plan for 
	coordinating w/ the zone consitutents on new service
	deployment?

	say putting up valid services on port 123?
	or, being more inovative, ports 88, 210, 546-7, 11371 and 26000

--bill

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/unsubscribe>