Dns host record with wrong details

  • Thread starter Thread starter Paul Martin
  • Start date Start date
P

Paul Martin

Hi All

Needed to change the IP address of our Win2000 server (PC1) at weekend from
192.168.0.1 to 192.168.0.2. After changing the values in DNS, WINS and DHCP.
Everything seemed to work but.... then you ping the server from any client
using its name e.g. ping pc1 it lists the pc at its old value 192.168.0.1
and of course times out. Ping the ip address and its fine.

Noticed that in DNS that it lists a host record for PC1 and its ip
192.168.0.1 but even if I change this, or delete and add a manual entry it
keeps coming back. Is this the problem? How do you solve it.

By the way pinging on PC1 on itself lists the correct ip address.

Cheers
Paul
 
In Paul Martin <[email protected]> posted a question
Then Kevin replied below:
: Hi All
:
: Needed to change the IP address of our Win2000 server (PC1) at
: weekend from 192.168.0.1 to 192.168.0.2. After changing the values in
: DNS, WINS and DHCP. Everything seemed to work but.... then you ping
: the server from any client using its name e.g. ping pc1 it lists the
: pc at its old value 192.168.0.1 and of course times out. Ping the ip
: address and its fine.
:
: Noticed that in DNS that it lists a host record for PC1 and its ip
: 192.168.0.1 but even if I change this, or delete and add a manual
: entry it keeps coming back. Is this the problem? How do you solve it.
:
: By the way pinging on PC1 on itself lists the correct ip address.
:
: Cheers
: Paul

Check the listener IP on the interfaces tab on the DNS server properties.
The best way to change the IP on a DC is to add the new IP and make sure
replication is working before removing the old IP.
 
Check the listener IP on the interfaces tab on the DNS server properties.
The best way to change the IP on a DC is to add the new IP and make sure
replication is working before removing the old IP.
Click to expand...
Hi Kevin

Thanks for the reply. I will no better next time ;)

The listener IP is set for the new IP address. Any other ideas?

Cheers
Paul
 
Hi Kevin

A bit more info for you. If you delete the record that appears in DNS saying
the host record for pc1 has an ip address of 192.168.0.1 and add manually
one with an ip address of 192.168.0.2 everyting within the network works
fine.

Reset the server the host record for PC1 changes back to 192.168.0.1 and
things stop working. Delete the record and add manually and eveyrthing works
again.

Any clues?

If I wanted to change the server back to the original ip address would
procedure would you recommend doing?

Thanks for your help
Paul
 
In Paul Martin <[email protected]> posted a question
Then Kevin replied below:
: Hi Kevin
:
: A bit more info for you. If you delete the record that appears in DNS
: saying the host record for pc1 has an ip address of 192.168.0.1 and
: add manually one with an ip address of 192.168.0.2 everyting within
: the network works fine.
:
: Reset the server the host record for PC1 changes back to 192.168.0.1
: and things stop working. Delete the record and add manually and
: eveyrthing works again.
:
: Any clues?
:
: If I wanted to change the server back to the original ip address would
: procedure would you recommend doing?
:
: Thanks for your help
: Paul
:
Is this an Active Directory domain?

Is the zone AD integrated or standard primary?

If the zone is standard Primary, in the C:\WINNT\system32\dns\backup folder
delete the zonename.dns file then restart the DNS service. That should stop
the old IP from returning.
 
Hi Kevin
Is this an Active Directory domain? Yes

Is the zone AD integrated or standard primary? Integrated

If the zone is standard Primary, in the C:\WINNT\system32\dns\backup folder
delete the zonename.dns file then restart the DNS service. That should stop
the old IP from returning.
Click to expand...
DOes this still apply with the above answers?

Cheers
Paul
 
In Paul Martin <[email protected]> posted a question
Then Kevin replied below:
: Hi Kevin
:
:: Is this an Active Directory domain?
: Yes
:
:: Is the zone AD integrated or standard primary?
: Integrated
:
:: If the zone is standard Primary, in the C:\WINNT\system32\dns\backup
:: folder delete the zonename.dns file then restart the DNS service.
:: That should stop the old IP from returning.



: DOes this still apply with the above answers?

Not if the Zone is AD Integrated.
On the zone properties, General tab is Allow dynamic updates set to Yes or
Secure updates only?
Since you removed the old IP you are probably going to need this to be set
to Yes.
For the time being set DNS to listen on all IP addresses.
Then, restart the Netlogon service, run ipconfig /flushdns, then run
ipconfig /registerdns

Post the ipconfig /all if you have more problems
 
Back
Top