[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[4]: [cobalt-users] DNS reverse address lookup, Raq3i
- Subject: Re[4]: [cobalt-users] DNS reverse address lookup, Raq3i
- From: COMPUTICA <cobalt@xxxxxxxxxxxxxxxxxx>
- Date: Tue Oct 29 18:57:00 2002
- Organization: The COMPUTICA Group of Companies, Inc.
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
On Tuesday, October 29, 2002, 8:47:21 PM, you wrote:
LS> On Tuesday 29 October 2002 08:14 pm, COMPUTICA wrote:
>> I am not sure if "it's needed", but I know it was in the DNS tutorial
>> I went through when first setting up DNS services on my RaQ's. I have
>> never run any domains without both MX records....
>>
>> Maybe someone else can let you know if it's needed to not....
>>
>> If not....this thread has taught me something today that will save a
>> little bit of time down the road..... :)
LS> If both "domain.com" and "www.domain.com" point to the same IP address then
LS> _not_ only is it not needed - it is _not_ recommended and really
LS> sort-of-kinda-almost- upsets admins such as myself who sit and watch a
LS> message in queue until it "timesout" with the first MX host only to see it
LS> connect to the exact same host as the second MX (and have to wait on that
LS> timeout also).... Really buggers up mail for remote people having two MX
LS> records pointing to the same place... Sort of like a voice mail that says
LS> "dial 0 for help and if that doesn't work dial 0" (why would it work the
LS> second time if not the first ??)
LS> Basic bottom line: you need an MX record per domain.
LS> If "www.domain.com" resolves to an IP - then mail can be delivered there
LS> anyway - since if there is no MX record for the domain portion of an address
LS> - EG: someone@xxxxxxxxxxxxxx - then the sending server simply trys to "call"
LS> that hostname directly.
That's some great info Larry! Thanks! :)
Ryan