>OK, Here is the skinny on the problem. Can you wait a few hours? I'd really like to get you straightened out, but I gotta run some errands, and gonna go see that submarine flick. (I pass on talking dinosaurs and anachronistic lemurs, no matter how cool the 3D simulation is! vbg) >We bought another ISP who happens to be running Imail V5.04 and using a >Linux DNS server. We did not buy out the whole company so their mail server >remains their own. They have two NS machines NS.CASTLEGATE.NET and >NS.FIRSTPLACE.NET, The main domain is castlegate.net. ok that's their DNS servers. >I put a new IP address on my mail server and told Imail V5.07 that it is >mail.castlegate.net and the alternate name is castlegate.net. that's backwards: consensus here is NOT like the Ipswitch doc. Put default domain as castlegate.net and alias as mail.castlegate.net. >One of our owners had the other company put our Primary DNS server This one of yours has hostname of what? >as their secondary. >Remember that castlegate.net is the other company's primary domain name! natch, got it. >We got castlegate.net customers to work just fine uh, doing what?? >BUT all the domains that she is hosting were having a problem. People >could get to their web pages just fine but when they tried to get to their >email from our system they would >constantly get the web site please give a domain that is having this pb. Please be precise: "to get to their email from our system they would constantly get the web site" ??? >rather than their mail server which is now known >as imail.castlegate.net. # dig imail.castlegate.net ; <<>> DiG 8.2 <<>> imail.castlegate.net ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUERY SECTION: ;; imail.castlegate.net, type = A, class = IN ;; ANSWER SECTION: imail.castlegate.net. 1H IN A 207.168.201.15 ;; AUTHORITY SECTION: castlegate.net. 1H IN NS NS.castlegate.net. ;; ADDITIONAL SECTION: NS.castlegate.net. 1H IN A 207.168.201.1 That looks ok. >The strange thing is our mail server cannot seem to get the correct MX >record from their machine. what does it get? What DNS have you told Imail to use? I'd use: 207.168.201.1 >Yet if we check their machine using what? >it gives the proper answer of 207.168.201.15 for the MX record and our DNS >responds properly as well. me, too, see above. >As a result we had the other company change their DNS records so that each >domain on their system shows the mail server. lost me, can you show the before/after DNS records rather than a word description? >So when you type the name into what? >kellyford.com the result is 207.168.201.15 # dig kellyford.com mx ; <<>> DiG 8.2 <<>> kellyford.com mx ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUERY SECTION: ;; kellyford.com, type = MX, class = IN ;; ANSWER SECTION: kellyford.com. 59m18s IN MX 10 207.168.201.15. ;; AUTHORITY SECTION: kellyford.com. 1d21h34m49s IN NS NS.FIRSTPLACE.NET. kellyford.com. 1d21h34m49s IN NS NS.CASTLEGATE.NET. ;; ADDITIONAL SECTION: NS.FIRSTPLACE.NET. 5h43m31s IN A 207.168.202.1 NS.CASTLEGATE.NET. 1d23h55m7s IN A 207.168.201.1 stay tuned ... Len Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list.
