Not quite. Unless this problem was just corrected, I cannot duplicate the MX
failure David reports. Here are my results from nslookup, run from my ISP's
server:
bash-2.01$ nslookup
Default Server: localhost
Address: 127.0.0.1
> set type=MX
> metta.lk
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
metta.lk preference = 10, mail exchanger = 204.143.107.46
Authoritative answers can be found from:
metta.lk nameserver = server1.tradenetsl.lk
metta.lk nameserver = edb.tradenesl.lk
server1.tradenetsl.lk internet address = 204.143.107.34
Since I have no difficulty sending mail directly to Jacob at metta.lk, it is
unsurprising that I can find the machine. It does suggest that the problem
is not general, though, but either specific to yahoo or intermittant. Note
in my nslookup report that two nameservers are listed by name but only one
has an associated IP address - this suggests a problem at the ISP that is
serving metta.lk (and providing its DNS), not at metta.lk itself. Possibly
yahoo is pickier about the absence of a nameserver than relays in general are?
At 08:51 PM 5/28/99 -0700, David Rysdam wrote:
>It means that the domain "metta.lk" doesn't have an MX (mail exchanger)
>record in the DNS system. I confirmed this using nslookup like so:
>
>%nslookup <return>
>>set type=MX
>>metta.lk
>***cannot find host/domain
>
>This means that, if there is a machine accepting mail for metta.lk,
>there isn't a way to reach it by name. This is not a yahoo problem, but
>a problem with metta.lk.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
