jskfan
asked on
windows 2000 DNS Records
I would like to know in which situations Windows DNS gets 2 records for the same client machine(XP)? and how to avoid this to happen?
thanks
thanks
Workstation is configured to register it's connection in DNS (look at tcp/ip properties, advanced). It's DHCP lease expires, and it gets a new address.
ASKER
I understand,
but I have 2 xp clients now that have the same IPs, the same DNS records
but I have 2 xp clients now that have the same IPs, the same DNS records
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
how do you solve this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The DHCP issue can be resolved by enabling conflict detection, which causes the DHCP server verify the address isn’t in use before issuing it.
Start the DHCP MMC
Right click your DHCP server, Properties
Advanced tab
Increase "Conflict detection attempts" from 0 (default) to 1.
Start the DHCP MMC
Right click your DHCP server, Properties
Advanced tab
Increase "Conflict detection attempts" from 0 (default) to 1.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
workstations are good, when I run ipconfig /release the renew they get a proper IP address.
example computer1 : 122.1.1.40 but in DNS it's 122.1.1.10
computer2: 122.1.1.10 and in DNS it's 122.1.1.10 (this one is correct)
do I have to manually delete the A record? and this happens to many of the workstations.
I checked aging and scavanging and it set up to its default.
I don't know how to solve and prevent this problem to happen.
example computer1 : 122.1.1.40 but in DNS it's 122.1.1.10
computer2: 122.1.1.10 and in DNS it's 122.1.1.10 (this one is correct)
do I have to manually delete the A record? and this happens to many of the workstations.
I checked aging and scavanging and it set up to its default.
I don't know how to solve and prevent this problem to happen.
Are you using the windows 2k server as dhcp server or are you using another box for that? If possible, disable any other DHCP server and use your windows server to provide the DHCP service.
ASKER
yes we use windows 2000 server as DHCP
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
prashsax ,
I can'I disable now a dhcp server during production time.
<<<Suppose you have 200 clients and your IP pool have 201 ip addresses.>>>
do you mean I have to setup the IP pool accordingto the clients machine that request IP? if so I will have to change the pool everytime I add or remove a computer.
I can'I disable now a dhcp server during production time.
<<<Suppose you have 200 clients and your IP pool have 201 ip addresses.>>>
do you mean I have to setup the IP pool accordingto the clients machine that request IP? if so I will have to change the pool everytime I add or remove a computer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"do you mean I have to setup the IP pool accordingto the clients machine that request IP? if so I will have to change the pool everytime I add or remove a computer."
No, but you should have the pool large enough to accomodate for more users than you have, or at least large enough that there are allways enough addresses available for all the users you expect to be onsite at one time. Also reduce the TTL time (Time To Live) so that leases are freed once they aren't used anymore.
No, but you should have the pool large enough to accomodate for more users than you have, or at least large enough that there are allways enough addresses available for all the users you expect to be onsite at one time. Also reduce the TTL time (Time To Live) so that leases are freed once they aren't used anymore.
ASKER
clients they get the new IP from DHCP, the problem is they can't update it in the DNS.
Step 1
Make sure your DNS server is configured to allow dynamic updates (see above)
Step 2
Make sure your DHCP server is configured to supply dynamic updates (see above)
Step 3
Enable DHCP Conflict Detection if machines keep getting the same IP (see above)
Step 4
Report back any errors you see while implementing steps 1 - 3.
Make sure your DNS server is configured to allow dynamic updates (see above)
Step 2
Make sure your DHCP server is configured to supply dynamic updates (see above)
Step 3
Enable DHCP Conflict Detection if machines keep getting the same IP (see above)
Step 4
Report back any errors you see while implementing steps 1 - 3.
if you are sure that clients are not updating the the DNS records then do this.
Allow unsecure updates on DNS. (Just for Test).
Then either make a script which will do :
ipconfig /registerdns
this should update the record.
You should always have more IPs in your pool then the number of machines in the network.
Allow unsecure updates on DNS. (Just for Test).
Then either make a script which will do :
ipconfig /registerdns
this should update the record.
You should always have more IPs in your pool then the number of machines in the network.
ASKER
Let me give you the records details in DNS
computer1 host(A) 122.1.1.40
Computer2 Host(A) 122.1.1.40
**Notice: they both have the same IP
========================== ====
122.1.1.40 Pointer(PTR) Computer1
122.1.1.40 Pointer(PTR) Computer55
122.1.1.40 Pointer(PTR) Computer66
**Notice: the same IP is for 3 different machines, computer1 is on the top and computer 2 is not there at all
========================== =====
122.1.5.56 Pointer(PTR) Computer2
**Notice: computer 2 has a different IP and this is the IP I get when I tun Ipconfig from the workstation itself. So this should be the right one.
========================== =====
computer1 host(A) 122.1.1.40
Computer2 Host(A) 122.1.1.40
**Notice: they both have the same IP
==========================
122.1.1.40 Pointer(PTR) Computer1
122.1.1.40 Pointer(PTR) Computer55
122.1.1.40 Pointer(PTR) Computer66
**Notice: the same IP is for 3 different machines, computer1 is on the top and computer 2 is not there at all
==========================
122.1.5.56 Pointer(PTR) Computer2
**Notice: computer 2 has a different IP and this is the IP I get when I tun Ipconfig from the workstation itself. So this should be the right one.
==========================
I forget what the term is but Windows DNS, for A records only, has some type of "scavange" feature where it will delete what it beleives are invalid A records. You may need to enable this.
That I am aware of there is no such feature for PTR records. Our Windows Admins finaly turned off autocreation of PTR records because of the mess is created.
That I am aware of there is no such feature for PTR records. Our Windows Admins finaly turned off autocreation of PTR records because of the mess is created.
ASKER
Aging and scavenging is already on.
ASKER
What is the process of resolving this issue?
computer1 host(A) 122.1.1.40
Computer2 Host(A) 122.1.1.40
**Notice: they both have the same IP
========================== ====
122.1.1.40 Pointer(PTR) Computer1
122.1.1.40 Pointer(PTR) Computer55
122.1.1.40 Pointer(PTR) Computer66
**Notice: the same IP is for 3 different machines, computer1 is on the top and computer 2 is not there at all
========================== =====
122.1.5.56 Pointer(PTR) Computer2
**Notice: computer 2 has a different IP and this is the IP I get when I tun Ipconfig from the workstation itself. So this should be the right one.
computer1 host(A) 122.1.1.40
Computer2 Host(A) 122.1.1.40
**Notice: they both have the same IP
==========================
122.1.1.40 Pointer(PTR) Computer1
122.1.1.40 Pointer(PTR) Computer55
122.1.1.40 Pointer(PTR) Computer66
**Notice: the same IP is for 3 different machines, computer1 is on the top and computer 2 is not there at all
==========================
122.1.5.56 Pointer(PTR) Computer2
**Notice: computer 2 has a different IP and this is the IP I get when I tun Ipconfig from the workstation itself. So this should be the right one.
PTR records you will need to delete. Do both of the A records have their own TTL?
ASKER
TTL is 1 day