Hi Phil,
Have you thought of using DNS aliases (CNAMEs) instead of a new standalone
DFS? We often hide things using DNS aliases, although usually not at the
domain name level, more at the hostname level. You could create a new DNS
zone newdom.com, and within that create a CNAME that points to domain.com. To
do this in Windows DNS, first create your DNS zone for newdom.com, then right
click on it and select "New Alias (CNAME)". Leave the "Alias name" field
blank so that it will show "(same as parent folder)" when we are finished. In
the "Fully qualified domain name" field, type in domain.com and click OK.
Please be aware that this may cause you problems with a later migration or
otherwise contacting the real newdom.com domain if you set up trusts etc, as
normally there are A records in the DNS domain root that point to the domain
controllers, i.e. if you ping domain.com, you will get a response from one of
your DCs.
I just tried the CNAME idea outlined above in my lab and it works for a
nslookup and ping, but if I try to browse to \\newdom.com I get an unexpected
authentication prompt. I'm not sure about what to do from here, but it is the
start of an idea for you.
Regards
Paul Whitfield
"durx" wrote:
> We are about to merge companies, and our company has a domain based
> DFS that users map as G:\Global but it also shows "Global on
> domain.com" in my computer.
> What we want (have) to do is hide or alias the domain name to show a
> different domain name, something like "Global on newdom.com".
> Maybe i am doing something wrong here - but I have created a
> standalone namespace and added the folders to point to the existing
> DFS shares, but concerned incase the namespace server cannot be seen
> over the wan (vpn down) and i presume that would make the folders
> unavailable.
> Adding a stanadalone namespace server on each site would help but seem
> a long way round.
> Basically, anything that hides or aliases the domain name would be
> good.
>
> regards
>
> Phil
>
|