Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Paul Vixie
whats disturbing is how many contact addresses for both whois and AS#'s bounce sure, i agree, that's disturbing. however, it's a different problem than having mail get ignored or ignorebotted and then depref'd so low that nobody even bothers to call you or let you know whether a human ever

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Alan Spicer
and Network Administration, and Telecommunications - Original Message - From: Paul Vixie [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 29, 2003 3:34 AM Subject: Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates) whats disturbing is how many contact addresses

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Michael . Dillon
but no matter how good an idea it is, my complaint is still that sending e-mail toward the whois contact for a network or AS# should elicit a clueful reply, and if it doesn't, then the key word we're looking for is cost shifting. (and that, in case y'all wondered, is why this is relevant to

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Paul Vixie
... probably most of the Abuse issues (especially via email) would continue to be ignored. Noone wants to handle that stuff. But someone(s) must handle that stuff. the underlying question is, or else what? this is an assymetric-benefit situation. when folks ignore reports from noncustomers

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Owen DeLong
--On Monday, September 29, 2003 2:44 AM + Paul Vixie [EMAIL PROTECTED] wrote: the whole end-to-end argument depends on uniform clue distribution for scale. ... Getting vendors to supply more appropriate defaults offers better scaling possibilities. Your complaint might fix one user's

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-29 Thread Alan Spicer
... probably most of the Abuse issues (especially via email) would continue to be ignored. Noone wants to handle that stuff. But someone(s) must handle that stuff. the underlying question is, or else what? * Fortunately, at least where I was, there is a knowledge of AUPs having written

ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-28 Thread Sean Donelan
On 28 Sep 2003, Paul Vixie wrote: Specifically, I want to know why Comcast makes itself so hard to reach. I'll bet I could get them to talk to me about this host if it were DDoS'ing me, or if I aggressively NMAP'd it at 25Mbits/sec for 48 hours straight. Based on the comments in many forums,

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-28 Thread Paul Vixie
How should an ISP tell the difference between good DNS packets and bad DNS packets? the bad ones are the ones people complain about. You aren't complaining about your dynamic update packets or even all dynamic updates. You are complaining about someone sending you packets you don't want.

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-28 Thread Sean Donelan
On Sun, 28 Sep 2003, Paul Vixie wrote: I've been thinking how to use ICMP to signal different types of responses; and even how smart edges on both ends of a communication could establish and enforce policies. Most of these are non-malicious communications involving misconfigured systems.

Re: ISPs blocking port 53? (was Re: Annoying dynamic DNS updates)

2003-09-28 Thread Paul Vixie
the whole end-to-end argument depends on uniform clue distribution for scale. ... Getting vendors to supply more appropriate defaults offers better scaling possibilities. Your complaint might fix one user's computer, Microsoft updating the default behaivor would fix tens of millions of