From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
References: <bde13d79d0a3adcb1545e5484908131f@comcast.net>
	<20060103121838.1ED253256D@dexter-peak.quanstro.net>
	<ee9e417a0601030639q6bcffd26x2143571a33dc8969@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <ee9e417a0601030639q6bcffd26x2143571a33dc8969@mail.gmail.com>
Subject: Re: [9fans] smtp dns failure: mx lookup
Message-Id: <20060104022813.847ED1E4138@dexter-peak.quanstro.net>
Date: Tue,  3 Jan 2006 20:28:13 -0600
Cc: 
Topicbox-Message-UUID: d02ba7e2-ead0-11e9-9d60-3106f5b1d025

so, the question is, why does the mx lookup fail?
are your [a-j].root-servers.net entries up-to-date?
i'm not able to replicate the failure here:

; fn dns { n=() {if (~ $#* 1) n=ip; echo $* $n | 9p rdwr dns/dns}}
; dns smtp.comcast.net mx

write: dns: resource does not exist

; dns smtp.comcast.net

	63.240.77.77

on a related note, is there a way to make the dns fileserver return all 
the answers for a given question? 

Russ Cox <rsc@swtch.com> writes

| 
| > the solution is probablly to add smtp.comcast.net in your ndb
| > database. maybe upas should lookup the a/aaaa record if there's
| > no mx record as a fallback. i'd be careful about doing that, though.
| 
| upas *does* look up the a record if the mx lookup says the name does not exist.
| it does not look up the a record if the mx lookup fails.
| 
| russ