Re: Another Internal/External MX question

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 02/29/04 

Date: Sat, 28 Feb 2004 20:37:50 -0500

In news:tIK%b.30092$AL.542446@attbi_s03,
aptrsn <busn66@hotmail.com> posted their thoughts, then I offered mine
> Thanks again for your replies and insight!
>
> Just some observations, you stated:
>
>> Ok, then you wouldn't need an MX record internally at all. Since
>> your Domino machine would be the only thing that really needs the
>> MX, and assuming that your DNS is hosted externally, then the MX
>> would be required for the external domain name so other mail servers
>> on the Internet will know what server is recieving mail for your
>> domain.
>
> This is our current setup and it works just fine IF our internet
> connection is up and not congested.

Honestly I'm not sure what's happening, but MX records just denote who is
the mail server for a domain and are just for mail servers to send mail to
another mail server. That's it.

> However, if the connection goes
> down (rarely) or is congested (frequently) then the resolution for
> all mail addresses (external or internal) either hangs or times out.

I would look at your network infrastructure design, your WAN speed or
problems with the ISP. Sounds like in your case you need to bump up your WAN
speed.

> While there is not much I can do about the resolution for external
> addresses, internal addresses should not have to be dependant on the
> MX record on the external DNS.

That is correct!

> Instead, I figured I could set up the
> root dc for resolving the mail queries with an MX record that points
> to the LAN nic of our Domino server.

I am assuming you are talking about altering your MX record on the external
DNS server, whomever that is you're using to host your external name space,
possibly your ISP...

>
> While I was typing this I realized that I left out some information
> regarding this whole process. I'm not sure if this is the same with MS
> Exchange, but when Domino is configure to "verify sender's domain in
> DNS" it verifies EVERYONE's domain (ie. those user's with accounts on
> Domino).

Yes, there is a setting to verify Reverse DNS in Exchange.

> Since our Domino server resolves to the DNS hosted by our
> ISP, it resolves our internal users addresses to that DNS. If the
> connection is congested or down, mail does not get sent, internal or
> external. So, knowing this, maybe you can understand my desire to
> route our Domain MX queries to the our root dc, rather then
> continuing to route them to the ISP's DNS.

I'm not understanding your use of the terminology here, since routing is an
IP functionality, not a DNS functionality. Routing is also used in mail
delivery between mutli mail servers in an enterprise environment.

Besides, if you're talking about how to resolve external queries, MX queries
are done by the Domino server when attempting to send mail and NOT by
internal clients, whether they are POP clients or Domino clients.

And if your infrastructure is setup properly, you would forward all to the
ISP. If maybe I am understanding this, maybe you want to create your
external zone name on your internal DNS, then go ahead, but keep in mind you
would need to also create your www, ftp and other records too.

Are you currently using your ISP's mail system to receive and send mail and
you have an ETRN or TRN setup to retrieve mail periodically?

> I do have forewarding
> turned on, in which case all other DNS queries by the mail server
> would then be passed on to our ISP's DNS. At this point, everything
> seems to be working, and in having this discussion, I think I know
> have a better understanding as to why it's working.
>
> Thanks again for the discussion.

I hope that helps ..... 

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
-- 
=================================

Relevant Pages

  • Re: Setting up mail server.
    ... then you would have an internal private DNS. ... mail server, you will not need to use DNS to resolve internally, but will ... Domino client installed on all workstaitons. ... How to Configure OEx for Internet News ...
    (microsoft.public.win2000.dns)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
Quantcast