Re: MX Query to Windows Server 2003 DNS does not return an answer

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

In news:8709385D-9FB4-4CD7-9FBA-72A2C93F9FD0@xxxxxxxxxxxxx,
Allie <Allie@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
well i added another MX, this time leaving the hostname blank, but
pointing it to the FQDN of the mail server

the Dig query responds the same

no answer section for MX if I run it against our internal DNS

ugh...

Actually based on the RFC that defines MX records, leaving the hostname
blank is the proper way to create an MX record. Otherwise it can cause
issues with other SMTP servers trying to resolve the mail exchanger record.
This way it shows up in the DNS console as:

(same as parent) MX mail.whatever.com

Do me a favor and try to force TCP with the DIG query. I havea feeling it's
due to EDNS0 and DIG is not supporting it for some reason.

Also try nslookup. Try these methods please:

c:\> nslookup
set q=mx
domain.com

Then try with forcing TCP:

c:\>nslookup
set vc
set q=mx
domain.com



Ace


.