yes, i have a reverse lookup and a forward lookup
what should i put in these fields:
host or domain
mail server
priority: 10 i think.
Main Topics
Browse All TopicsHello,
I have two NT servers:
exchange server v5.5 on nt4 192.1.1.12
nt 4 pdc on nt 2000 192.1.1.13
My pdc does DNS and I need to be able to have internal clients resolve mail.company.com internally. On the outside of the company this mail.company.com is a valid mx record and works properly. However, when I have internal clients point at 192.1.1.13 for primary dns it has problems doing resolution for mail.company.com
Can you walk me through how to add a mx record in nt 2000 dns so that I can have mail.company.com resolve to 192.1.1.13?
thanks
tony
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
when i do a nslookup i cannot resolve mail.company.com
i have my dns pointing at the pdc (which is the dns server as well)
i cannot ping that name either but i have created the mx record and the alias...
i tried reloading the zone and that didnt work...
i created the a and mx record in the forward lookup zone only...
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-1999.
C:\>nslookup
Default Server: llfilepdc.company.com
Address: 192.1.1.13
> ls -d company.com
[llfilepdc.company.com]
company.com. SOA llfilepdc.company.com admin.londonlit
ho.com. (218 900 600 86400 3600)
company.com. A 192.1.1.13
company.com. A 192.1.1.14
company.com. A 192.1.1.6
company.com. NS llbdc1.company.com
company.com. NS llfilepdc.company.com
company.com. NS llbackup.company.com
1f3dce9c-5fbc-40e1-b96f-da
56d46e46-b4ab-417a-99f9-4e
a51b13e2-0b5c-4c7b-922b-18
_kerberos._tcp.Default-Fir
ht=100, port=88, llbdc1.company.com
_kerberos._tcp.Default-Fir
ht=100, port=88, llfilepdc.company.com
_kerberos._tcp.Default-Fir
ht=100, port=88, llbackup.company.com
_ldap._tcp.Default-First-S
00, port=389, llbdc1.company.com
_ldap._tcp.Default-First-S
00, port=389, llfilepdc.company.com
_ldap._tcp.Default-First-S
00, port=389, llbackup.company.com
_kerberos._tcp.dc._msdcs SRV priority=0, weight=100, port=88, llbdc1.l
ondonlitho.com
_kerberos._tcp.dc._msdcs SRV priority=0, weight=100, port=88, llfilepd
c.company.com
_kerberos._tcp.dc._msdcs SRV priority=0, weight=100, port=88, llbackup
.company.com
_ldap._tcp.dc._msdcs SRV priority=0, weight=100, port=389, llbdc1.
company.com
_ldap._tcp.dc._msdcs SRV priority=0, weight=100, port=389, llfilep
dc.company.com
_ldap._tcp.dc._msdcs SRV priority=0, weight=100, port=389, llbacku
p.company.com
_ldap._tcp.cfdb5b1d-7ce9-4
0, weight=100, port=389, llbdc1.company.com
_ldap._tcp.cfdb5b1d-7ce9-4
0, weight=100, port=389, llfilepdc.company.com
_ldap._tcp.cfdb5b1d-7ce9-4
0, weight=100, port=389, llbackup.company.com
gc._msdcs A 192.1.1.13
_ldap._tcp.Default-First-S
00, port=3268, llfilepdc.company.com
_ldap._tcp.gc._msdcs SRV priority=0, weight=100, port=3268, llfile
pdc.company.com
_ldap._tcp.pdc._msdcs SRV priority=0, weight=100, port=389, llfilep
dc.company.com
_gc._tcp.Default-First-Sit
8, llfilepdc.company.com
_kerberos._tcp.Default-Fir
rt=88, llbdc1.company.com
_kerberos._tcp.Default-Fir
rt=88, llfilepdc.company.com
_kerberos._tcp.Default-Fir
rt=88, llbackup.company.com
_ldap._tcp.Default-First-S
89, llbdc1.company.com
_ldap._tcp.Default-First-S
89, llfilepdc.company.com
_ldap._tcp.Default-First-S
89, llbackup.company.com
_gc._tcp SRV priority=0, weight=100, port=3268, llfile
pdc.company.com
_kerberos._tcp SRV priority=0, weight=100, port=88, llbdc1.l
ondonlitho.com
_kerberos._tcp SRV priority=0, weight=100, port=88, llfilepd
c.company.com
_kerberos._tcp SRV priority=0, weight=100, port=88, llbackup
.company.com
_kpasswd._tcp SRV priority=0, weight=100, port=464, llbdc1.
company.com
_kpasswd._tcp SRV priority=0, weight=100, port=464, llfilep
dc.company.com
_kpasswd._tcp SRV priority=0, weight=100, port=464, llbacku
p.company.com
_ldap._tcp SRV priority=0, weight=100, port=389, llbdc1.
company.com
_ldap._tcp SRV priority=0, weight=100, port=389, llfilep
dc.company.com
_ldap._tcp SRV priority=0, weight=100, port=389, llbacku
p.company.com
_kerberos._udp SRV priority=0, weight=100, port=88, llbdc1.l
ondonlitho.com
_kerberos._udp SRV priority=0, weight=100, port=88, llfilepd
c.company.com
_kerberos._udp SRV priority=0, weight=100, port=88, llbackup
.company.com
_kpasswd._udp SRV priority=0, weight=100, port=464, llbdc1.
company.com
_kpasswd._udp SRV priority=0, weight=100, port=464, llfilep
dc.company.com
_kpasswd._udp SRV priority=0, weight=100, port=464, llbacku
p.company.com
APetrie A 192.168.160.25
bclesen A 192.1.1.225
compaq A 192.1.1.224
delltest A 192.1.1.20
DHianik A 192.1.1.59
elondonlaptop A 192.1.1.203
HResources A 192.1.1.115
JBruso A 192.168.120.26
jhernandez A 192.1.1.11
kcarroll A 192.168.120.74
KLindgren A 192.1.1.165
KMatthews A 192.1.1.64
LL700Kiosk A 192.168.170.26
llbackup A 192.1.1.6
llbdc1 A 192.1.1.14
lldnbbdc A 192.1.1.19
llexchbdc1 MX 10 192.1.1.12
llfilepdc A 192.1.1.13
llsql A 192.1.1.8
LLUPS100 A 192.1.1.85
LMcabee A 192.168.160.27
mail CNAME llexchbdc1.company.com
MEder A 192.168.120.46
PFritsch A 192.1.1.31
PMusall A 192.1.1.20
RYoung A 192.168.160.41
SALES-ALPHA A 192.168.120.213
Scanner A 192.1.1.200
server A 192.1.1.20
SMcneill A 192.168.120.68
tadduci A 192.1.1.164
company.com. SOA llfilepdc.company.com admin.londonlit
ho.com. (218 900 600 86400 3600)
>
If the DNS Server insists to add the Host entry as CNAME it must already have the actual Host entry in it's database,
llexchbdc1 A 10 192.1.1.12
although the output you posted doesn't show it.
I think there shouldn't be any problem using "mail" as a CNAME record unless the server is still SP2. SP3 fixed some problems with CNAME Aliases:
http://support.microsoft.c
http://support.microsoft.c
im a little curious as to why your internal clients are needing DNS at all for this ?
why are your clients requiring DNS at all ? Exchange clients use RPC calls and do not do a DNS lookup for the mail records for exchange.
Are you using pop3 clients on your internal network ? if so my next question would be why ?
if not what exactly are you trying to achieve with an internal mx record ? your clients should be able to resolve the mx record using normal DNS from whereever delegated DNS server is ?
or maybe i missed something in your Q ?
i have internal clients that need to be able to send mail to an internal smtp system... for example mac os 10 doesnt use exchange server rpc calls, it only has support for pop3 and smtp...
the bottom line is i need the alias mail.londonlitho.com internally to work and resolve to 192.1.1.12
outlook on the pc's works fine and those clients are all using the exchange server service... no issues there...
the reason i dont use the ip of the mail server for the smtp entry is because when those people step outside of the company they use the same email client profile and that smtp ip address is not a public one (not for our use at least) I also dont want them to have a inside and outside profile, i just want one profile.
thanks.
Hi tadduci,
I think all you need to do is ensure that you have a correct Host A record for your mail server which should look like
llexchbdc1 A 10 192.1.1.12
then the MX record
llexchbdc1 MX 10 192.1.1.12
as well as the ALIAS
mail CNAME llexchbdc1.company.com
that should ensure that mail.company.com resolves to 192.1.1.12
you cannot have a Host A record for 192.1.1.12 with the name "mail" since the machine's name is llexchbdc1. "mail" should be listed as CNAME.
If you do have those 3 entries and still have problems you might be running into a known issue with CNAMEs. I finally found the article I had been looking for regarding the SP3 Fix for a known Problem with CNAMEs
http://support.microsoft.c
tadduci:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
Business Accounts
Answer for Membership
by: geoffrynPosted on 2003-01-02 at 11:46:31ID: 7657588
Have you added a zone for company.com?