Re: Problem running Split DNS configuration and Exchange mailboxes?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Which IP address did you use to point to you own mail server (LAN or WAN)?
I'm also not understanding why you didn't do an AD integrated zone and I
wouldn't recommend the POP3 solution. If you want a backup for email you can
implement that with either your ISP or some other service where you have a
second MX record with a lower value (20 or something) pointing to that
server. If your mail server is not reachable, mail will be delivered to the
second server which will hold the mail until your server is available again
and then push the mail over.

I would first, delete that second zone and create a new AD integrated one
called "yourdomain.com". Enter the www record for your offsite hosting, an A
record for your own server (use the same name as the one you used in your
certificate) and point it to the WAN IP of your SBS. If you want you can
also create that A record that points to the POP3 mail server.

Either an email integrated distribution group or a user should work fine.
--
Claus
<bob.smith.0182@xxxxxxxxx> wrote in message
news:1190688068.804422.32490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hey all,

Thanks for your help. I know it does seem a bit confusing basically:

Split DNS means:
Forward Lookup Zone has TWO Zones:
1. Installed by default domain.local Zone
2. Custom setup NON-AD integrated domain.com Zone that allows us to
use email.domain.com pointed to server, but domain.com pointed to our
hosting servers offsite

Basically the issue is that we could not send internal emails to the
hr_recruiting@xxxxxxxxxx email - it returns a NDR with error 5.1.1 but
from external email accounts (e.g. yahoo/gmail/hotmail accounts, it
can receive ok)

I tried setting up hr_recruiting two ways:
1. As a user mailbox - linked to the manager's mailbox
2. As a distribution group (with manager and HR staff linked as
members of distribution group)

Both ways turned up NDR errors of 5.1.1 when sending internally, but
could still receive from external accounts.

We have implemented POP3 connector to provide redundancy - so that our
mail is still received when our server is offline or our internet
connection is down, as our POP3 is hosted externally by redundant
hosting servers.

Only mentioned OWA because i was using OWA to check it at the time (to
lazy to use RPC over HTTPS at the time but normally do use it :P)

Thanks for your help.



On Sep 24, 11:37 pm, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
Let's see if I understand this correctly.
First, your setup looks normal and I'm not sure why you call it a split
DNS
configuration. I would however recommend that you switch your users to
Outlook over HTTP instead of having them use OWA. I also would drop the
POP3
connector.

As to hr_recruiting, is that a mail enabled distribution group?

--
Claus<bob.smith.0...@xxxxxxxxx> wrote in message

news:1190635898.460363.172700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



We currently have a Split DNS Configuration running, where staff using
OWA are allowed to use our external domain (email.domain.com) to check
OWA INTERNALLY to (i.e. can use email.domain.com internally and
externally). Because of this, we have created Host (A) records that
link to our website (domain.com) IP address, but have pointed
email.domain.com in a Host (A) record to our server IP address. We
have also added correct MX Records and Host (A) Records to point to
our mail server (we use POP3 Connector to provide redundancy for our
mail services). Our Human Resources staff have their account
hr_recruit...@xxxxxxxxxx that works in a similar fashion to your
proposed solution to running exchange distribution groups. However, as
the hr_recruit...@xxxxxxxxxx address is not actually linked to an
existing user account (whereas previously, our accounts and sales
accounts were), we are receiving Exchange NDR emails (error 5.1.1)
reporting that we cannot internally send email to
hr_recruit...@xxxxxxxxxx however it is receiving fine from external
emails. Could this possibly conflict with the Split DNS Configuration?

Might seem a bit random/confusing so just reply me if you need
configuration

Thanks

cheers- Hide quoted text -

- Show quoted text -



.

Relevant Pages

  • RE: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... Run the CEICW and go through the Internet and firewall option. ... If you choose to forward emails to the ISP's email server (smart ... Connector for POP3 Mailboxes' option, ... The Mailbox type is User Mailbox, and select the appropriate Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: mailbox disabled
    ... Your POP3 connector question made me realize that the ... we got tunnel vision thinking it was a server problem. ... that the mailbox was disabled. ... I stepped back today to see what the accounts that were working seemed to ...
    (microsoft.public.exchange.admin)
  • Re: How Best to Use Exchange in Our Company
    ... consisting of 1 server and 4 desktop machines.As the unofficial ... POP3 account into their Outlook. ... previous experience with Exchange, but am totally new to SBS. ... different than our publicly registered Internet domain name. ...
    (microsoft.public.windows.server.sbs)
  • Re: mailbox disabled
    ... POP3 provider was still being used as a backup. ... it was a server problem. ... just from the senders' servers stating that the mailbox was ... I stepped back today to see what the accounts that were working ...
    (microsoft.public.exchange.admin)
  • Re: 0x80042108
    ... This posting is provided "AS IS" with no warranties, and confers no rights ... > and by default has web traffic enabled only i.e. no pop3 or ftp. ... >>> I can confirm that we're not running the ISA server or clients. ... Are you perhaps using an Internet Services Accelerator server? ...
    (microsoft.public.outlook.general)