Hello,
My problem is that I cannot get mail to pass quickly between two Exchange 2003 servers on the same subnet. The servers point only to themselves with no forwarders for DNS resolution and use root hints to deliver mail to the outside world. Clients have no issues with being able to talk to the servers on either domain.
summary of enviroment:
firewall: 10.0.1.254
exchangeserver1: 10.0.1.5
exchangeserver2: 10.0.1.25
Each server runs dns and is authorative for it's domain internally. Each server has a zone record created with an A record for mail.companyname.com to the proper ip for that 2nd domain... I have no MX records listed in either domain's dns record...
When I look at the queue manager in Exchange it says it cannot bind to the dns server. However nslookup resolves properly. I can ping by name and WINS runs fine.
Instead of creating another primary zone for eachother's domain, I created a secondary zone and setup the zone permissions on the opposite domain to allow zone transfer to the requesting server.
In other words, I permitted zone transfers on each side and created a secondary zone with the domain name of the opposite server in it.
Only after doing this step did I see that mail began to flow for me but still it takes 15 minutes... I cannot speed this process up for some reason.
Any ideas?
I see timeout errors in the DNS manager talking about zone expirations...
This is the error in my DNS event viewer:
Zone companyname.com expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. The zone has been shut down.
When I reload the zone from the server with the mail waiting in the queue it goes out immediately... So I think that my zone info is expiring on each respective server...
1 possible answer is to just fix the expiration problem and the other answer might include a different solution other than loading each zone from the opposite domain that I am administrating... Right?
My problem is that I cannot get mail to pass quickly between two Exchange 2003 servers on the same subnet. The servers point only to themselves with no forwarders for DNS resolution and use root hints to deliver mail to the outside world. Clients have no issues with being able to talk to the servers on either domain.
summary of enviroment:
firewall: 10.0.1.254
exchangeserver1: 10.0.1.5
exchangeserver2: 10.0.1.25
Each server runs dns and is authorative for it's domain internally. Each server has a zone record created with an A record for mail.companyname.com to the proper ip for that 2nd domain... I have no MX records listed in either domain's dns record...
When I look at the queue manager in Exchange it says it cannot bind to the dns server. However nslookup resolves properly. I can ping by name and WINS runs fine.
Instead of creating another primary zone for eachother's domain, I created a secondary zone and setup the zone permissions on the opposite domain to allow zone transfer to the requesting server.
In other words, I permitted zone transfers on each side and created a secondary zone with the domain name of the opposite server in it.
Only after doing this step did I see that mail began to flow for me but still it takes 15 minutes... I cannot speed this process up for some reason.
Any ideas?
I see timeout errors in the DNS manager talking about zone expirations...
This is the error in my DNS event viewer:
Zone companyname.com expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. The zone has been shut down.
When I reload the zone from the server with the mail waiting in the queue it goes out immediately... So I think that my zone info is expiring on each respective server...
1 possible answer is to just fix the expiration problem and the other answer might include a different solution other than loading each zone from the opposite domain that I am administrating... Right?
