| Author |
Message |
Tim C
Guest
|
 Posted:
Wed Jan 19, 2005 12:39 am Post subject:
Primary DNS failed to repond |
|
|
Exchange Server 2003 SP1 on Windows 2003 Server DC.
I just updated ExBPA and ran a health check scan.
It reported "Primary DNS failed to respond." I have not seen this message
on previous scans and DNS seems to be running normally (on the same server
as Exchange). I clicked on the "Tell me more about this issue..." link.
Apparently the link is broken or in error, as I was forwarded to the default
Microsoft Exchange Server TechCenter page.
Tim C
|
|
| Back to top |
|
 |
Hank Arnold
Guest
|
| Posted:
Wed Jan 19, 2005 3:54 pm Post subject:
Re: Primary DNS failed to repond |
|
|
I'd try again and then run some diagnostic tests. I believe that you can get
this message if the server is "busy" at the time. I'd want to see the error
more often than just once.
Also, check the DNS event log for similar or other errors.
--
Regards,
Hank Arnold
"Tim C" <timclainc@yahoo.com> wrote in message
news:OUEg9zY$EHA.1300@TK2MSFTNGP14.phx.gbl...
| Quote: | Exchange Server 2003 SP1 on Windows 2003 Server DC.
I just updated ExBPA and ran a health check scan.
It reported "Primary DNS failed to respond." I have not seen this message
on previous scans and DNS seems to be running normally (on the same server
as Exchange). I clicked on the "Tell me more about this issue..." link.
Apparently the link is broken or in error, as I was forwarded to the
default Microsoft Exchange Server TechCenter page.
Tim C
|
|
|
| Back to top |
|
|
Paul Bowden [MSFT]
Guest
|
| Posted:
Thu Jan 20, 2005 11:58 am Post subject:
Re: Primary DNS failed to repond |
|
|
Hi Tim,
The link to the associated article is
http://www.microsoft.com/technet/prodtechnol/exchange/ExBPA/b927d1e3-c764-4aba-9b91-7c936d07e034.mspx
....I just tried this and it works okay for me.
Basically, ExBPA is looking at the DNS search order on your TCP/IP stack,
taking the first DNS IP address on the list, and then attempting to open
port 53 at that address. If the port doesn't appear to be alive, then we
fire this rule.
If you believe that the rule is firing in error, I can definitely
investigate. I'd need the output XML (generated by ExBPA) from your server
to debug. You can send this to pbowden@microsoft.REMOVETHIS.com
Best Regards,
--
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/exbpa
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tim C" <timclainc@yahoo.com> wrote in message
news:OUEg9zY$EHA.1300@TK2MSFTNGP14.phx.gbl...
| Quote: | Exchange Server 2003 SP1 on Windows 2003 Server DC.
I just updated ExBPA and ran a health check scan.
It reported "Primary DNS failed to respond." I have not seen this message
on previous scans and DNS seems to be running normally (on the same server
as Exchange). I clicked on the "Tell me more about this issue..." link.
Apparently the link is broken or in error, as I was forwarded to the
default Microsoft Exchange Server TechCenter page.
Tim C
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in