Nslookup and MX record issue

Hi,

we have a internal DNS and exchange 2010 server. When I run nslookup I get
> set type=mx
> domain.com
Server:  dc13.domain.com
Address:  10.10.10.10

domain.com
        primary name server =  dc13.domain.com
        responsible mail addr = admin.domain.com
        serial  = 253862
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

On our DNS server the MX record is setup to point to an edge server, shouldn't i get the edge server name and IP when i run nslookup for MX record internally?

Please help

Noveen
noveenmorrisAsked:
Who is Participating?
 
noveenmorrisConnect With a Mentor Author Commented:
Ok the issue has been resolved. Deleted and added new MX record and it started working. Not sure what happend, but its working now.
0
 
Tony MassaCommented:
This would say to me that the MX record does not exist in the domain you queried.

This does not mean that the HOST (A) record for the email server doesn't exist, but specifically the MX record. Can you provide a screenshot that shows the MX record?

You should see something like this via NSLOOKUP:
> domain.com
Server:  dns.server.name.domain.com
Address:  10.10.10.201

Non-authoritative answer:
domain.com  MX preference = 10, mail exchanger = mail.server.name.domain.com

Open in new window

0
 
noveenmorrisAuthor Commented:
Here is a screenshot of our DNS server.
pic.jpg
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
noveenmorrisAuthor Commented:
As you can see MX record that is pointing to our Edge server is there. But internally nslookup not returning that record.
0
 
GlobalStrataCommented:
Are you running into issues with this configuration?

Although I have not done Exchange for a while, I am confused why you expect the internal MX to be your edge server.  I would expect the internal MX to be pointing to an internal mail server.  The Edge server is supposed to be used to proxy internet traffic to your mail servers. (http://technet.microsoft.com/en-us/library/bb124701.aspx)
0
 
Tony MassaCommented:
Is the server you were remoting to your only DNS server, meaning is that the DNS server your PC is using?
0
 
noveenmorrisAuthor Commented:
Sorry guys I was busy and was not able to work on this issue.
I am planning on contacting Microsoft. I will update you all after the issue is resolved.
0
 
noveenmorrisAuthor Commented:
worked with microsoft to resolve issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.