MX Records Problem?

You can do nslookup and telnet and verify that the MX is resolve to the correct host records. I'm with you, the person tryong to sell the MX. If everthing is working just ignore it.

You also verify your MX records at www.centralops.net and http://www.mxtoolbox.com/

I can perform a nslookup and returns the name servers, but how do i look up the host records?

Who said that and in what context?  Sounds like marketing.

Put your domain name into http://mxtoolbox.com which provides several different types of tests.  The default test will resolve your MX records, then you can click on further testing links from there such as blacklists and open relay checks.

please see results attached. any helpful information and direction on how to fix this would be greatly appreciated. is there a change i need to make on exchange?

i tried pinging the meganameservers.com NS servers but they're not responding.

there's no attachment

here
records-info.pdf

sorry.

FYI your MX record is fine, you're talking about fixing the "Missing nameservers reported by parent" errors, correct?

May happen if there is a mismatch or old IP between the DNS at the registrar and the ones in your DNS.

run dcdiag /test:dns on the server and post the results.

on the DC? i can't run that command from the EXCH server.

yes on the DC, what server OS are you running for your DC

do you have access to the DNS portal where your domain is registered you should check DNS entries here as well.

here are the results.


C:\Users\Administrator>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = ServerExchDC
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\ServerExchDC
      Starting test: Connectivity
         ......................... ServerExchDC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\ServerExchDC

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... ServerExchDC passed test DNS

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : ServerExch

   Running enterprise tests on : ServerExch.in
      Starting test: DNS
         ......................... ServerExch.in passed test DNS

C:\Users\Administrator>

dns info attached.
dns-mgr.pdf

run this test:  dcdiag /test:dns /f:dnslogfile.txt do a search for logfile.txt and post it, I don't believe you got all the dcdiag test results posted.

identical results in txt file (not attached)

you ran this on your exchange server, correct? What about your DC, don't you have DNS installed on that?

i ran this on the DC. this command will not run on the EXCH

Performing initial setup:

   Trying to find home server...

   ***Error: serverExc is not a Directory Server.  Must specify

   /s:<Directory Server> or  /n:<Naming Context> or nothing to use the local

   machine.
   ERROR: Could not find home server.

I didn't think so but usually there's allot more info, sorry had to ask. Give me a second to look something up.

wouldn't hurt to do a ipconfig /flushdns on the server and run the test again.

Do the ip addresses in the portal look correct to you?

yes. I don't know where it's getting ns1.meganameservers.com from though.

the name servers at ns1.covad.net and nds2.covad.net for the website. the website is hosted at a third party via A record. just FYI.

did you ever have pop mail, possibly before your exchange mail? Or maybe you popped mail into exchange? Does anything like this sound familiar?

no

The DCDIAG results are normal.  If you included the /v switch there would be a lot more info, but all the tests passed, so I don't think there's much point to it.  The results you're seeing from the test at intodns.com are not related to your internal DNS.

It appears from the report that your nameservers have nameservers and they don't know about each other.  Frankly I don't know what that means, but it would be something that your hosting company has to work out, there's nothing you can do about it.

It looks like the NS records in your zone file at covad are incorrect, do you control those records?.  If you could provide the domain name in question I can do thorough testing and explain what needs to be done.

how do i email it to you in private?

yes, i have access to the DNS zone.  I can change the covad servers.  the domain is registered at godaddy, but the website has a hosting service at megapath (covad), but the website is pointing to another provider for hosting via A name record.

Checking your domain now...

yes, that is the internal name. email is being delivered fine so that's probably not the issue right?

i put all call to covad to edit the zone file. I only see ns1/ns2.covad.net when I login, so I may not have access to edit meganameservers.com NS servers.

Some mail servers will block you when your SMTP Banner isn't a valid FQDN and/or doesn't match with the FQDN that the PTR record for the IP you're sending from resolves to.  For example, if the IP you're sending from is 100.200.300.400, and the PTR record for that IP resolves to mail-out.example.com, then your SMTP Banner should be mail-out.example.com.  And the A record for mail-out.example.com should resolve to 100.200.300.400.  If you're sending and receiving from different addresses, this doesn't have to match up with your MX record (your MX record could be for mail-in.example.com).

we need to discuss how they are currently being routed through quite a few different servers

I don't think that the records state is being questioned...they're talking about quite a few different servers.
In outlook, locate an email that was sent from outside your domain.
Right-click the message and select "Message Options"
Check the number of servers that your message was sent to before it was delivered to the mailbox.

How simplified do they want it without affecting your ability to protect you environment?
If you have 3x servers between you and the senders SMTP server then I'd be happy.

Server1: @ISP doing spam and virus checks and mail distribution, e.g. holding large mails for after hours
Server2: In your DMZ offering your mailbox servers protection from spam/flooding. That way you can block incoming/outgoing mail in the event of spam attack/virus while not affecting your ability to route email internally. Will be used as a smart host for your internal SMTP(Server3)
Server3: your Exchange server which handles internal routing/mail bridghead.

Anything simplier reduces your ability to be agile when things go wrong.