AD Problem - DC GUID won't resolve to IP

Printable View

January 14th, 2004, 05:01 PM
techleet

AD Problem - DC GUID won't resolve to IP

I just ran dcdiag on a new Win2K Server installation and got the following error:

Testing server: Default-First-Site-Name\TECHSERV
Starting test: Connectivity
TECHSERV's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(1b5585cb-b2cf-4335-a5fd-891d42XXXXXX._msdcs.DOMAIN.com) couldn't be resolved, the server name (techserv.techleet.com) resolved to the IP address (63.200.XXX.XXX) and was pingable. Check that the IP address is registered correctly with the DNS server.
......................... TECHSERV failed test Connectivity

Any ideas? I have no idea what I'm doing :)

I knew NT4 Server, but Win2K is a bit different :)

I installed DNS and configured it without reverse lookups, but I'm not sure if I even did THAT right. I'm slippin!

Any ideas? Thanks!
January 14th, 2004, 09:55 PM
TripleRLtd

Quote:

Originally Posted by techleet

I just ran dcdiag on a new Win2K Server installation and got the following error:

Testing server: Default-First-Site-Name\TECHSERV
Starting test: Connectivity
TECHSERV's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(1b5585cb-b2cf-4335-a5fd-891d42XXXXXX._msdcs.DOMAIN.com) couldn't be resolved, the server name (techserv.techleet.com) resolved to the IP address (63.200.XXX.XXX) and was pingable. Check that the IP address is registered correctly with the DNS server.
......................... TECHSERV failed test Connectivity

Any ideas? I have no idea what I'm doing :)

I knew NT4 Server, but Win2K is a bit different :)

I installed DNS and configured it without reverse lookups, but I'm not sure if I even did THAT right. I'm slippin!

Any ideas? Thanks!

Come on techleet, you know what you're doing. All you need is more XP with 2kServer. Is the server working? Are all domain compuirters communicating? What are your particular problems, not just an error message...which as you've noticed, can be quite cryptic. Post more details on your situation. https://forums.windrivers.com/images.../2006/04/1.gif

EDITED BY DAMNED ANGEL
January 14th, 2004, 10:11 PM
Matridom

Now, techleet, what i would recommend doing is to delete your DNS zones and rebuild them, however make sure you set them as AD integrated. Be sure to create the reverse DNS lookup zone. Once that is done, create the proper A record and Pointer record for the domain controller. One record needs to be created for each IP address that the server has. Hopefully that should help sort things out.

EDITED BY DAMNED ANGEL
January 15th, 2004, 12:09 AM
silencio

It sounds like you don't have either a) DNS running on a DC in AD mode b) your DC techserv isn't using the correct DNS resolver (in your tcp/ip settings) c) you've deleted some entries in the DNS zone.

DNS on 2000/03 need the following entries under the DNS zone:

https://forums.windrivers.com/

I'll bet you $100 your missing some of the above entries in your DNS zone.
January 15th, 2004, 07:22 AM
confus-ed

Quote:

Originally Posted by TripleRLtd

EDITED BY DAMNED ANGEL

I'm absolutely certain this won't help at all BUT ..... Ooooo-ooo ! I think that's a first.
January 15th, 2004, 09:05 AM
Ya_know

Quote:

Originally Posted by confus-ed

I'm absolutely certain this won't help at all BUT ..... Ooooo-ooo ! I think that's a first.

And what exactly was taken out???
January 15th, 2004, 10:27 AM
Cleetus

No one ever told me DNS could get so brutal that it would have to get edited before I could read it. :rolleyes:
January 15th, 2004, 11:51 AM
silencio

The M in MX record is for 1000. The X is for X-Rated.

DNS is filthy.
January 15th, 2004, 02:44 PM
techleet

Quote:

Originally Posted by silencio

The M in MX record is for 1000. The X is for X-Rated.

DNS is filthy.

HAHAHAHAHAHA :D
January 15th, 2004, 02:56 PM
techleet

Ok, well I reinstalled Win2k Server -- again.

Now this time I kept the network cable unplugged, just in case msblast.exe decided to pay me a visit and ruin my party.

So I'm doing a clean install as we speak (er...type). During initial install, I told it to stay in a workgroup, not join a domain (no domain to join anyway).

Ya know, I should explain this better. Here's some background:

I have 2 machines on my network. One is WinXP Pro and the other is WinME. (Don't laugh). This Win2K Server is going to be used for Exchange 2003 /w OWA. Since there are no other servers on the network, the server has to be a DC for a new domain (so exchange will run), has to have Active Directory (ditto) and be a DNS server (so AD will run). Yes, the server has a static IP.

Ok, so now we know where I'm going, but how the hell do I get there? LOL

Questions:

- I seem to recall DCPROMO.EXE automatically installing/configuring DNS for me when I promoted the server to DC and it couldn't find a dns server on the network. Am I trippin? Do I have to manually create ghetto zones? Can I just create a caching dns and walk away? Doesn't AD create the dns entries it needs when you install it? wft? :)

- Why is Win2K infinitely more complicated/bloated than NT4? This is jacked.

- Do you even NEED Active Directory installed for Exchange 2003 to work?

- I'm going to change my alias to Techweak.

- Help. Somebody point me to a Win2K Server/AD HOWTO For Dummies website.

Thanks!
January 15th, 2004, 03:00 PM
Ya_know

Did you forget to point the server to itself as the prefered DNS server in the network properties? Could it be that simple? Of course, DNS installed correctly is important to...

And you are using a static IP as well...right?
January 15th, 2004, 03:25 PM
NooNoo

Quote:

Originally Posted by techleet

- Do you even NEED Active Directory installed for Exchange 2003 to work?

- I'm going to change my alias to Techweak.

- Help. Somebody point me to a Win2K Server/AD HOWTO For Dummies website.

Thanks!

2k server has some very nice walkthroughs - if you bring up the "configure my server" window, there are links to the walkthroughs further down the page. The links point to the help files - this is not online.
January 15th, 2004, 08:17 PM
TNR

This link should help you through most of a W2k Server DC setup

http://www.microsoft.com/technet/tre...o/depprof1.asp

For W2k server to become a DC

DNS must be install and the services running. DNS does not have to be configured, but the server does need to point to itself for DNS. DCPromo.exe will configure DNS for you when you decide on an Active Directory name. DNS can be configured before you run DCPromo, but it will set it up if it isn't. DNS will use Root Hint servers by default, unless you specify DNS Forwarders. DNS should work fine with just the Root Hints, but I have run into issues with only using Root Hints before. You shouldn't have a problem though.

If you want to run Exchange 2000/2003, Active Directory must be running on a domain controller. The Exchange setup will not run if it cannot find an Active Directory. Normally Exchange is installed on a member server in a w2k/w2k3 AD domain. It looks like you only have one server and this shouldn't be a problem.
January 15th, 2004, 08:38 PM
techleet

Quote:

Originally Posted by TNR

DNS must be install and the services running. DNS does not have to be configured, but the server does need to point to itself for DNS. DCPromo.exe will configure DNS for you when you decide on an Active Directory name. DNS can be configured before you run DCPromo, but it will set it up if it isn't. DNS will use Root Hint servers by default, unless you specify DNS Forwarders. DNS should work fine with just the Root Hints, but I have run into issues with only using Root Hints before. You shouldn't have a problem though.

Thanks for the advice!
I checked my dns server setup (I let dcpromo install/configure it) and it says Root Hints are not required because the server is setup as a Root Server. I cannot use forwarders (which I need) because, again, it is setup as a Root Server. Is there a way around this?

My server was not pointing to itself for preferred dns, it was pointing to my ISPs dns. I have changed it to point to itself now. I assume i'm going to have to demote server, uninstall DNS and AD and reinstall it all. Correct? Or if there's a way to fix the DNS without reading 800 pages of the help file...?

Thanks for any and all input! :D
January 15th, 2004, 08:52 PM
silencio

Quote:

Originally Posted by techleet

My server was not pointing to itself for preferred dns, it was pointing to my ISPs dns. I have changed it to point to itself now. I assume i'm going to have to demote server, uninstall DNS and AD and reinstall it all. Correct? Or if there's a way to fix the DNS without reading 800 pages of the help file...?

Thanks for any and all input! :D

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.
January 16th, 2004, 09:26 AM
Ya_know

Quote:

Originally Posted by silencio

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...
January 16th, 2004, 09:29 AM
Matridom

Quote:

Originally Posted by Ya_know

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.
January 16th, 2004, 10:13 AM
Ya_know

Quote:

Originally Posted by Matridom

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?.?.
January 16th, 2004, 10:22 AM
Matridom

Quote:

Originally Posted by Ya_know

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
January 16th, 2004, 12:11 PM
peterpam

I am absolutely certain...

... 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
January 16th, 2004, 02:43 PM
NooNoo

I did hear that there are only 5 "." dns servers officially in the world.
January 17th, 2004, 03:56 AM
confus-ed

Quote:

Originally Posted by NooNoo

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 !
January 17th, 2004, 08:00 AM
Matridom

Quote:

Originally Posted by confus-ed

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.
January 17th, 2004, 08:26 AM
confus-ed

Quote:

Originally Posted by Matridom

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 :D ... 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 !
January 17th, 2004, 08:47 AM
Matridom

Quote:

Originally Posted by confus-ed

Go on then ... since you've 'professed' to knowing this :D ... 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.
January 17th, 2004, 09:58 AM
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 :D & illustrates this root business, Matt's pyramids ... ;)
January 17th, 2004, 05:50 PM
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.

All times are GMT -5. The time now is 07:48 AM.