Exchange Server

instauratio · Guest

Windows2003 SBS
Exchange2003

I just last week had my DNS host put pointers in his server so that mail
starts going directly to my server.

How can I know that this is working as it is supposed to? That is to say,
how will I know when I can delete the accounts at my previous host?

How can I test?
Thanks

Andy David - MVP · Guest

On Mon, 28 Nov 2005 10:59:02 -0800, "instauratio"
<instauratio@discussions.microsoft.com> wrote:

instauratio · Guest

thanks for the reply David,

I tested and found that the site dnsreport.com brings back successful, but
then cites a totally unknown mail server mx.webminders.com????? It even has
their IP address and not mine?

Can anyone help me understand why I would be getting a response like this?
If not the mx pointers?

"Andy David - MVP" wrote:

Lanwench [MVP - Exchange] · Guest

In news:6E1E05B2-1A81-48E1-BF42-16B17129BEF9@microsoft.com,
instauratio <instauratio@discussions.microsoft.com> typed:

instauratio · Guest

Indeed, they are not in any way associated with this company. I don't
understand how this could happen. I gave my host specific instructions.

Plus, I tested by telneting to my exchange server address:port 25?

I don't want to burden you with too much here Lanwench, but I'm faced with
several questions.

Why is my domain name pointing to another mail server in spite of my hosts
supposed changes? If I approach my host on this issue, how can I state
difinitively what has happened, how I'm sure it's happened and demand that he
correct it at once. (he doesn't have an interface in which I can manage my
own records).

Also, is this, would this be in fact why I can send email and not receive? I
know this must strike some as a naive question, but I'm baffled as to how
this happened in the first place, let alone the repercussions.

Are you familiar with this mx.webminders.com? Do you have any idea why it
would be directed towards them (besides ineptitude on the part of my host)?

Can an mx pointer become corrupted in some way? If my pointers at my host
are pointing to this rogue server, how is it that I can still telnet to my
mail server on port 25?

hope I haven't drowned you! thanks

"Lanwench [MVP - Exchange]" wrote:

instauratio · Guest

Thanks Lanwench for replying.

I found that I can telnet to port 25 on my email server name

I found that I can also send email out. Outgoing email arrives almost
instantaneously (as you would expect)

I'm pretty sure that the DNS host has the right info. I asked him to change
it about 1 week ago, and it has worked well for at least 2 business days. It
just started to show problems today. The main problem seems to be receiving
email. Up until close of business today, it seemed the email was just slow to
arrive. But, now almost 5 hours after waiting for expected email, I'm
convinced that there is a serious issue.

The domain name is dgbco.com or dgbco.net
This is windows2003 SBS with Exchange. Mostly setup "out of the box" I see
nothing particularly wrong when I look through the events or the exchange
system manager. But then I'm not exactly expert.
Thanks

"instauratio" wrote:

Lanwench [MVP - Exchange] · Guest

In news:464497F6-F471-434F-874F-7B0CC2092A82@microsoft.com,
instauratio <instauratio@discussions.microsoft.com> typed:

Lanwench [MVP - Exchange] · Guest

In news:6CCC0AD5-859B-4EBB-9AF4-111187D6B8FC@microsoft.com,
instauratio <instauratio@discussions.microsoft.com> typed:

seth · Guest

i was looking at the information on your domain name, thinking somehow maybe
the webminders name was setup for secondary mail server, but it doesn't look
like it is with the same company.

yes it would explain why you can send mail and not receive
on the outside, there is a pointer for your email, but it's pointing in the
wrong direction
if your exchange server is named (for example) mail.dgbco.com then an mx
record needs to replace the webminders address with mail.dgbco.com with your
exchange server's ip
being able to telnet on 25 to your server is good to know it's working.
when someone on the outside sends you mail, it checks dns for the mx record
for your domain, which currently is mx.webminders.com so it attempts to
deliver the mail there; the other end doesn't know about your mail server.
changing the mx record to your mail server will allow mail to go to you.

this should explain it more
http://www.han.com/dns.html

HTH

"instauratio" <instauratio@discussions.microsoft.com> wrote in message
news:6CCC0AD5-859B-4EBB-9AF4-111187D6B8FC@microsoft.com...

	Exchange Server Forum Index -> Exchange General	All times are GMT
Page 1 of 1