Questions

Pop Connector - DNS Issue

+
0 Votes
Locked

Pop Connector - DNS Issue

westcoastpc
I have a server (SBS 2000) Named abc.com not, local but .com. When 2000 server first came out, that was the way. Not .local, my issues is I setup a pop connector in Exchange, works great. The mail server's name is mail.abc.com. So when the POP connectors kicks off it looks to local DNS for the resolution and sees that the SOA is on the local network and look to the local network. Can?t find it, because it is not local. So I create a mail record for mail.abc.com in the local DNS. Problem solved. Well not really, that IP can and will changed at some point. Is there a way to have the pop connect use and outside DNS server? If I change the server?s DNS to point outside, AD goes crazy....

Thanks!!
Mat
westcoastpc@gmail.com
  • +
    0 Votes
    CG IT

    POP3 is usually used to connect to an ISPs mail server to download email, then Exchange uses SMTP internally to distribute the mail to users mailbox.

    now if your hosting email service and want to know how users can use POP3 to connect to your exchange to get their mail, you have to allow POP3 inbound to exchange. you also have to configure mail boxes for users. If your doing relay, well it's a hackers delight.

    so which is it? are you trying to connect to your ISPs POP3 server to get mail for your users? or are you hosting email for users?

    +
    0 Votes
    westcoastpc

    We are pulling in to the exchange server via the pop connector. Why? Because the MX record was pointing this small SBS server's public address, but they were receiving over 12,000 spam email per day. The serer was getting killed trying to filter spam with GFI. SO I moved the MX record to IPOWER and we pop from them, and only pull mail addresses to real users ... Bob@abc.com not dafasdfasdf@abc.com

    no relay. just poping mail via a pop connector.

    +
    0 Votes
    Whatme?

    #1. Assign your in-house a local static IP. That should not change. In your local DNS as you have said, you insert an A record for your in-house email server with the local fixed IP address. Your In-house DNS server should be forwarding to your outside DNS server. If the outside DNS server is not yours(ISP etc), you will have to ask them to add an MX record for your email server to their DNS server. Now the internet recognizes your email server as well as your networked users.
    If you have DHCP, add your email server to it.
    If you have a firewall, it would be a good idea to put your email server in the DNS zone but either way you will have to insert a rule for the outside to "come in" to your network, probably by a NAT translation

    +
    0 Votes
    westcoastpc

    I think you are the right track, our local DNS does forward to the ISP (SBC), but we are on a SBC DSL. I can?t image calling the 18 year kid @ SBC and trying to get them to add a DNS record. But what I could do is point this server local DNS to forward to another server I has access to (I?m a consultant) and see where I can go from there. If I could write script that would change the servers DNS and then change it back?. Hum?.. GPO?

    Thanks for your thoughts

  • +
    0 Votes
    CG IT

    POP3 is usually used to connect to an ISPs mail server to download email, then Exchange uses SMTP internally to distribute the mail to users mailbox.

    now if your hosting email service and want to know how users can use POP3 to connect to your exchange to get their mail, you have to allow POP3 inbound to exchange. you also have to configure mail boxes for users. If your doing relay, well it's a hackers delight.

    so which is it? are you trying to connect to your ISPs POP3 server to get mail for your users? or are you hosting email for users?

    +
    0 Votes
    westcoastpc

    We are pulling in to the exchange server via the pop connector. Why? Because the MX record was pointing this small SBS server's public address, but they were receiving over 12,000 spam email per day. The serer was getting killed trying to filter spam with GFI. SO I moved the MX record to IPOWER and we pop from them, and only pull mail addresses to real users ... Bob@abc.com not dafasdfasdf@abc.com

    no relay. just poping mail via a pop connector.

    +
    0 Votes
    Whatme?

    #1. Assign your in-house a local static IP. That should not change. In your local DNS as you have said, you insert an A record for your in-house email server with the local fixed IP address. Your In-house DNS server should be forwarding to your outside DNS server. If the outside DNS server is not yours(ISP etc), you will have to ask them to add an MX record for your email server to their DNS server. Now the internet recognizes your email server as well as your networked users.
    If you have DHCP, add your email server to it.
    If you have a firewall, it would be a good idea to put your email server in the DNS zone but either way you will have to insert a rule for the outside to "come in" to your network, probably by a NAT translation

    +
    0 Votes
    westcoastpc

    I think you are the right track, our local DNS does forward to the ISP (SBC), but we are on a SBC DSL. I can?t image calling the 18 year kid @ SBC and trying to get them to add a DNS record. But what I could do is point this server local DNS to forward to another server I has access to (I?m a consultant) and see where I can go from there. If I could write script that would change the servers DNS and then change it back?. Hum?.. GPO?

    Thanks for your thoughts