dns cached lookup "." folder

[dpsmith]

what's the purpose of the "." folder in the cached lookup section of DNS?

it's full of website info.
but the strange thing is this is the only DC on the network and no one can use it to surf and internet access for everyone on the network is through a firewall.
(the DC is locked and only i use it so i know no-one is hopping on)

how is it getting the users on the network's website info?

tia

 

[grshpr]

the "." entry in DNS means that your DC is a root zone server. A root zone is the top level for lookup of domain names on the internet. There are 2 reasons to have a root zone:
1. Your intranet is not connected to the internet
2. Your organizations is connected to the internet through a proxy server.

 

[dpsmith]

how do i stop it from being a root zone?
i currently have have everything forwarded to my ISP.

(this might be the cause of my endless event id# 7062)

 

[grshpr]

To delete a root zone, you open up DNS snap-ip, then expand your domain, and forward look-up zones. You will find the "." there. To delete that root zone, simply right-click the "." and select delete.

I would recommend writing down any settings that are on the tabs in your root zone before you delete it so that if you have to put it back you know the settings.

Are you part of a larger company, or are you it?
What are you using for your firewall, a hardware firewall like a Cisco box, or a Windows server such as proxy server?

 

[GlenJohnson]

Also, make sure you've got a good backup before trying something like this. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"Patience is more powerful than force."
Plutarch (46-125 A.D.);

 

[dpsmith]

it's funny, when i first started to research the event ID# 7062 one of the first things i did was delet the "." in the forward lookup zone.
it's been gone for over a year.

we're a small company with a sonicwall firewall.
only 1 Domain Controller acting as a DNS/AD/DHCP.

i followed some advise found on another post and from nslookup i ran ls -t mydomain.com and got 5 name servers.

is this a problem?

 

[GlenJohnson]

Why don't you post the results? Did you nslookup and route print also just to look at the overall picture? Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"Patience is more powerful than force."
Plutarch (46-125 A.D.);

 

[FilthPig]

This thread has gone wild. You are on the wrong track.

Whenever your DNS server performs a lookup, it caches that information so that the next time that same address needs to be looked up, it already has the answer (there is an expiration, but I'll try to keep this simple). The DNS server stores these caches in a way that matches the FQDN (fully qualified domain name) hierarchy: in order to find

http://www.website.com,

the server must first ask the "." or "root" server where to look for ".com". It then asks the ".com" DNS server (you undoubtedly have a subfolder named ".com" with several subfolders) where to look for "website.com". Once it finds that out, it asks the DNS server hosting records for "website.com" where it can find the host "

http://www.website.com",

and it stores all this information for a time to speed up the query on the likely chance that somebody may make it again. Marc Creviere