[EMAIL PROTECTED] wrote:
>> So, what do you get when you:
>> # dig compdev.xxxx.com MX
>> from the box that the toaster is running on?
>
> dig compdev.xxxx.com MX
>
> ; <<>> DiG 9.2.4 <<>> compdev.xxxx.com MX
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22046
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;compdev.xxxx.com. IN MX
>
> ;; AUTHORITY SECTION:
> xxxx.com. 600 IN SOA ns1.<dnsserver>.net.
> support.<hostingdomain>.net. 2007121302 10800 3600 86400 600
>
> ;; Query time: 20 msec
> ;; SERVER: 192.168.1.29#53(192.168.1.29)
> ;; WHEN: Sat Jan 19 11:57:20 2008
> ;; MSG SIZE rcvd: 100
>
> Note that compdev.xxxx.com is not a public server. It is only a web server
> used for development internally. It has a private IP, 192.168.1.58.
>
> Because it's not public, I have to admit that I'm not sure where dig is
> getting the above MX record since this server doesn't have one. Should I add
> the internal (and public) web server names somewhere perhaps?
>
> Mike
>
Dig isn't getting an MX record at all. Note the "QUESTION SECTION". It's
simply telling you what the request was for.
Your simplest solution is going to be to change the apache application so
that it doesn't use compdev in the domain name, i.e. just "[EMAIL PROTECTED]"
or "[EMAIL PROTECTED]". As there doesn't appear to be a logical
"compdev.xxxx.com" sub domain for which there is an email server (and email
accounts), this seems like the right solution to me.
Alternatively, you could set up an authoritative private dns server for your
private network addresses. This would be pretty complicated though, and I
would recommend against going there. ;)
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
