Cowles, Steve wrote:
Here's a slow pitch:
[snip]
imagine if you will:
www.customersite.com. IN A 192.168.0.5 www.customersite.com. IN A 192.168.0.6 www.customersite.com. IN A 192.168.0.7 www.customersite.com. IN A 192.168.0.8
I'm hoping your asking us to imagine that you actually added public IP addresses for the above. :-)
Yes, please imagine, real, public addresses here. :) I'm greeking all of this to protect hosts, etc. (not that anything can't be had for the truly investigative, but I'm being cautious and paranoid.
I have since hoped to correct the problem by adding a MX record:
customersite.com. IN MX 10 mail.customermailhost.com
Would this be correct?
The above MX syntax looks correct. Hopefully you have also defined the address record (A) for mail.customermailhost.com.
Steve, et. al,
Hmmm... isn't this taken care of by "customermailhost.com". Remember, I'm not managing, maintaining or otherwise associated with the mail server. It is a seperate entity altogether (quite literally "over the hills and through the woods"). If I were to put an A record:
mail.customermailhost.com IN A 172.16.0.10
at my DNS host, am I not announcing "authoritive" responses for this host? I don't want to do that (do I?). I guess want I'm trying to say is won't:
customersite.com. IN MX 10 mail.customermailhost.com
resolve? or should I be saying:
customersite.com. IN MX 10 172.16.0.10
???
As a final followup: It seems that my MX entry as first described is doing the trick.
> customersite.com. IN MX 10 mail.customermailhost.com
*No additional* A records needed to be added.
But if any more experienced DNS admins wish to comment, please do. This young DNS "Padawan" wishes to learn more.
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
