North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: FW: DNS .US outage

  • From: Suresh Ramasubramanian
  • Date: Mon Jul 11 09:28:06 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RAoq3S/jwldA0QzlzpsfeVCRV64io3n8WPS92lRFgxCtk9sgnEuMHGsELnt5t+WF6h8/A5GDwE7jaWVwVExvwrKaonG9VsVIKzJRLew458PGna6tuaR40qR+oL8KntUaA6L9jux8b1Kng1OYDDPx4Qg7pb4nTIDkEUwuBz1VPBU=
On 11/07/05, Church, Chuck <[email protected]> wrote:
> One thing to note is that when you use dig or nslookup or whatever,
> it'll also be using some ephemeral port, so it'll work, even when the
> lookups from source port 53 wouldn't. Again, I haven't checked since
> that night to see if that's gone away, so it might be a moot point
> now.

Hold on now - dig or nslookup query the local resolver with that ephemeral port.

If this behavior you describe still exists on the resolver (query from
port 53 and not ephemeral ports) then you still wouldnt get a result

-- 
Suresh Ramasubramanian ([email protected])