domains
1.Does your system has valid ip address check with Ipconfig 2.check the lan connectivity 3.check with ping whether one can ping to another system by IP or FQDN 4.check with nslookup command nslookup FQDN on cmd prompt 5.restart the dns services. 6. registerdns by ipconfig \registerdns. that shd resolve the issue
forward look up zone
A fully qualified domain name (FQDN) is the complete domain name for a specific computer, or host, on the Internet. The FQDN consists of two parts: the hostname and the domain name. Additional info: you may see an FQDN as the following parts: hostname - actual name of the device subdomain - a part of the overall domain domain - usually a company name TLD - what area of the naming convention it appears in so you could have: sales.Midwest.us.Microsoft.com as a complete FQDN, with the name 'sales' as the actual device within the Midwest/us subdomains within the Microsoft domain within the com TLD area.
FQDNA fully qualified domain name (FQDN) is the complete domain name for a specific computer, or host, on the Internet. The FQDN consists of two parts: the hostname and the domain name. For example, an FQDN for a hypothetical mail server might be mymail.somecollege.edu. The hostname is mymail, and the host is located within the domain somecollege.edu.PQDNIf a label is not terminated by a null string, it is called a partially qualified domain name (PQDN). A PQDN starts from a node, but it does not reach the root. It is used when the name to be resolved belongs to the same site as the client. Here the resolver can supply the missing part, called suffix, to create an FQDN.
PQDN is Partially Qualified Domain Name FQDN is Fully Qualified Domain Name.
The issues which comes up if dns is not working nslookup(forward and reverse) result failure cannot connect to any machines. cannot resolve Ip to FQDN and vice versa
Fully Qualified Domain Name
if the preferred dns server is blank then the system takes dns as the host server and try to resolve the entries from its own cache if it is able to do it then finew other wise it will show dns error on the IE page. same thing happens with the resources if its in the cache it will resolve the FQDN to IP othere wise will give error
DNS suffix
Try Ping or Tracert using a FQDN as the target instead of an IP address. Both will do a DNS lookup before performing the ping or tracert.
The issues which comes up if dns is not working nslookup(forward and reverse) result failure cannot connect to any machines. cannot resolve Ip to FQDN and vice versa and one is not geeting internet pages alos if system connected to network
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.