NSLOOKUP Messed up DNS

[ftoddt]

Hello,
I was reading the thread950-663132
I am having logon problems with XP Pro to a Win2K Server LAN taking over 30 minutes. Win2k clients have no problem. I have two Domain Controllers and they both have DNS and they talk between them. When I do a nslookup in the cmd window on the XP computer, I get
Server: servername.edu (will use servername for domain)
Address: 169.254.1.101

*** servername.edu can't find nslookup: Non-existent domain.

I am also logged onto the XP locally because it takes so long to go via the LAN. I can ping the two domain controllers. Any ideas?
Thanks

 

[GlenJohnson]

Good luck. (People thought ME was here to stay also. My os of choice is and always will be W2K.) I'll keep checking to see if I can find a fix or at least something that might help. I'm sure others will be out there working to help you also.



Glen A. Johnson
"Fall seven times, stand up eight."
Proverb

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[ricpinto]

Can you add your DNS name and its IP address to your hosts file (C:\winnt\system32\drivers\etc)to all the affected PC, edit it using notepad.

 

[wbg34]

Ftoddt,
Can you post an ipconfig /all from a workstation and one from you dns server pls.

 

[ftoddt]

wbg34
You bet I can. I will try and do it tomorrow but I may not be able to do so until maybe Friday at the earliest. You want one ipconfig/all from the dns server and one from the troubled xp client, right?
Ricpinto,
You have lost me with the host file in the System 32
driver folder. Is that the lmhost file there or the host file or both. I see them in my work computer but they look like samples. Can you show me an example of how it should look..
Thanks Guys

 

[ricpinto]

Edit your hosts file only, enter your dnsname(FQDN) and its ip address.

Example.

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
# Assuming below is your DNS and it's ipaddress, similar to the result on ipconfig/all.
169.254.1.2 servername.edu

 

[ftoddt]

Ok,
Let me see if I have this right with some real type entries. I would type the following?

# 169.254.1.2 wsd-dc.domain.edu # dns server
# 169.254.1.101 wsd-bc.domain.edu # 2nd dns server
# 169.254.1.153 103-2-2k.domain.edu # x client host

The above are the exact names and ips. The computer names are wsd-dc, wsd-bc, and 103-2-2k.
So is this how it would look in a host file and I would write it in notepad and save it as a host file..?

 

[ricpinto]

Yes, try it. What's your domain name? What's the domain name when your press ctl-alt-del in the login screen?

 

[ftoddt]

It is really long so I just substituted domain.name. The full domain name is internal.waterville.wednet.edu. So the one of the domain controllers is call
wsd-dc.internal.waterville.wednet.edu.
I have to accept the wednet.edu from the school ISP system. I am not sure why the previous IT made added the internal. We could of just stayed with waterville.wednet.edu... I may change it later. Makes email addresses really long. From what I can tell one cannot shorten the email address any shorter than the domain name..with mx alias etc in exchange...

 

[ricpinto]

One reason of your DNS error messages is that they have so many zones (wsd-dc.internal.waterville.wednet.edu) it's complicated to configure your DNS this way.. for best practice read on.

http://www.microsoft.com/technet/prodtechnol/ad/windows2000/plan/bpaddsgn.asp?frame=true#g

or Google for AD design, computer naming etc.

Also the way they choose internal IP addressing scheme is arguable, you use APIPA.

I know you just inherit this mess but if you have the power to change then do so.

 

[ftoddt]

ricpinto,
I could shorten the name. I believe that the domain name when it was nt was just wsd.wednet.edu. which is considerably shorter than after the w-2k upgrade to internal.waterville.wednet.edu. Only shorter by one word but the words aren't so long. I can't get it any shorter than three words in that I have no control over the wednet.edu. and must use them. So my domain controller will be a minimum of 4 segments or words. Would be a lot of work changing the public dns and private dns records not to mentions isa server, dhcp, reconfiguring all the client computers, printers etc. etc. to save one word. except I could make them much shorter.
Todd

 

[ricpinto]

Don't change the names yet, you have to find out first why they do it that way.. like why there's an internal. Check the the following: your zone transfers, forwarders, root hints. Most probably something is wrong with your DNS coz of the XP slow logins. What's the result of editing the host files, remember to include also all your DNS servers and domain servers here.

.wednet.edu
/ . waterville.wednet.edu
. internal.waterville.wednet.edu ???
. wsd-dc.internal.waterville.wednet.edu

 

[ftoddt]

Ok, not sure what you have done by this:
.wednet.edu
/ . waterville.wednet.edu
. internal.waterville.wednet.edu ???
. wsd-dc.internal.waterville.wednet.edu

If what you are showing me above is the tree, then you have it perfectly except you could put edu by itself at the top.
As you know, the nationwide school system is .edu Depending on the size of the administation that supports the various schools in the area, ours is called wednet. Therefore I am committed to wednet.edu In our area there are many different school districts. Mine is Waterville. Therefore our IP is waterville.wednet.edu and we are given a number of public ip addresses. Now I think the first name was not waterville but rather wsd.wednet.edu. But whoever did our upgrade to Win2k changed it to internal.waterville instead of just leaving it wsd.
I think it works alot like the government that I work for. My email address is
Forrest.T.Trantham @nws02/usace.army.mil. The only thing that applies to me in that addres is nws which is my district.

 

[ftoddt]

Ok here is the ipconfig/all from domain controller and xp client.

Domain controller wsd-dc

Windows 200 IP Configuration
Host Name ..........:wsd-dc
Primary DNS Suffix..:internal.waterville.wednet.edu
Node Type...........:Broadcast
IP Routing Enabled..:No
WINS Proxy Enabled..:No
DNS Suffix Search List..:internal.waterville.wednet.edu
waterville.wednet.edu
wednet.edu

Ethernet adapter Local Area Connection:

Connection specific DNS Suffix..:
Description...:Netelligent 10/100TX PCI Embedded UTP/AUI Controller
Physcial Address...........00-08-C7-4F-FC-89
DHCP Enabled............:No
IP Address..............:169.254.1.2
Subnet Mask.............:255.255.254.0
Default Gateway.........:169.254.1.1
DNS Server..............:169.254.1.2


XP Client: Computer name Kims

Windows 200 IP Configuration
Host Name ..........:Kims
Primary DNS Suffix..:internal.waterville.wednet.edu
Node Type...........:Broadcast
IP Routing Enabled..:No
WINS Proxy Enabled..:No
DNS Suffix Search List..:internal.waterville.wednet.edu
waterville.wednet.edu
wednet.edu

Ethernet adapter Local Area Connection:

Connection specific DNS Suffix..:
Description...:Netelligent 10/100TX PCI Embedded UTP/AUI Controller
Physcial Address...........00-07-E9-D9-91-C3
DHCP Enabled............:Yes
IP Address..............:169.254.1.125
Subnet Mask.............:255.255.254.0
Default Gateway.........:169.254.1.1
DNS Server..............:169.254.1.101
169.254.1.2
Leased Obtained.......Saturday Jan 31, 2004 11:04:14
Leased Expires........Sunday February 08, 11:0414

Thats what it shows. What I find interesting is DHCP enabled in on the client and not the domain controller. I may also have another lead on the XP slow logon. Seems to be working well today if my proximity is real close. I am wondering how much delay I am getting into with many diffenerent brand name hub/switches and some of these clients go thru at least 2 to get to the dns server.
Thanks for your help all.
Todd

 

[wbg34]

Ftoddt,
What is serving your DHCP. You need to alter that so that 169.254.1.2 is your primary dns server. For now leave the secondary dns server blank.
You do not want dhcp enabled on your server's Network card. It is best to leave them as static IP's. Make sure that your reserve them in your DHCP though.

 

[ftoddt]

wbg34,
The DHCP server is the same as one of the DNS servers.
wsd-dc is our primary domain controller and has both DHCP and DNS.
wsd-bc is our backup domain controler and only has DNS.

It is my understanding that in Win2K that all domain controllers are suppose to be somewhat equal. I may have configured the client to look for the wsd-bc first and the wsd-dc second. That would be an easy fix if you think it is necessary.
So you also think that it would be best to make all the existing clients static ip's and make reservations for all 175 of them or maybe just the 30 XP clients. In fact, I did make a reservation for that particular XP client above in DHCP but did not make it static at the client computer. I will experiment with that. Thanks

 

[wbg34]

So you also think that it would be best to make all the existing clients static ip's and make reservations for all 175 of them
No do not do that!!!!
My response was in regards to your question
What I find interesting is DHCP enabled in on the client and not the domain controller.
You do not want DHCP enabled on your servers LAN connection.

 

[wbg34]

Is 169.254.1.101 your BDC?
Can you post an Ipconfig /all from that server.

 

[ftoddt]

Thanks for clarifying. All servers have been given staic IPs and reservations in DHCP. I got to thinking about that curiosity comment that I made earlier and I didn't think it through. I knew they were static and certainly would not want DHCP reassigning servers new addresses. Thanks for catching that.
Todd