On 5 Mar 2007, at 11:11, Jan Johansson wrote:
> I get a problem with " all relevant MX records point to non-existent
> hosts"
>
> And I do not understand why? Why are these hosts being ignored?
[snip]
> nrtms01.ne.nykline.com. 3600 IN A 10.31.4.37
> nrtms02.ne.nykline.com. 3600 IN A 10.31.4.38
So these are in private address space...
[snip]
> --------> dnslookup router <--------
> local_part=dan.stahl domain=ne.nykline.com
> checking domains
> cached no match for +local_domains
> cached lookup data = NULL
> ne.nykline.com in "! +local_domains"? yes (end of list)
> R: dnslookup for dan.stahl@???
> calling dnslookup router
> dnslookup router called for dan.stahl@???
> domain = ne.nykline.com
> DNS lookup of ne.nykline.com (MX) succeeded
> DNS lookup of nrtms02.ne.nykline.com (AAAA) gave NO_DATA
> returning DNS_NODATA
> DNS lookup of nrtms02.ne.nykline.com (A) succeeded
> 10.31.4.38 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
> 10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
Your dnslookup router is configured (correctly for internet use) to
ignore the private address spaces, including 10.0.0.0/8, so your
targets in private address space are discarded.
You want to do one of the following:-
- If these are hosts you want to contact from this box then
its probably worth adding an extra dns router that is limited
to your own domains and does not have an ignore_target_hosts
setting that blocks out your own systems
- Reduce ignore_target_hosts appropriately. However if you do
that on an internet box you may then spend time attempting to
deliver to boxes that you can never get to....
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
