Re: Internal / External DNS problem.
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 10:12:21 -0400
In news:99F7735C-94C4-4F34-8215-201EBA88B1B6@xxxxxxxxxxxxx,
Adrian Coles <AdrianColes@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi,
Thanks Lanwench, that is how my set up is... set up.
However, I think Leythos has hit the nail on the head.
<winces> That was my head, actually. Do you have any ibuprofen?
In effect, the mycompany.co.uk internally is resolving to the
external IP address and therefore cannot connect.
No, that doesn't matter. It *should* be external. When I'm on my LAN and
ping mail.mycompany.com it resolves to my public IP. As it should.
But my Exchange client
is not connecting to mail.mycompany.com as its server - it's connecting to
servername.mycompany.local.
My internal network knows nothing about
mycompany.com nor mail.mycompany.com - it doesn't need to.
How do I
"setup my internal DNS to resolve the FQDN to private addresses before
anything else with work with the public name."
You don't.....
How do I get:
"My DNS shows mycompany.local and mycompany.com as two different
forward zones, the mycompany.com zone has pointers that match the
public DNS names but have private addresses that point to the proper
server/node." working on my server?
Thanks to both of your help, sorry if my lack of correct terminology
has caused any confusion.
No big deal. Did you read the link on the RWW page as I've suggested?
.
- Prev by Date: Re: Added second Nic but the email CEICW wizard does not recognize it
- Next by Date: Re: RWW vs VPN - Printing at home
- Previous by thread: Re: Internal / External DNS problem.
- Next by thread: Re: Internal / External DNS problem.
- Index(es):
Relevant Pages
|
