Hi,
I've running an appserver on Windows XP Pro. The server kicks off a number of processes when it starts up by communicating with them using an entry held in the DNS e.g it uses a name that equates to an IP address. This DNS entry points back to the local machine by it's IP address on the network rather than the 127.0.0.1 address
This all works fine whilst the machine is running on the network initially used to set up the appserver. However, if it's moved onto another network it's local IP address changes and the DNS entry no longer points to anything valid. So the calls made by the appserver don't work.
What I need to be able to do is to update the DNS entry. However, as the machine will be moving networks quite frequently I don't think I really want to be flushing the DNS all the time.
Is there any way to do this? Sorry if there is an obvious answer, networks really ain't my strong point.
Thanks,
Jim
I've running an appserver on Windows XP Pro. The server kicks off a number of processes when it starts up by communicating with them using an entry held in the DNS e.g it uses a name that equates to an IP address. This DNS entry points back to the local machine by it's IP address on the network rather than the 127.0.0.1 address
This all works fine whilst the machine is running on the network initially used to set up the appserver. However, if it's moved onto another network it's local IP address changes and the DNS entry no longer points to anything valid. So the calls made by the appserver don't work.
What I need to be able to do is to update the DNS entry. However, as the machine will be moving networks quite frequently I don't think I really want to be flushing the DNS all the time.
Is there any way to do this? Sorry if there is an obvious answer, networks really ain't my strong point.
Thanks,
Jim
