|
-
January 14th, 2004, 05:01 PM
#1
Registered User
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!
DON'T PANIC

-
January 14th, 2004, 09:55 PM
#2
Banned
 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. 
EDITED BY DAMNED ANGEL
Last edited by Damned Angel; January 15th, 2004 at 12:19 AM.
-
January 14th, 2004, 10:11 PM
#3
Chat Operator
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
Last edited by Damned Angel; January 15th, 2004 at 12:18 AM.
-
January 15th, 2004, 07:22 AM
#4
Geezer
 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
#5
Banned
 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
#6
No one ever told me DNS could get so brutal that it would have to get edited before I could read it.
-
January 15th, 2004, 11:51 AM
#7
Registered User
The M in MX record is for 1000. The X is for X-Rated.
DNS is filthy.
-
January 15th, 2004, 12:09 AM
#8
Registered User
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:

I'll bet you $100 your missing some of the above entries in your DNS zone.
-
January 16th, 2004, 12:11 PM
#9
Registered User
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
#10
Driver Terrier
I did hear that there are only 5 "." dns servers officially in the world.
-
January 17th, 2004, 03:56 AM
#11
Geezer
 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
#12
Chat Operator
 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.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks