Re: Renaming the "external" DNS for your SBS server
- From: "Chris Lehr" <chris.lehr@xxxxxxxxx>
- Date: Sat, 17 Feb 2007 17:28:57 -0500
Wow,
Sorry you typed so much.. I know SBS well, and am very familiar with DNS
internal/external and was not talking about renaming the server at all (its
named COMPANYSBS, actually)
It wass just sloppy that the SMTP banner doesnt match and was bugging me.
I changed the masquerade setting as you suggested (thanks!) and restarted
SMTP and that did it.. (and I guess the reg key I searched and found is
the one that the masquerade setting was! (I feel dumb that I didnt look
there)
Thanks!
Chris
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OPmC1CrUHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
In news:OJpUhVfUHHA.4756@xxxxxxxxxxxxxxxxxxxx,
Chris Lehr <chris.lehr@xxxxxxxxx> typed:
I have a SBS 2003 Std customer, who early on did not have control
over his DNS,
Meaning, his *public* DNS...not good, but actually not relevant here.
so I was forced to set up his extenal DNS as
mail2.company.com during the initial install.
No; you can't do anything to his "public" DNS during SBS/AD setup, you
aren't hosting his public DNS in house, and you don't even need a publicly
registered internet domain name to install or run SBS anyway. The server
name you chose MAIL2 (and it seems that's what you're most concerned
about) isn't technically part of the AD domain name - it's a host on the
internal company.com domain. The internal FQDN of the server is now
(permenantly) mail2.company.com. Remember, your internal/AD DNS structure
has absolutely nothing to do with your internet domain's DNS. During the
SBS install, the setup wizards include a recommendation not to name your
private DNS the same as your public one - it would automatically have
suggested "something.local" - which you can then change to suit your
needs, such as:
company.local
company.lan
internal.company.com
...or even
adorablefluffy.bunny
None of these have any bearing on his public domain name, although the
latter suggestion might be a bit embarrassing unless your boss is a
ten-year-old girl :)
Using myrealinternetdomain.com *works* but has some consequences...see
below.
Since then, he has
finally reacquired control over his DNS after jumping through the
appropriate hoops. (hooray!)
Indeed!
The server is up, and working at mail.company.com now, but the SMTP
banner still reports the mail2.company.com name. Not a problem, mail
flows, all works, etc..
Yes, it works fine...although now that the DNS server MAIL2 thinks itself
authoritative for the company.com domain, your internal users won't be
able to access externally hosted resources such as www.company.com - the
SBS server will try to resolve it internally, and won't find it. In that
case, you'd need to add a host for www in the internal DNS server, in the
forward lookup zone, and enter the real public IP for the website. Same
with anythingelse.company.com. Etc.
I have rerun the CIECW, this setting isn't part of the CIECW.
That's correct....you cannot rename your server (which is what you're
talking about), or your AD domain, using SBS...and hell, even with regular
W2003 AD & Exchange on a member server, this is not fun. With SBS, you'd
need to completely reinstall, and why bother?
Using the CEICW, you *can* change stuff like the name of the Internet
domain you use for email, etc..and create/modify your self-signed SSL
certificate if you haven't bought a third party cert. (you really need SSL
for OWA/RWW, RPC over HTTP, and wireless Activesync). The cert name should
match the correct public A record for your domain - which is in the public
DNS. Often this is mail.company.com but it doesn't have to be, of course.
I know
I can change two regkeys,
Hmm - I'm curious as to which ones you mean. You don't need to do anything
in the registry for your Exchange server's SMTP banner...
restart SMTP, and fix this, but I dont want
to do the "non-SBS" way, and haven't found the SBS way yet.
This isn't SBS specific, but in your Exchange System Manager, you can
navigate to the properties of the vsmtp server, and set the "masquerade
domain name" to whatever you like (mail.company.com). There's probably no
need to do this, though, unless you just don't like the way it looks
currently, or are running into problems sending mail to domains run by
overzealous antispam/RBL whackjobs.
HOW TO: Set the Masquerade Domain Name in Exchange 2000 Server (misleading
title)
http://support.microsoft.com/kb/314331
Or - if you just want things to match, change the public domain's DNS A
record (currently mail.company.com), to mail2.company.com. Then you don't
have to do anything in Exchange at all.
HTH....if I've misunderstood anything, please correct me.
Anyone?
Chris
.
- Follow-Ups:
- Re: Renaming the "external" DNS for your SBS server
- From: Lanwench [MVP - Exchange]
- Re: Renaming the "external" DNS for your SBS server
- References:
- Renaming the "external" DNS for your SBS server
- From: Chris Lehr
- Re: Renaming the "external" DNS for your SBS server
- From: Lanwench [MVP - Exchange]
- Renaming the "external" DNS for your SBS server
- Prev by Date: Re: Can't browse across subnets
- Next by Date: Question about hosting multiple email domains
- Previous by thread: Re: Renaming the "external" DNS for your SBS server
- Next by thread: Re: Renaming the "external" DNS for your SBS server
- Index(es):
Relevant Pages
|
Loading
