NSLOOKUP not returning MX Records

Hello Experts,

I have AD domain called test.com and have an exchange organisation. I also have a edge transport server. So i created an MX Record in DNS for my edge and everything is working fine, i mean email flow. I can send/recieve email. I have a phone system which will send emails when a user gets Voicemail and its not working.

So i checked nslookup to see my MX Records with set type=MX and i got the below reponse.

test.com
        primary name server = dc1.test.com
        responsible mail addr = admin.test.com
        serial  = 86835
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 900 (15 mins)

I am not getting my MX Records. Can you help me find why ? if i do hotmail.com or google.com or any other its returning MX records but for test.com i get the above response.

Please help!

R/Raj.
PHESupportAsked:
Who is Participating?
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:
> mailserver.test.com MX Preference = 10, mail exchanger = mailserver.test.com

This is an MX record for the domain mailserver.test.com, it's active when you send to someone@mailserver.test.com.

If you had the zone "test.com" and you use MS DNS you would leave the name field (domain / child / whatever) blank so you end up with:

(same as parent folder)   MX  10   mailserver.test.com.

Chris
0
 
omarfaridCommented:
are you sure that mx records are stored in the zone file? can you list records in zone file?
0
 
PHESupportAuthor Commented:
Yes the MX records are there in the zone file and pointing to correct IP's. if i do mailserver.test.com then i get

mailserver.test.com MX Preference = 10, mail exchanger = mailserver.test.com
mailserver.test.com internet address = 192.168.1.10
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Chris DentPowerShell DeveloperCommented:
No MX record, it's giving you the SOA.

But...

That looks like a private DNS service, you'll only see a public MX if you manually replicated it into the private service.

If you want to test the public view of the MX:

nslookup -q=mx thedomain.com 8.8.8.8

Where 8.8.8.8 is Google's free public DNS service.

Chris
0
 
PHESupportAuthor Commented:
Yes it is a private DNS server running on my DC.

When i do the nslookup -q mx=test.com 8.8.8.8 i get the public MX Records correctly.

Why is my private MX Records not showing up ? my phone system queries for the MX record in the domain and uses to send email and since i am not getting any response its not working. I moved to 2010 over the weekend and the problem started from then

Do i have to do anything else apart from creating MX record in my zone file ?
0
 
Chris DentPowerShell DeveloperCommented:
> Why is my private MX Records not showing up ?

Because you did it wrong. See my last comment about what you made vs what you needed to make.

Chris
0
 
PHESupportAuthor Commented:
Thank you Chris. That was the problem. I need to leave the name field bland to make it work.
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.