Je suis using mon domain `example.org`in mon firm. I can use `www.example.org`to view mon website. If I try `http://example.org` depuis outsite mon firm there is no problem, mais si I try it depuis inside, mon windows DNS servers deliverthe IPs of domain controllers.
How can I solve this? Can I prevent mon DCs depuis registering as `example.org` in mon DNS et will this be a problem for mon enviroment?
Mon nom de site web public et mon nom de domaine AD sont identiques. Comment accéder à mon site externe depuis mon réseau ?
Re: Mon nom de site web public et mon nom de domaine AD sont identiques. Comment accéder à mon site externe depuis mon réseau ?
If you've named votre Active Directory `example.org` alors you cannot prevent this. You've gone against Microsft's best practices for naming an AD et you're seeing one of le symptoms.
Vous avez a peu de choices:
-
Migrate to a properly named AD. Something like `corp.example.org`.
-
Install a web server on chaque DC et configure it to forward web requests for `example.org` to `www.example.org`. Ceci est dirty et ne devrait pas be done, mais c'est an option nonetheless.
-
Train votre users to allez dans `www.example.org` internally.
J'ai blogged about AD naming best practices multiple times et link to official Microsoft sources. Vous devriez read them:
- [http://web.archive.org/web/20200214122247/http://www.mdmarra.com/2013/04/best-practices-for-configuring-new.html](http://web.archive.org/web/20200214122247/http://www.mdmarra.com/2013/04/best-practices-for-configuring-new.html)
- [http://web.archive.org/web/20191201074255/www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in-your.html](http://web.archive.org/web/20191201074255/www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in-your.html)
- [http://web.archive.org/web/20200122002118/www.mdmarra.com/2013/07/more-documentation-from-microsoft-about.html](http://web.archive.org/web/20200122002118/www.mdmarra.com/2013/07/more-documentation-from-microsoft-about.html)
If you want le short version:
>
Do pas create nouveau Active Directory forests avec le même name as an
external DNS name. Par exemple, si votre Internet DNS URL is
[http://contoso.com](http://contoso.com), you must choose a différent name for votre internal
forest to avoid future compatibility issues. That name should be
unique et unlikely for web traffic. Par exemple: corp.contoso.com.
-http://technet.microsoft.com/en-us/library/jj574166.aspx
Vous avez a peu de choices:
-
Migrate to a properly named AD. Something like `corp.example.org`.
-
Install a web server on chaque DC et configure it to forward web requests for `example.org` to `www.example.org`. Ceci est dirty et ne devrait pas be done, mais c'est an option nonetheless.
-
Train votre users to allez dans `www.example.org` internally.
J'ai blogged about AD naming best practices multiple times et link to official Microsoft sources. Vous devriez read them:
- [http://web.archive.org/web/20200214122247/http://www.mdmarra.com/2013/04/best-practices-for-configuring-new.html](http://web.archive.org/web/20200214122247/http://www.mdmarra.com/2013/04/best-practices-for-configuring-new.html)
- [http://web.archive.org/web/20191201074255/www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in-your.html](http://web.archive.org/web/20191201074255/www.mdmarra.com/2012/11/why-you-shouldnt-use-local-in-your.html)
- [http://web.archive.org/web/20200122002118/www.mdmarra.com/2013/07/more-documentation-from-microsoft-about.html](http://web.archive.org/web/20200122002118/www.mdmarra.com/2013/07/more-documentation-from-microsoft-about.html)
If you want le short version:
>
Do pas create nouveau Active Directory forests avec le même name as an
external DNS name. Par exemple, si votre Internet DNS URL is
[http://contoso.com](http://contoso.com), you must choose a différent name for votre internal
forest to avoid future compatibility issues. That name should be
unique et unlikely for web traffic. Par exemple: corp.contoso.com.
-http://technet.microsoft.com/en-us/library/jj574166.aspx