Odd - I can't find any specific mention of this in the documentation, but: SME does not serve as an Internet DNS server. You MUST configure your external IP and your various public DNS settings on a public DNS server outside of your local network.
I suppose this is your option 'B'.
DNS is an odd beast; imagine the following scenario:
Root_DNS
| Registrar
| / DNS Server
| / / Other_DNS
| | / /
Internet---Other_ISP---Remote_User
|
Your_ISP---Your_ISPs_DNS
|
SME
|
Local_User
Let's assume that
- SME has IP Address a.b.c.d
- SME has domain name mysmeserver.com
- Remote_User is configured to use Other_DNS for DNS lookups
If Remote_User tries to browse to
http://mysmeserver.com, his computer asks Other_DNS how to find 'mysmeserver.com'. Other_DNS server then
- asks the Root_DNS servers where 'mysmeserver.com' is registered
- asks the Registrar where to get specific answers for 'mysmeserver.com'
- asks the DNS_Server for the IP address of 'mysmeserver.com'
- saves the answer in its local cache for the amount of time specified by the administrator of the DNS record at DNS_Server.
If, on the other hand, Remote_User asks for information about your IP address (a.b.c.d), his DNS server
- asks the Root_DNS servers where d.c.b.a.in-addr.arpa is registered.
- asks the Registrar where to get more info about d.c.b.a.in-addr.arpa. This is probably but not necessarily Your_ISPs_DNS.
- asks the host indicated by the Registrar (probably Your_ISPs_DNS) what name belongs to 'd.c.b.a.in-addr.arpa'. The return value is almost always a generic filler based on your IP address unless you contact your ISP and ask them to change the PTR data for your IP address.
Basically, PTR records are managed by the organization that controls the IP address (which makes sense, if you think about it).
If Local_User tries to open
http://mysmeserver.com (assuming a default SME installation with DHCP and therefore DNS provided by the SME server):
- If mysmeserver.com is configured for Local resolution, the SME server returns the data that has been configured locally.
- If mysmeserver.com is configured to use Internet DNS Servers, the SME proceeds just as the first example from Root_DNS to Registrar to DNS_Server to local cache (actually, it checks the local cache first...)
So, for you to host a public web server at your location you need:
- An ISP to provide connectivity
- A DNS Registrar where you can 'register' your domain name and publish the addresses of your DNS servers.
- A DNS service provider who will respond to queries about your domain
Some ISP's provide registration and DNS hosting capabilities as part of the connectivity package.
Some ISP's provide DNS hosting but not Registration as part of the connectivity package.
Some Registrars provide DNS hosting as part of the registration.
Sometimes you will need 3 separate vendors for these separate services.
You need to find out if your Registrar provides DNS hosting services, and if so, how to configure them. They'll provide you with a web address where you can configure your DNS.
If they do NOT provide DNS hosting services, your ISP might. Ask them. If so, configure your DNS on their servers, then edit the Registrar page to point to the DNS servers indicated by your ISP.
If neither your Registrar nor your ISP provides DNS hosting, you'll need to find a 3rd vendor to do this. I use 'PairNIC' here in the US and pay a few dollars per year for DNS hosting that is reliable and easy to configure. You could also use DynDNS, etc. Once you have a DNS hosting account, setup your hosts on the hosting server, then change the 'DNS servers' settings on your Registrar's site.
One last item: the PTR (or 'Pointer', or 'Reverse DNS') address of your IP address only becomes important once you start hosting email on your system - some providers will not accept your email if the name returned by the 'reverse lookup' of your IP address does not in its turn result in your IP address when it, itself is looked up. It doesn't necessarily need to match your configured domain name (since so many providers host multiple domains on one IP), but it has to work both ways. In your example this means that if your reverse lookup is
dsl-58-x-xx-xx.location.myISP'sname.com.au then before trying to send email directly from your SME to the Internet at large you want to make sure that
nslookup dsl-58-x-xx-xx.location.myISP'sname.com.au returns your IP address (not an error, and not some other address).