| Local Domain Name doesn't have to match the Domain Name.
In your example, the host that you ran UCX SHOW NAME
from happened to be in the HARRIS_LAB.LNK.COM domain.
However, your resolver points to VAX2 in LNK.HARRIS.COM domain,
AND default domain name used for non FQDM (fully qualified
domain name) is LNK.HARRIS.COM. That means that whenever a
resolver sees a name that does not end in "." it tries to
make a FQDN out of it by adding ".LNK.HARRIS.COM." or
some portion of that domain name to it.
Now, the nslookup part:
1. Normally, when you say NSLOOKUP NAME1 NAME2 that means
that you want to lookup the NAME1 using the nameserver NAME2.
What happens then is the resolver tries to resolve NAME2 into
ip address using the nameserver that it's currently pointing
to. Well, I guess there is no such host LNK.HARRIS.COM, so
it can't resolve that. So instead, nslookup uses the name
server that the resolver is configured to use, which is
VAX2.LNK.HARRIS.COM.
2. In your case NAME1 is MX, so the resolver tries to make
a FQDN out of it and ask the name server, VAX2.LNK.HARRIS.COM.,
for A record for that name. Now the nameserver is confused,
because it doesn't know anything about MX.LNK.HARRIS.COM,
MX.HARRIS.COM, etc. It replies with rcode = NXDOMAIN, which is
non existing domain name, as expected.
3. The confusion around origin = VAX2.HARRIS_LAB.LNK.COM is
the namespace of the zone or subdomain that the VAX2 has
authority over. If you look at how the bind server is configured
on that VAX2 host, you'll find that the SOA record will look
something like:
LNK.HARRIS.COM. IN SOA VAX2.HARRIS_LAB.LNK.COM. POSTMASTER.VAX2.HARRIS_LAB.LNK.COM. (
2 3600 300 172800 43200 )
where the postmaster is the mailbox of the person responsible for
the zone LNK.HARRIS.COM.
Finally, I don't have a clear understanding of what it is you are
tring to do, but if you want to be able to recieve mail from the
internet on a host FOO.LNK.HARRIS.COM you need to have an MX
record in the zone database LNK.HARRIS.COM. something like that:
FOO.LNK.HARRIS.COM IN A your_ip_address
IN MX 10 your_ip_address
IN MX 100 your_firewall_mailgateway1
IN MX 200 your_firewall_mailgateway2
and your mailgateway has to know how to forward mail to you.
To be able to send mail out, you have to define an alternate
smtp gateway to point to the mailgateway that knows how to send
mail out.
I hope it helps. I know it's confusing, so if you have more
trouble let me know.
Thanks,
Ben
|