asked on
DNS or not?
Afternoon All,
Exchange Server 5.5, SP4.
One domain will not leave my IMS queue. Their inbound mail works like a charm, but if I respond to it - just hangs in the queue as [Host unreachable].
I had a stray DNS # (of three) but browsing the Internet was/is working fine, however I removed the stray DNS entry just the same. NSLOOKUP reports back:
Server:ns1.host.net (not exactly - names have been changed to protect the innocent)
Address: IP address of my DNS
If I set type=mx and type the domain name that will not leave my queue, I get Name servers, dhcp server and mail server associated with the domain in question. Does this mean the problem lies in between me and the domain in question?
I cannot telnet to the mail server over port 25 either, but I can from my home via the Internet.
I checked URLSACN logs and everything... cannot find a reason for the madness.... Their end claims it is my end, but this has been an on going thing that I would like to put to rest... Any assistance would ROCK!
Thanks Guys (and ladies),
Ed
Exchange Server 5.5, SP4.
One domain will not leave my IMS queue. Their inbound mail works like a charm, but if I respond to it - just hangs in the queue as [Host unreachable].
I had a stray DNS # (of three) but browsing the Internet was/is working fine, however I removed the stray DNS entry just the same. NSLOOKUP reports back:
Server:ns1.host.net (not exactly - names have been changed to protect the innocent)
Address: IP address of my DNS
If I set type=mx and type the domain name that will not leave my queue, I get Name servers, dhcp server and mail server associated with the domain in question. Does this mean the problem lies in between me and the domain in question?
I cannot telnet to the mail server over port 25 either, but I can from my home via the Internet.
I checked URLSACN logs and everything... cannot find a reason for the madness.... Their end claims it is my end, but this has been an on going thing that I would like to put to rest... Any assistance would ROCK!
Thanks Guys (and ladies),
Ed
Exchange
Last Comment
David Wilhoit
alternately, since you had a dead DNS server, ipconfig /flushdns, restart netlogon service.
D
D
ASKER
Thanks D. That's just it though, how can I prove this to them? I have enabled all exchange diagnostics and message tracking etc, but nothing is giving me a specific point of failure as I sort through the seemingly endless amount of logs!
Do you know of a way I can provide this info?
Thanks!
Do you know of a way I can provide this info?
Thanks!
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If you can telnet to port 25 on 9 different servers, but not on theirs, it's their problem. Prove it to them....
D