E-Mail: webmaster@jawed.co.in
All the content/s are collected from the search engines and/or free resources. Please read disclaimer before using/downloading any content/stuffs or whatsoover.
All Logo/s,Trade Mark/s,Stuff/s,Content/s,Material/s,Software/s are property of their respective owner
For any query please contact at webmaster@jawed.co.in
All Logo/s,Trade Mark/s,Stuff/s,Content/s,Material/s,Software/s are property of their respective owner
For any query please contact at webmaster@jawed.co.in
Describe the process of working with an external domain name
If it is not possible for you to configure your internal domain as a subdomain of
your external domain, use a stand-alone internal domain. This way, your internal
and external domain names are unrelated. For example, an organization that uses
the domain name contoso.com for their external namespace uses the name
corp.internal for their internal namespace. The advantage to this approach is that
it provides you with a unique internal domain name. The disadvantage is that
this configuration requires you to manage two separate namespaces. Also, using a
stand-alone internal domain that is unrelated to your external domain might
create confusion for users because the namespaces do not reflect a relationship
between resources within and outside of your network. In addition, you might
have to register two DNS names with an Internet name authority if you want to
make the internal domain publicly accessible.
Describe the importance of DNS to AD.
When Microsoft began development on Active Directory, full compatibility with the
domain name system (DNS) was a critical priority. Active Directory was built from
the ground up not just to be fully compatible with DNS but to be so integrated with
it that one cannot exist without the other. Microsoft's direction in this case did not
just happen by chance, but because of the central role that DNS plays in Internet
name resolution and Microsoft's desire to make its product lines embrace the
Internet. While fully conforming to the standards established for DNS, Active
Directory can expand upon the standard feature set of DNS and offer some new
capabilities such as AD-Integrated DNS, which greatly eases the administration
required for DNS environments. In addition, Active Directory can easily adapt to
exist in a foreign DNS environment, such as Unix BIND, as long as the BIND
version is 8.2.x or higher. When Microsoft began development on Active Directory,
full compatibility with the domain name system (DNS) was a critical priority. Active
Directory was built from the ground up not just to be fully compatible with DNS
but to be so integrated with it that one cannot exist without the other. Microsoft's
direction in this case did not just happen by chance, but because
of the central role that DNS plays in Internet name resolution and Microsoft's
desire to make its product lines embrace the Internet. While fully conforming to the
standards established for DNS, Active Directory can expand upon the standard feature set of DNS and offer some new capabilities such as AD-Integrated DNS, which greatly eases the administration required for DNS environments. In addition, Active Directory can easily adapt to exist in a foreign DNS environment, such as Unix BIND, as long as the BIND version is 8.2.x or higher.
If it is not possible for you to configure your internal domain as a subdomain of
your external domain, use a stand-alone internal domain. This way, your internal
and external domain names are unrelated. For example, an organization that uses
the domain name contoso.com for their external namespace uses the name
corp.internal for their internal namespace. The advantage to this approach is that
it provides you with a unique internal domain name. The disadvantage is that
this configuration requires you to manage two separate namespaces. Also, using a
stand-alone internal domain that is unrelated to your external domain might
create confusion for users because the namespaces do not reflect a relationship
between resources within and outside of your network. In addition, you might
have to register two DNS names with an Internet name authority if you want to
make the internal domain publicly accessible.
Describe the importance of DNS to AD.
When Microsoft began development on Active Directory, full compatibility with the
domain name system (DNS) was a critical priority. Active Directory was built from
the ground up not just to be fully compatible with DNS but to be so integrated with
it that one cannot exist without the other. Microsoft's direction in this case did not
just happen by chance, but because of the central role that DNS plays in Internet
name resolution and Microsoft's desire to make its product lines embrace the
Internet. While fully conforming to the standards established for DNS, Active
Directory can expand upon the standard feature set of DNS and offer some new
capabilities such as AD-Integrated DNS, which greatly eases the administration
required for DNS environments. In addition, Active Directory can easily adapt to
exist in a foreign DNS environment, such as Unix BIND, as long as the BIND
version is 8.2.x or higher. When Microsoft began development on Active Directory,
full compatibility with the domain name system (DNS) was a critical priority. Active
Directory was built from the ground up not just to be fully compatible with DNS
but to be so integrated with it that one cannot exist without the other. Microsoft's
direction in this case did not just happen by chance, but because
of the central role that DNS plays in Internet name resolution and Microsoft's
desire to make its product lines embrace the Internet. While fully conforming to the
standards established for DNS, Active Directory can expand upon the standard feature set of DNS and offer some new capabilities such as AD-Integrated DNS, which greatly eases the administration required for DNS environments. In addition, Active Directory can easily adapt to exist in a foreign DNS environment, such as Unix BIND, as long as the BIND version is 8.2.x or higher.
For Question & Answer on DHCP and Its process etc. click here
For Question & Answer on IP Address,
Subnet Mask, ARP etc. click here
Subnet Mask, ARP etc. click here
For Question & Answer on DNS, DNS Zones etc. click here
For Question & Answer on DNS, DNS Zones and AD etc. click here
For Question & Answer on Windows Clustering , NLB, WINS click here
For Question & Answer on IAS & RAS, PAT, NAT, VPN click here
For Question & Answer on Domain, DC, Active Directory and its features etc. click here
For Question & Answer on LDAP,AD- Structure & Namespace etc. click here
For Question & Answer on Application Partition, DC- Backup, Sysvol etc. click here
For Question & Answer on Recovery/Restore of DC & GC etc. click here
For Question & Answer on Global Catalog, REPLMON. LDP, ADSIEDIT etc. click here
For Question & Answer on Netdom, Sites, KCC, ISTG etc. click here
For Question & Answer on FSMO and its roles etc. click here
For Question & Answer on Active Directory (AD) & its backup etc. click here
For Question & Answer on GPO, GPC and GPT etc. click here
