Marcin Floryan wrote:
On 17/01/2008, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Ken Schneider wrote:
No, this is just another of my anal retentive moments where I can't understand why my machine wants to ssh out to the world as mail.3111skyline.com. It's another of my inquisitively stupid "Why?" questions. I mean, what logic on the box looks to bind dns and says, "I want to be known as mail today? Hell, why not nemesis.3111skyline.com, it real name? (Ur, Umm, the name of the box is probably at fault) I should have called the son-of-a-bitch accommodating.3111skyline.com and I wouldn't have to put up with this stuff.
I know it doesn't matter, but why?
It is simply a problem of incorrectly configured reverse DNS for the domain. A lookup for 66.76.63.120 yields mail.3111skyline.com. If mail and nemesis are on machine as it seems to be I would also consider using CNAME.
Regards,
Ahah! lightbulb on, it's my upstream dns making the call, but same problem there. My upstream dns is: 3111skyline.com A 66.76.63.120 ftp.3111skyline.com CNAME 3111skyline.com nemesis.3111skyline.com CNAME 3111skyline.com www.3111skyline.com CNAME 3111skyline.com mail.3111skyline.com MX 3111skyline.com - priority: 10 Is it a coin toss for them as well? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org