Re: smtp could not connect to any dns server: exchange smtp will not d
From: Omer maydan (omermaydan_at_yahoo.com)
Date: 08/30/04
- Next message: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Previous message: tony adduci: "smtp could not connect to any dns server: exchange smtp will not d"
- In reply to: tony adduci: "smtp could not connect to any dns server: exchange smtp will not d"
- Next in thread: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Reply: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 22:42:41 +0200
first look at these posts as they came from eventid site:
Adrian Grigorof
>From newsgroup posts:
- "It means that your server has not performed a zone transfer from whomever
the master DNS server is for <zone name> in the allocatted time, so the zone
file you have has expired and your DNS server will no longer answer queries
for that zone. Investigate the DNS server holding the master zone"
- "Looks like a problem on the master. Are any of the other slaves (if any)
having any problems with zone transfers of the zone? On your slave, try
doing a non-recursive, TCP AXFR query for the domain from the master. The
error you get back should help you troubleshoot the problem. If you're
not getting any kind of error back, then there is something wrong with your
nameserver."
- "You should probably be looking for a problem like the secondary being
unable to connect to the primary on TCP/IP port 53, or the primary being
configured to deny zone transfer requests from the secondaries IP address.
On the secondary server start by using ping to establish that it can reach
the primary at all. Then, also on the secondary, use NSLOOKUP. Use the
SERVER command to point it to the primary. Then try to manually transfer a
copy of the zone using the ls -d command. This should tell you if the
secondary cannot reach the primary on port 53 or if there is a problem in
the transfer."
also, if you have windows 2003 Dns, you can use other methods to ecommplish
name resolution between the domains without replicating information. you can
setup conditional forwarding to the other server, and by that saving some
hassale.
-- Omer Maydan MCSE, Security+ "tony adduci" <tonyadduci@discussions.microsoft.com> wrote in message news:080C5794-C096-49B5-BCCD-8B2C00B920D2@microsoft.com... > Hello, > I have two exchange servers in two windows domains on one internal subnet > and they are haivng a hard time periodically delivering mail between the two > of them. I also get that error: SMTP could not connect to any DNS server" in > my event viewer on one of my domains. > > Until I added secondary zones I wasn't able to pass mail at all between the > two servers. Each server points to itself only for internal/external dns > resolution. No forwarders exist or no dns servers in the smtp properties of > the connector. > I added secondary zones to each server one for eachothers domain and that > doesn't seem to help. I also see timeout errors relating to DNS in my event > viewer... > > That error is: 6527 zone companyname.com expired before it could obtain a > successful zone transfer or update from a master server.... > > Any ideas?
- Next message: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Previous message: tony adduci: "smtp could not connect to any dns server: exchange smtp will not d"
- In reply to: tony adduci: "smtp could not connect to any dns server: exchange smtp will not d"
- Next in thread: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Reply: tony adduci: "Re: smtp could not connect to any dns server: exchange smtp will n"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
