0
The first DC in the domain.
Wiki User
∙ 14y ago
Add your answer:
Earn +20 pts
Locations of root domain server in India?
In inda there is a root server in Chennai. It is the Root server for total Asia..
What is the root server of dns?
Them root server in general is . .com,.org etc but in your domain the first dc in the forest/domain is the one
How many root servers control the overall Domain Name Server lookup process for the entire Internet?
13
What is the purpose of a root server in DNS?
If a DNS server cannot find the answer to the DNS Query in its own database it will first query the forwarders (if there are any configured) and then ask the root server. root servers (by default) are the master DNS servers of the Internet. The are called A, B, C, ... These are the highest level of the DNS hierarchy. Ultimately, any DNS request that can't be solved at a lower level (through the use of a cache) is traced back to those 13 root servers. Them root server in general is . .com,.org etc but in your domain the first dc in the forest/domain is the one
Can a windows domain environment not connected to the internet still need a dns root server?
yes a windows domain enviorment not connected to the internet still need a dns root server because to access the resources(i.e computers, printers) we need IP and FQDN The role of DNS server is to provide that info and convert IP to FQDN and vice versa.
How would a mail server on the internet locate the mail server?
Whenever mail servers talk to each other, they look for MX records at the destination's DNS. When a DNS server is setup for a domain and that domain has mail capabilities, their DNS server will have at least one MX record to denote which server handles mail. The root DNS servers for the internet denote the addresses for the SOA (start of authority) DNS servers for a particular domain.
What is the difference between Child Domian and Tree Domain?
A child domain is a member of a domain tree, but is not the root of the tree. The domain tree is the root of the tree.
What is the first domain installed in a new active directory forest called?
Forest root domain
Difference between domain DFS and stand alone DFS in windows 2k?
Stand-alone DFS Namespace In a stand-alone DFS namespace, the path to access the root or a link starts with the root server name. The stand-alone DFS root can comprise of a single root target. Therefore, these are not fault tolerant. When the root target is not available, you cannot access the complete DFS namespace. You can enable fault tolerance on a stand-alone DFS namespace by creating these namespaces on a cluster of servers. A stand-alone DFS namespace has its configuration information stored in the local registry of eth root server. Domain-based DFS Namespace In a domain-based DFS namespace, the path to access the root or a link starts with the domain name of the host. The domain-based DFS root can comprise of single or multiple root targets that enables fault tolerance and load sharing. A domain-based DFS namespace has its configuration information stored in the Active Directory. Exemple : • \\DomainName\RootName: This is the format of the namespace when you select the Domain-based DFS namespace type. • \\ServerName\RootName: This is the format of the namespace when you select the Stand-alone DFS namespace type.
Which commmand is used to find DNS server's information about a domain name?
Find All Name Servers GOALS: Find every name server that may be authoritative for your domain. Make sure that all are authoritative, and that WHOIS has a list of all of them (and no others). BACKGROUND: Every domain name is required to have a primary nameserver (only one), and at least one secondary nameserver. This is to help ensure that all domains are reachable. For example, if you have 3 separate offices, and one of them suffers a disaster, that shouldn't prevent people from being able to reach the other two offices. The WHOIS database lists all the authoritative nameservers (ones that get updated automatically when you make changes) for your domain. This list gets sent to the root server for your Top Level Domain (such as .com). Anyone in the world trying to reach your domain will get that list, and go to one of the nameservers to resolve a subdomain within your domain. Step 2a: Find out what the root servers think your nameservers are To do this, you will need to use a program that can generate DNS requests (such as NSLOOKUP on Windows or DIG). My favorite program for this is Sam Spade. Or, you can go to a web site that allows these requests, such as http://www.samspade.org/. First, find the primary root server for your Top Level Domain (such as .com if you have the domain example.com). With NSLOOKUP, you can type "set type=NS" (to get the NS, or nameserver, records) and then enter your top level domain ("com" or "uk" or whatever). You will get a list of root nameservers. Type "server " followed by the first nameserver in the list (for example, "server a.root-servers.net"). Then, enter your domain name ("example.com"). Now, you will have a list of servers that the root servers think are authoritative for your domain. With DIG, enter your top level domain ("com") as the domain to look up (or type "dig com@default.dnsserver" where "default.dnsserver" is your normal DNS server). Look at the "NS" entries in the results, and take the top one, and enter it as the nameserver to use. Then, as the domain to look up, enter your domain name (or, type "dig example.com@a.root-servers.net", where your domain goes before the "@" and the root server goes after the "@"). This should just return the name servers for your domain, but make sure just to look at entries with " NS " in them. Problem? If there are any nameservers listed here that are NOT listed in WHOIS, or there are any nameservers listed in WHOIS that are NOT listed here, there is a problem. Contact the company that gave you your domain name for help. Add these to your list of nameservers from WHOIS that you got in Step 1. Step 2b: Find out what your name servers say your nameservers are For this step, do exactly what you did in Step 2a, except this time use the first one of the name servers you have written down as the DNS server to use, and use your domain name as the domain to look up. Using NSLOOKUP, type "server nameserver.example.com" (where nameserver.example.com is the first name server on the list you wrote down), then "set type=ns", and then enter your domain name. If there are any name servers listed here that are not on your list, add them to the list. Or, using DIG, enter the first name server you wrote down as the name server to use, and then your domain name as the domain to look up. Or, from the command line, type "dig example.com@nameserver.example.com". If there are any name servers listed here that are not on your list, add them to the list (only look at entries with " NS " in them). Problem? If any name server you check here returns a name server that was NOT listed in WHOIS, it is called a "missing nameserver", and is an error. If the name server listed is authoritative for your domain (see steps below), it MUST (RFC882 p.25) be added to the WHOIS listing. If it is NOT authoritative for your domain, it MUST be taken out of the nameserver it was listed in. Problem? If any name server you check here does NOT return one of the name servers listed in WHOIS, there is a problem. If the name server listed in WHOIS IS authoritative for your domain (see steps below), it MUST be added to your nameservers. If it is NOT authoritative, it MUST be taken out of WHOIS (but you MUST have at least 2 nameservers listed in there). Repeat this step for EVERY name server on your list -- even ones you may have just added. Step 2c: Test every name server You need to make sure that every name server on your list is authoritative for your domain. With DIG, use the first name server on your list as the domain server to use, and enter your domain name as the domain to look up (or, from the command line, type "dig example.com@nameserver.example.com"). You should see "Authoritative answer" (or something similar) if it is authoritative, or "Non-authoritative answer" if it is not. Problem? If the name server is NOT authoritative for your domain, you have a "lame delegation." If this server is not authoritative, and it is listed as an NS record in your domain (step 2b), it MUST be taken out. If this server is not authoritative, and it is listed in WHOIS, it MUST be taken out (but, you MUST also have at least 2 name servers listed in WHOIS). Step 2d: Sanity Checks * You MUST have ONLY ONE primary nameserver. You will check this later in the step for SOA (Start of Authority) records, where the primary server is listed. * You MUST have AT LEAST ONE secondary nameserver. That means that WHOIS, the root servers, and all your name servers MUST list at least two name servers that are authoritative for your domain. You may have more than one secondary nameserver (4 to 7 SHOULD be the maximum). * Your secondary nameserver(s) MUST get their information directly from your primary nameserver, and check it periodically (how often is based on the SOA record fields) for updates.
What is the use of root domains?
I have a domain DomainA.com and X.DomainA.com is it consider a single domain or multiple domain?
What could cause the Forwarders and Root Hints to be grayed out?
Win2K configured your DNS server as a private root server
