Hi Dean29000,
Hope you managed to get this all working, however if not i'll try and clarify what techsoeasy and Skreem have correctly instructed you to do.
Bit of background.
DNS record is hosted by a DNS host. This is often the domain registrar, else a specific DNS host, sometimes if you have a seperate webhosting provider they will host your DNS records for you.
DNS record in your case seems to be hosted with your registrar.
Two important records to get email flowing:
1. MX record
2. Corresponding 'A Name' record.
[] MX record points to an arbitrary 'A Name' record. ie mail/email/fred/tony/jeff (it really does not matter which name you pick)
[] Next you require a corresponding 'A Name' record. If you picked 'mail' then you would create an A name record called mail. likewise jeff or tony.
The A name record points to an explicit IP address. In this instance the IP address would be the static external IP address of your mailserver.
So you might have a DNS record looking something like this:
Code:
DNS record for domain: mycompany.com.au
A records:
----------
www --> 203.12.150.47 (ie. [URL unfurl="true"]www.mycompany.com.au)[/URL]
mail --> 220.231.56.12 (ie. mail.mycompany.com.au)
ftp --> 220.231.56.12 (ie. ftp.mycompany.com.au)
MX record:
----------
(mx record) --> mail.mycompany.com.au
Next you need to configure and NAT or port forwarding you might have at the perimeter router/firewall level. This will be device dependant, however for a layer-2 f/w you would NAT through all traffic from the WAN interface incoming on port 25 (SMTP port) to the internal IP address of your mailserver (still port 25/SMTP).
If your firewall does not automatically do this you may also need to configure a WAN firewall rule permitting traffic across the WAN interface inbound from port 25 to your mailservers internal IP on port 25. (Hope this makes sense).
Ensure any software based f/w are not blocking traffic.
At this point you should have created the appropriate DNS records required and opened up access to your mailserver so email can arrive at it for processing.
Now you will need to run the SBS configuration wizard to ensure that the mailserver is aware that it should be accepting email for your email domain(s). (If you don't tell it that your email domain is mycompany.com.au it will reject email addressed to that domain)
Now that your email server is configured, double check your email address from active directory (Or the SBS user panel) and update if incorrect email address.
Now when bob.brown@greens.gov.au wishes to send you an email from his account, his email server looks up the mx record for mycompany.com.au negotiates with your mailserver and transfers the email direct to your mailserver.
You don't actually need to configure your email server to pulldown the email from a specific server **UNLESS** you have a 3rd party server in the mix such as a POP3 server OR a 'smarthost' which essentially 'washes' (spam/virus checking etc) before it hits your systems.
This seems a little long and windy explanation, more about the conceptual ideas rather than specific tech terminology so please don't hesistate to ask for clarification.
Cheers - blakey2