DNS Issues

[Mighty]

Hi Folks,

I have posted this issue here a couple of times and am back to haunt the forum again. To give some background, I have a server which is a domain controller, Exchange Server, Remote Access server and DNS server. Initially, when I set up the server I set up two NICS hoping to use one NIC for remote access traffic. However, there was an issue with Exchange so I disabled one of the NICS (195.10.20.3) leaving just one functional NIC (195.10.20.10).

However, the problem was that the .3 NIC still appeared in DNS - despite my best attempts to prevent this. So when clients attempted to connect to the server they were resolving to the .3 address and then getting connection issues because the NIC was disabled. I tried deleting and readding the DNS zone and this didn't get rid of it.

My latest action was to physically remove the network card from the server. However, the .3 address still appears. I am at my wits end and don't know what to do about it.

Can anyone suggest what to do? We would have some clients with static IP addresses. If they made any reference to the .3 address would that cause the DNS server to keep putting a record in DNS for it? I just can't see why it keeps appearing.

Any help would be appreciated.

Thanks

Mighty

 

[Mighty]

What I have tried now is to add a second IP address to the remaining NIC - I have added 195.10.20.3 as a 2nd IP address on this NIC.

When I clicked OK on this it told me that the IP address was already bound to another network card but it was hidden from view as the card wasn't physically in the machine. I said that it was OK to use it anyway.

However, it highlighted that the server obviously has bound that IP address to the interface. Where would I look to find out???

Mighty

 

[PScottC]

When you removed the NIC from the system, the IP configuration was kept in case the NIC is re-inserted. To get rid of this message re-install the NIC, then configure that NIC to use DHCP for it's IP and DNS settings. Then, re-remove the NIC.

You will have to manually delete the .3 address from DNS if you no longer want to use it.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[PuzzledUNIX]

The other simple solution is insert the NIC at the same slot where the old one was placed. Most of the time it happens on Proliant Servers.


I hope it helps.
Sam.

 

[Mighty]

I have tried to remove the .3 IP address manually from DNS. I do it several times every day but it keeps reappearing - even though I had first disabled the interface and then removed it.

Mighty

 

[PScottC]

If you've configured that IP as a secondary address on an active NIC, then yes, it will reappear.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[ShackDaddy]

Mighty, your RAS service (running locally or on another server) might be registering that IP in DNS for you. Check all your RAS configurations and see what the IP range that it is ready to assign clients is and see what IP the RAS services thinks it is being bound to.

When you do an 'nbtstat -n' does anything referencing that .3 address show up?

ShackDaddy

 

[Mighty]

PSC,

In response to your comments, it kept reappearing in DNS before I added it as a secondary IP address. I only put it in as a secondary address in an attempt to fix the problems with clients resolving to the .3 address. I couldn't get it out of DNS so I did that to fix the problem.

ShackDaddy, RAS uses a completely different set of addresses as it gets them from DHCP and the DHCP scope only starts at 195.10.20.10. I have also set the RAS addresses not to register with DNS. When I did the nbtstat there was no reference to the .3 address.

At the moment, it is working fine with .3 as a secondary IP address but I don't know if it will cause any other issues. The reason that I took out the .3 interface in the first place is because it was causing problems with Exchange.

Mighty