SMTP could not connect to any DNS server

[Steve Schofield]

I'm curious to here Sandy's input on

"SMTP could not connect to any DNS server. Either none are configured, or
all are down."

All the help I see on the net is related to Exchange. Under the relay tab,
the wrong host name was listed. Do you think this is possible to cause the
event id 2013 error.

We've disabled EDNS on our Windows Server 2003 sp2 AD / DNS servers. This
error is not constant, just happened on a server here and there.

Thoughts?

[Steve Schofield]

Never fails when I post a question (basically giving up). I find something.
http://support.microsoft.com/default.aspx?scid=kb;en-us;330070

Adjusting the metabase to not use TCP?
--
Best regards,

Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield

http://www.IISLogs.com
Log archival solution.
Install, Configure, Forget

Post by Steve Schofield
I'm curious to here Sandy's input on
"SMTP could not connect to any DNS server. Either none are configured, or
all are down."
All the help I see on the net is related to Exchange. Under the relay
tab, the wrong host name was listed. Do you think this is possible to
cause the event id 2013 error.
We've disabled EDNS on our Windows Server 2003 sp2 AD / DNS servers. This
error is not constant, just happened on a server here and there.
Thoughts?
--
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield

[Sanford Whiteman]

"SMTP could not connect to any DNS server. Either none are
configured, or all are down."

Are you sure about the consistent availability of your DNS servers?
Are you using shared DNS servers at your ISP (which can certainly
blink on and off under load), or running your own recursive DNS? How
many?

I'd ensure that your DNS servers are highly available and correctly
configured: no broken forwarders in use, recursion enabled on all.

Also check general network connectivity (switchport, cabling). DNS/UDP
uses very small packets, whose loss can show up problems you might not
otherwise have seen. Corrupted drivers or broken/breaking NICs could
cause packet loss as well.

All the help I see on the net is related to Exchange. Under the relay
tab, the wrong host name was listed.

On the 'Relay' tab? Are you restricting by hostname instead of IP?
This can have some drawbacks, which I posted about a few days ago.

--Sandy



------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
------------------------------------