What are the error messsage i should look at after running the nslookup command to query MX record and receive an error message?

What you want to achieve out of error messages ?I do not represent the organisation I work for, all the opinions expressed here are my own. This posting is provided "AS IS" with no warranties or guarantees and confers no rights. ... .- -. - --- ... ....

By the way, if you would like to use Nslookup to Verify MX record configuration, pls see the article below How to Use Nslookup to Verify MX record configuration http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65)I do not represent the organisation I work for, all the opinions expressed here are my own. This posting is provided "AS IS" with no warranties or guarantees and confers no rights. ... .- -. - --- ... ....

I know this information already but any way thanks for the link.

I haven't seen a MX record error message before in nslookup command, so i wonder how the error message is look like so i know how to troubleshoot the MX record error message the next time the same error message appear.by using the nslookup command.Nothing special.

I haven't seen a MX record error message before in nslookup command, so i wonder how the error message is look like so i know how to troubleshoot the MX record error message the next time the same error message appear.by using the nslookup command.Nothing special. You will receive Non-Existant domain or a timeout if you are not able to do the resolution. To have the exact error message, you can query a not existing MX record. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

I tried with an non-existence MX is this the error message i should receive? >set query=MX > sdfd.local Server: UnKnown Address: 192.168.1.110 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out

I tried with an non-existence MX is this the error message i should receive? >set query=MX > sdfd.local Server: UnKnown Address: 192.168.1.110 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out Here, it means that there was a timeout since the query was not resolved within 2 seconds. This may be because of latency of because the DNS record does not exist. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

DNS MX record doesn't exist.so this is a way to use nslookup command to troubleshoot DNS server problem?

DNS MX record doesn't exist.so this is a way to use nslookup command to troubleshoot DNS server problem? Yes, to check if your computer / server is able to solve the DNS record or not. If not then there may be several causes: The record does not existThe computer / server is not able to do the resolution because it pointing to a wrong DNS serverThe DNS traffic is blocked... So, there is many causes and the use of nslookup is important here. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer