Re: DNS MX Problem

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hello Mike,

If i ping your domain and mail server name i got this as an answer:

ping mail.canadaici-van.com

Pinging mail.canadaici-van.com [216.251.32.97] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.251.32.97:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping canadaici-van.com

Pinging canadaici-van.com [216.251.43.11] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.251.43.11:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


So the ip addresses you are talking about are not used.

Also nslookup to your domain and mail server name give the same result:
nslookup canadaici-van.com
Server: canadaici-van.com
Address: 216.251.43.11

DNS request timed out.
timeout was 2 seconds.
*** Request to canadaici-van.com timed-out
nslookup mail.canadaici-van.com
Server: mail.canadaici-van.com
Address: 216.251.32.97

DNS request timed out.
timeout was 2 seconds.
*** Request to mail.canadaici-van.com timed-out

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

Hi Everyone:

Our company had a static IP address from our ISP. However, late one
night,
our ISP did some sort of server upgrade and every one came into work
and had
no internet. Called the ISP tech support and they confirmed their
upgrade and
told us to change static settings on the router to DHCP which we did.
We
unfortunately obtained all new IP information despite supposedly
having a
static IP. Anyway, we now had internet again, but of course cannot
receive
email because no one can now find our Exchange server. We logged into
DNS
manager at our registrar and changed the appropriate records to
reflect the
new IP. Our ISP confirms that our zone file is correct. However, it
has now
been over 40 hours and our mail server is not being resolved
correctly.
Our domain is canadaici-van.com
Our mail server is mail.canadaici-van.com
Our domain is currently showing no MX records for our domain and is
presently being incorrectly resolved to 208.67.219.145. Our new IP is
209.121.x.x number.
The ISP which is also the registrar has no ideas why it is not
working.
Everything is functioning within our network and our server. I can
remotely
connect to the router via the new IP address. I can access OWA via the
new IP
address.
Can anyone see anything that I missing?
Thanks so much,
Mike



.



Relevant Pages

  • Re: DNS MX Problem
    ... and our domain is still resolving to the wrong IP's that you noted. ... If i ping your domain and mail server name i got this as an answer: ... Also nslookup to your domain and mail server name give the same result: ... Our company had a static IP address from our ISP. ...
    (microsoft.public.win2000.dns)
  • Re: connecting via broadband?
    ... > Ping statistics for 193.252.22.137: ... >> mail server and that it is responsive so you get a mail session ... >> host that responds to 'ping' does NOT mean the server program is ... >> actually running or responsive on that host. ...
    (microsoft.public.outlook.general)
  • Re: Strange PPPoe problem
    ... PING longbow.arroway.com 1472bytes of data. ... packets transmitted, 0 received, +1 errors ... server is causing icmp 3/4s from reaching the mail server. ...
    (Debian-User)
  • Re: host availability
    ... >>>google.com, my default gateway, comcast's mail server etc. ... a host was "up or down". ... If you don't get an answer to a ping request, ... happened to reset the interface right then, remote system got trojaned ...
    (comp.security.firewalls)
  • Re: issues with mail - dns
    ... I can not connect to my mail server on port 25 due to it being secure (that ... >> longer ping. ... If not, it's your firewall, dollars to doughnuts. ...
    (microsoft.public.windows.server.networking)