Hello

What do I need to do at the ISP to ensure that remote.mycompany.com is
resolved. Do I need them to set up an a record to point to my external IP
address? If I do need this, will I need to do anything else?



thanks for your help

First, do you really use your ISP to manage your DNS? I'd much prefer to not
have them anywhere NEAR it, and currently use ZoneEdit.com for ours.

But, leaving aside that question, yes, you need to have them create an A
record for remote.mycompany.com pointing to your external IP address.
Ideally, you should also have a PTR record for your IP address as well
(reverse DNS record).

--
Charlie.
http:/msmvps.com/blogs/xperts64


"JD" <noreply@newsgroup> wrote in message
news:e5b9vv0PKHA.5032@newsgroup

> Hello
>
> What do I need to do at the ISP to ensure that remote.mycompany.com is
> resolved. Do I need them to set up an a record to point to my external IP
> address? If I do need this, will I need to do anything else?
>
> thanks for your help

Yes you will need to set up a DNS A record to point to remote.mydomain.com

One of the things I have done is created subdomain forward that looks like
this...
1. domain = abccompany.com
2. DNS A record for "remote" pointing to external IP address of SBS
3. myremote subdomain forward points to https://remote.abccompany.com

That way you tell your users just to type in myremote.abccompany.com and it
takes them right to the https. I can't tell you how many times people just
put in remote.abccompany.com and it will not work if you have port 80 shut
down (which you should). They miss the https part.

"JD" <noreply@newsgroup> wrote in message
news:e5b9vv0PKHA.5032@newsgroup

> Hello
>
> What do I need to do at the ISP to ensure that remote.mycompany.com is
> resolved. Do I need them to set up an a record to point to my external IP
> address? If I do need this, will I need to do anything else?
>
> thanks for your help