AD Problem - DC GUID won't resolve to IP

[Ya_know]

NO! You don't have to reinstall. 1) Delete the dot zone in your DNS zones 2) Make sure your machine is pointing to itself for DNS resolution 3) reboot the machine.

If you do this, a short while after reboot you'll see a) root hints populated b) the correct domain relevent DNS entries in your local domain zone c) your server will resolve any external queries. In a nutshell, the machine will configure itself it's it's pointing to itself and you delete the dot that makes it authoratative for the world.

The bold in your quote, please go into more detail there, I have a limited understanding here, and want to clear it up...

[Matridom]

The bold in your quote, please go into more detail there, I have a limited understanding here, and want to clear it up...

one of the folders in the DNS zone will be called " . " nothing else, just a dot. This means that the server thinks it owns the internet. you need to delete this so that it is no longer "authoritive" (DNS lingo for in charge of a name space). this way the server will look elsewhere for a resolution on a name if it is unable to do so itself. (like going to the TRUE " . " server.

[Ya_know]

one of the folders in the DNS zone will be called " . " nothing else, just a dot. This means that the server thinks it owns the internet. you need to delete this so that it is no longer "authoritive" (DNS lingo for in charge of a name space). this way the server will look elsewhere for a resolution on a name if it is unable to do so itself. (like going to the TRUE " . " server.

Is that the same for 2003 server? I am looking at one right now (no 2000 server here) and I don't see the entry. I have a basic understanding of what you are saying, but if asked to explain it myself I think I would come up short still, but let me try. In other words, if by chance you name you domain microsoft.com, you want internal DNS to stay internal, finding all domain resources, while anyone trying to go to microsoft.com on the web can still get there as well?.?.

[Matridom]

Is that the same for 2003 server? I am looking at one right now (no 2000 server here) and I don't see the entry. I have a basic understanding of what you are saying, but if asked to explain it myself I think I would come up short still, but let me try. In other words, if by chance you name you domain microsoft.com, you want internal DNS to stay internal, finding all domain resources, while anyone trying to go to microsoft.com on the web can still get there as well?.?.

Basicly, if you register your DNS properly into the global namespace, your server would be responsible for resolving ANY IP for ANYONE that has a .microsoft.com on the end of it.

DNS resolves backwards. so, www.microsoft.com. is what we want to resolve (notice the end of com, there is a dot, it's not a typo)

Dot is the ultimate root in DNS, it knows where .com. is, where .gov, .net, .org etc

As the dns resolved back each step, it goes to lower and lower dns servers. .com will point it to .microsoft, .microsoft will point it to www.

have the "." in the namespace makes your dns server think it's responsible for everything. so if you give it www.google.com, it looks in it's records.. does not see it, and hence gives it an unknown host error.

I've not seen the dot entry in 2k3 at all, and was only there on fresh installs of 2k. if it's there, remove it, if not, don't worry about it.

Silencio mentions it in this old thread here

http://forums.windrivers.com/showthr...DNS+server+DOT

[peterpam]

... that all you have to do is to, before running DCpromo, configure a static IP adress in your local area conection and configure thatb same ip adress as your dns server. After that run DC promo and say YES when he prompt you to create DNS server. - DONT UNPLUG YOU NETWORK CABLE! - After that just reboot and all should bee well.

BEFORE you try that, just check if your DC local area connection is pointing for his own ip adress as DNS resolver, and if so, go to RUN, CMD (command prompt) and TYPE: IPCONFIG /REGISTERDNS, followed by ENTER. Maiby thats enough.

Greetings

[NooNoo]

I did hear that there are only 5 "." dns servers officially in the world.

[confus-ed]

I did hear that there are only 5 "." dns servers officially in the world.

Surley there's only one ? I thought, that being the point of how it all works ... one machine must be top & contain the master list, there's a company responsible for all the '.com' desginations, another for all the '.uk' bits so pressumably somewhere, there's somebody or something that effectively 'owns' those designations too ?

Its a big tree & there's only one trunk !

[Matridom]

Surley there's only one ? I thought, that being the point of how it all works ... one machine must be top & contain the master list, there's a company responsible for all the '.com' desginations, another for all the '.uk' bits so pressumably somewhere, there's somebody or something that effectively 'owns' those designations too ?

Its a big tree & there's only one trunk !

Actualy, there are 13 top level DNS servers. Each dns server has those 13 listed in it's "Root hints" section. There are more then one for redundancy reasons and also load balancing reasons. As you work your way down the DNS name space to the final designation, you eventualy flip to privatly run DNS server, usualy AFTER the .com.

If you think about it, even with 13 top level servers, each still get's "hit" millions of times per day.

[confus-ed]

Actualy, there are 13 top level DNS servers. Each dns server has those 13 listed in it's "Root hints" section. There are more then one for redundancy reasons and also load balancing reasons. As you work your way down the DNS name space to the final designation, you eventualy flip to privatly run DNS server, usualy AFTER the .com.

If you think about it, even with 13 top level servers, each still get's "hit" millions of times per day.

Go on then ... since you've 'professed' to knowing this ... I'm pretty certain about my 'one trunk' remark .... lets have an explanation other than redundancy & mirroring why we have 13 & especially anyway more than 1 !

[Matridom]

Go on then ... since you've 'professed' to knowing this ... I'm pretty certain about my 'one trunk' remark .... lets have an explanation other than redundancy & mirroring why we have 13 & especially anyway more than 1 !

Unfortunatly, I was not born when DNS was invented so i did not follow the history when it developed. Other then the reasons i've giving, redundancy and load balancing, (both very valid), I'm not sure what your looking for. To properly answer your questions, i think , i would have to become a DNS historian rather then a tech who knows how the system works.

But as for .uk being a different server the .com and .net, you are correct, they ARE seperate servers. each "." in a DNS name designates a new name space in the dns structure and hence a different DNS server

Edit: After reading this throuhg, I see what Confus-ed is after.. "conceptualy" there is "one" root server where all DNS queuries start and is in essense a "pyramid" shaped structure.

[confus-ed]

Anyone else confus-ed by the 'one root' business I'm on about can get complete clarification in this link ... DNS

There's a picture which paints, I suspect if I'm involved, several thousand words & illustrates this root business, Matt's pyramids ...

[NooNoo]

There is a UK server, which is either in London or Amsterdam....depending on which day it is... and one of the US servers is in Aberdeen. there are 9 other US servers and one in Japan and 1 in Sweden.