|
|
Can someone explain this response to me?
H:\>nslookup
Default Server: archive.domain.com
Address: 192.168.101.4
[Quoted Text] > set type=mx
> domain.com
Server: archive.taray.com
Address: 192.168.101.4
domain.com
primary name server = archive.domain.local
responsible mail addr = hostmaster.domain.local
serial = 4
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
I am setting up a second mail server on site. domain.local is a local
Windows domain, and the Exchange mail server is working fine. The
company has a R&D spinoff company which had hosted e-mail in the past
and we purchased a CentOS box to bring the e-mail in-house.
Everything works great with the new e-mail server EXCEPT we can not
e-mail from the Exchange server to the CentOS server. I believe it is
a DNS issue since a manual resolution gives me the result above
instead of a MX record lookup. I did create a local MX record
192.168.101.249 and can ping and telnet/25 to that address. I can
also manually send a message to the CentOS box via telnet and manually
doing helo, mail from....
Is it possible to have two mail servers for two different internet
domains, but internally have DNS set up with local zones? I set up
teh following in DNS-
domain.local-Local Active directory DDNS entries
primary zone (non AD integrtated) domain.com, with www, mail, and MX
for domain.com
primary zone (non AD integrated) domain-tek.com, with www, mail, and
MX for domain-tek.com
Ping resolves everything correctly
Any help?
TIA
Mike Z
--
Posted via a free Usenet account from http://www.teranews.com
|
|
In news:058q23pa4jhtmvtiqqff7umf32abvbfdvp[ at ]4ax.com,
Mike Smith <mike_z[ at ]excite.com> typed:
[Quoted Text] > Can someone explain this response to me?
>
> H:\>nslookup
> Default Server: archive.domain.com
> Address: 192.168.101.4
>
>> set type=mx
>> domain.com
> Server: archive.taray.com
> Address: 192.168.101.4
>
> domain.com
> primary name server = archive.domain.local
> responsible mail addr = hostmaster.domain.local
> serial = 4
> refresh = 900 (15 mins)
> retry = 600 (10 mins)
> expire = 86400 (1 day)
> default TTL = 3600 (1 hour)
>
>
> I am setting up a second mail server on site. domain.local is a local
> Windows domain, and the Exchange mail server is working fine. The
> company has a R&D spinoff company which had hosted e-mail in the past
> and we purchased a CentOS box to bring the e-mail in-house.
> Everything works great with the new e-mail server EXCEPT we can not
> e-mail from the Exchange server to the CentOS server. I believe it is
> a DNS issue since a manual resolution gives me the result above
> instead of a MX record lookup. I did create a local MX record
> 192.168.101.249 and can ping and telnet/25 to that address. I can
> also manually send a message to the CentOS box via telnet and manually
> doing helo, mail from....
>
> Is it possible to have two mail servers for two different internet
> domains, but internally have DNS set up with local zones? I set up
> teh following in DNS-
>
> domain.local-Local Active directory DDNS entries
>
> primary zone (non AD integrtated) domain.com, with www, mail, and MX
> for domain.com
>
> primary zone (non AD integrated) domain-tek.com, with www, mail, and
> MX for domain-tek.com
>
> Ping resolves everything correctly
>
> Any help?
>
> TIA
>
> Mike Z
Your nslookup is using domain.com but you say it is called domain.local. Is
that a misprint?
Does the MX record for domain.com or company.local zone exists on server
192.168.101.4?
The CentOS server will need to resolve the MX for the domain.local or
domain.com, whichever it is, zone. If CentOS is using it;s own DNS and does
not have a reference (a way to get there) to the domain.local or com zone,
then whatever you changed on one of the servers, the CetnOS doesn't have
access to it.
You can use Conditional Forwarding for that specific zone to send any
resolution requests for domain.local or com to that specific DNS.
--
Regards,
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations
Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
"Quitting smoking is easy. I've done it a thousand times." - Mark Twain
|
|
On Tue, 24 Apr 2007 01:42:04 -0400, "Ace Fekay [MVP]"
<PleaseAskMe[ at ]SomeDomain.com> wrote:
[Quoted Text] >Your nslookup is using domain.com but you say it is called domain.local. Is
>that a misprint?
Not a misprint. It could be causing the problem though.
>Does the MX record for domain.com or company.local zone exists on server
>192.168.101.4?
Yes
>The CentOS server will need to resolve the MX for the domain.local or
>domain.com, whichever it is, zone.
There are 3 zones-
domain.local (Active Directory Integrated, installed by DCPROMO)
domain.com (Primary, non AD-set up to resolve certain websites to
internal addresses, including mail internally. Public MX record
points to routable address and hosted with ISP DNS)
domain-tek.com (Primary, non-AD-set up with new server installation to
host internal MX record, www, and several other A records. Public MX
record points to routable address and hosted with ISP DNS)
>If CentOS is using it;s own DNS and does
>not have a reference (a way to get there) to the domain.local or com zone,
>then whatever you changed on one of the servers, the CetnOS doesn't have
>access to it.
I set up the CentOS to use the Windows DNS. I thought I would be able
to keep things simple by only having one DNS internally for
everything. I am most familiar with Windows DNS, too. Mail IS
flowing from CentOS to Exchange without problems so DNS is resolving
fine in that direction. It is domain.com --> domain-tek.com which is
not working. Both domain.com and domain-tek.com can send/receive mail
internally and externally with the only exception being domain.com -->
domain-tek.com.
>You can use Conditional Forwarding for that specific zone to send any
>resolution requests for domain.local or com to that specific DNS.
I tried that but I probably need to confirm some of my CentOS settings
for DNS because it did not work.
I guess I do have these questions which knowing the answer to may help
my investigation.
Does Exchange need a MX record internally in DNS? The messages from
domain-tek.com to domain.com do not need to go outside of the building
and then back so they are resolving internally.
Is there any reason why I can't have DNS set up to have domain.local,
domain.com and domain-tek.com, with each .com set up with a MX record?
What does this nslookup response actually mean?
H:\>nslookup
Default Server: archive.domain.com
Address: 192.168.101.4
> set type=mx
> domain-tek.com
Server: archive.domain-tek.com
Address: 192.168.101.4
domain-tek.com
primary name server = archive.domain.local
responsible mail addr = hostmaster.domain.local
serial = 5
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
I was expecting to see something like:
[admin[ at ]mail ~]$ nslookup
> set type=mx
> domain-tek.com
Server: 192.168.101.250
Address: 192.168.101.250#53
domain-tek.com mail exchanger = 10 mail.domain-tek.com.
CentOS release 4.4 (Final)
Kernel 2.6.9-42.0.10.ELsmp on an i686
login:
Password:
Last login: Mon Apr 23 16:57:30 from apps.domain.local
[admin[ at ]mail ~]$ nslookup
> set type=mx
> domain-tek.com
Server: 192.168.101.250
Address: 192.168.101.250#53
domain-tek.com mail exchanger = 10 mail.domain-tek.com.
What would be a "best practice" here?
Exchange 2003 hosting domain.com
SendMail Server hosting domain-tek.com
sharing a 192.168.101.0 network
Should I only use Windows DNS since I am running AD?
-OR-
Should I use WIndows DNS and linux DNS with conditional forwarding set
up in Windows DNS?
-OR-
something else?
Mike
--
Posted via a free Usenet account from http://www.teranews.com
|
|
On Tue, 24 Apr 2007 01:42:04 -0400, "Ace Fekay [MVP]"
<PleaseAskMe[ at ]SomeDomain.com> wrote:
[Quoted Text] >You can use Conditional Forwarding for that specific zone to send any
>resolution requests for domain.local or com to that specific DNS.
I got it!
I did try conditional forwarding like I said but after your suggestion
I tried it again. This time it worked. I probably had a
configuration problem before but now it works. Thanks for the
suggestion
Mike
--
Posted via a free Usenet account from http://www.teranews.com
|
|
In news:ndls23169idqq000he2c2aujfmnu9v8nf1[ at ]4ax.com,
Mike Smith <mike_z[ at ]excite.com> typed:
[Quoted Text] > On Tue, 24 Apr 2007 01:42:04 -0400, "Ace Fekay [MVP]" > <PleaseAskMe[ at ]SomeDomain.com> wrote: > > >> You can use Conditional Forwarding for that specific zone to send any >> resolution requests for domain.local or com to that specific DNS. > > I got it! > > I did try conditional forwarding like I said but after your suggestion > I tried it again. This time it worked. I probably had a > configuration problem before but now it works. Thanks for the > suggestion > > Mike
That is GREAT to hear!!
You are quite welcome.
:-)
Ace
|
|
|