Re: Forwarders and Existing Zone

Tech-Archive recommends: Speed Up your PC by fixing your registry

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2B6FEF58-BA2B-4C7E-A491-3E82CCC72F19@xxxxxxxxxxxxxxxx
We have a partner company (companyB) that is on our network (separate
domain/forest/DNS environment). I needed to add the MX record/A record of
their receiving mail server to our Windows 2003 DNS and the queue cleared
(Ex2007).

Why?

The MX record is useless if the "public" can't find it. If the "public" can
find it,...then you find it the same way. The other company must have a DNS
"somewhere" out in Internet-Land that is authoritative for their Domain Name
(and hence the MX record "lives" there).

Assuming you use your ISP in the forwarders list of you DNS,...then that's
it. The query is forwarded to the ISP's DNS which then follows the normal
process to resolve anything that it would resolve and the MX is resolved.

Granted there may be something I am missing. Running two companies with two
forests on the same over-all network often creates a "mess",...but for now,
what I stated is how I see it at this point. I don't believe in
over-complicating things.

As a backbground of what I came out of,..
We had roughly 20 locations joined by VPN (hence a private connection, so
logically the same as if in the same building) and each location was a
different company. Each company had their own Domain and their own Exchange,
and their own MX records. I can tell you that I didn't have to worry squat
about what any of the MX records were and never had to maintain anything if
they changed.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


.

Relevant Pages

  • Re: Domain Controller GUID DNS name could not resolve
    ... > apply but nothing for windows 2003. ... The problem you are having is caused from what appears to be a single-label ... entries to enable this but that only fixes one side of the problem, DNS will ... instance DNS will not be able to resolve the domain name to the IP addresses ...
    (microsoft.public.windows.server.dns)
  • NetBIOS name resolution failing, DNS working, ICMP, 445/tcp
    ... I recently discovered that on a Windows machine trying to resolve the ... if NetBIOS name resolution of the hostname ... the IP address that was obtained from the DNS ...
    (microsoft.public.win2000.networking)
  • Re: Need Help from DNS Expert on Subdomain DNS Records
    ... When you use nslookup to resolve these names do you get the correct internal ... domain from within and outside our firewall. ... public IP to point to the same private IP, ... You need to verify that the all DNS servers assigned to a the DNS Client be ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot a DC, HOPELESS Case
    ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
    (microsoft.public.win2000.active_directory)
  • Re: aol..
    ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
    (microsoft.public.windows.server.sbs)