nslookup problem

Microsoft Windows server v2003 r2 standa...
February 12, 2010 at 05:52:46
Specs: Windows 2003
Hi,

I've a problem with the DNS resolution.
Every time I make a nslookup in a workstation it gives me a different name for a static IP address (DHCP configuration).
Any idea to resolve this problem?

Thanks,

seb


See More: nslookup problem

Report •

#1
February 12, 2010 at 06:44:22
what does "static IP address (DHCP configuration)." mean? IP reservation?

Please provide the output from a nslookup in question and a ping -a to this static ip


Report •

#2
February 12, 2010 at 07:20:15
Sorry I redifine my question :

Hi,

I've a problem with the DNS resolution.
Every time I make a nslookup of a client of the domain from my workstation it gives me a different name (DHCP configuration).
f.ie . : 1/ nslookup x.x.x.x -> result laptop-client-3
2/ nslookup x.x.x.x -> result laptop-client-14
Any idea to resolve this problem?

Thanks,

seb

Is it clearer?

seb


Report •

#3
February 12, 2010 at 08:04:49
Please provide the output from a nslookup in question and a ping -a to this ip.

Also provide a ipconfig /all from your workstation for review. Thanks


Report •

Related Solutions

#4
February 12, 2010 at 10:34:00
Here is an output of the nslookup :

C:\Users\Sébastien>nslookup 10.0.1.33
Serveur : newsat-sion.newsatg.local
Address: 10.0.1.9

Nom : pc-sion.newsat.local
Address: 10.0.1.33


C:\Users\Sébastien>nslookup 10.0.1.33
Serveur : newsat-sion.newsatg.local
Address: 10.0.1.9

Nom : telecal
Address: 10.0.1.33


C:\Users\Sébastien>nslookup 10.0.1.33
Serveur : newsat-sion.newsatg.local
Address: 10.0.1.9

Nom : lap-sion-4.newsat.local
Address: 10.0.1.33

This makes for all workstations those are managed by DHCP but not with static IP address (there is like a loopback).

For the ping and the ipconfig /all the workstation is unfortunately switched off and I'm away from work...

Thanks,

seb


Report •

#5
February 12, 2010 at 11:24:23
2003 server doing the dhcp?

Report •

#6
February 12, 2010 at 12:01:10
yes, it's 2003 doing the DHCP


Report •

#7
February 12, 2010 at 13:48:05
at workstation 10.0.1.9 do an ipconfig /all and post the results

Report •

#8
February 13, 2010 at 14:19:39
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : newsat-sion
Primary Dns Suffix . . . . . . . : newsatg.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : newsatg.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DC Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 00-16-76-D0-2A-06
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 10.0.1.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.249
DNS Servers . . . . . . . . . . . : 10.0.1.9
212.147.10.180
212.147.10.10


Report •

#9
February 13, 2010 at 15:36:52
From your last post

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 10.0.1.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0

You are manually assigning multiple ips to the same pc/nic.

Compound this with the nslookups it appears you are also assigning the same ips dynamically via dhcp server.

Normally your ip plan looks something like this;
192.168.1.1-19 is the range for static ips
192.168.1.20-200 is your dhcp scope
192.168.1.201-254 available

It appears you have a dhcp scope which includes the ip addresses you assigned statically. If the server dhcp is set to auto update dns you will get one ip address assigned to two pcs, one via dhcp and one via your static assignment. Add to that any ips that are cached due to broadcasts.

When you assign a ip statically you usually enter the host and ptr records in DNS manually


Report •

#10
February 15, 2010 at 08:22:26
Thanks, I understand but in practice what do I have to do?
I'm a little novice...

Report •

#11
February 15, 2010 at 09:41:37
Start by removing all static tcp/ip entries in the clients and set them to "automatically assigned" since you have a dhcp server.

Then you go in and clean up the dns host/ptr entries that are incorrect.


Report •

Ask Question