dns resolver failures

[dfrhodes]

Okay, I downloaded the demo and installed. I even read the warnings beforehand. I was impressed with the product but now that I've uninstalled I am getting massive failure points on my server.

BTW - I am NOT happy at the moment.

Basically, I installed on a Windows 2003 Server that is a domain controller, dual-homed, DNS and DHCP server. A very clean setup (until now)

The first thing I noticed was the inability to resolve dns from the server console. I had already restarted the DNS server locally and it is working fine for network clients - just not from itself. I attempted to change the dns server setting for the external adapter to my ISP server..still no luck. Not having the DNS client on the server working is a disaster.. Active Directory is having problems, local apps are not working, etc.

I scanned the registry after the unintal and there is still a ton of firstspot.org references in it that were not cleaned up. I appears that firstspot actually changes the domain controller name to firstspot.org

If anyone can help me with this please respond. I'm to the point of having to reinstall the OS. I've already reinstalled the adapter and other common fixes to no avail.

thanks,

David
dfrhodes@proxinet.net

[hans]

It is caused by window itself not renew the original domain.

1. right click MyComputer->Property

2. Choose Computer Name tag

3. Click Change( Choose Ok if there is a dialog box popup )

4. Click More

5. Enter the original domain under "Primary DNS suffix of this computer:".

6. Click Ok and restart computer.
_________________
~ Patronsoft Limited ~

[dfrhodes]

hans - Thank you for your response and your solution did resolve my problem. You have my deepest gratitude.

However, in order to change the suffix back I had to uninstall Certificate Services after getting this error -

http://www.proxinet.net/mycomputer.GIF

I assume that's why the uninstaller wasn't able to clean up properly. Luckily I had backups of my root certs so I didn't have to issue new ones.

I really think the dev team should look into the impact of this. I can't be the only one running cert server out there. If this had been a production server I would have been toast!

Requiring a change of the domain name sounds highly suspicious as well. If that is truly required, it seems like it would be better just to ship entire OS image like joltage used to do.

[hans]

Thank you so much for your information, we will look into it asap.
_________________
~ Patronsoft Limited ~