DNS and Namespace Servers

Discussion in 'File Systems' started by Nordic, Aug 28, 2006.

  1. Nordic

    Nordic Guest


    I have a W2k3 R2 domain. I have just begun deploying an integrated namespace
    using DFS-R. Several users report being unable to access certain parts of the
    namespace. For example, some users browse to \\company.com and only see
    NETLOGON and SYSVOL. It seems that only those who are pointing directly to a
    DFS Nameserver as their primary DNS server see the entire namespace.

    Is this by design? Do I need to make every DNS server a namespace server?


    Nordic, Aug 28, 2006
    1. Advertisements

  2. This is by design. Users should be going to \\company.com\root to see the
    contents of the namespace.
    Jill Zoeller [MSFT], Aug 28, 2006
    1. Advertisements

  3. Nordic

    Nordic Guest

    Thanks for the fast response, Jill.

    So do you mean that the intention is to have users go explicitly to
    \\company.com\data or \\company.com\Installers rather than going to
    \\company.com and seeing data and installers? Some users _do_ see all of the
    roots when they go to \\company.com.

    Is my assesment of the DNS server placement correct? That is, if someone points
    to a DNS server that is also a namespace server, will they see all of the roots?

    Thanks, again.

    Nordic, Aug 28, 2006
  4. Hi,

    Yes, the intention is for users to browse the actual namespace,
    \\company.com\data or \\company.com\installers. DFS wasn't designed so that
    you could just go to \\company.com and see all the roots in the domain.

    Now, I'm not sure if the DNS issue is the real reason why this is working.
    As I understand the issue, if you host a namespace root on a DC, and you go
    to \\company.com and happen to be directed to the DC that hosts a root, then
    yes, you'll see the various roots hosted on that DC. If \\company.com takes
    you to a DC that doesn't host a root, then you won't see any roots.

    I hope this makes sense!

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Want to learn more about Windows Server file and storage technologies? Visit
    our team blog at http://blogs.technet.com/filecab/default.aspx.
    Jill Zoeller [MSFT], Aug 28, 2006
  5. Nordic

    Nordic Guest

    Ok. That makes sense. I will keep an eye on it. Thanks.
    Nordic, Aug 28, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.