I'm using this program to monitor dns requests made by other programs on my computer, but I've the problem that the program won't run on dynamic ip addresses. Now I've changed the ip to static (still the same ip as in dynamic mode) and the program runs nicely, but it requires quite a lot of work to change my ip to static and also requires a lot of work to change it back to dynamic when connecting to another network. Is it possible to add some option in the ini-file to allow running the server on a network device that uses a dynamic address.
I was also wondering if it is possible to let the server assign an ip address, defined in the ini-file, to the network device it listens on. This would be a great tool for lan-parties were no internet connection is available, since it doesn't require assigning all computers a static ip.
I'm using windows xp and dualserver 6.0beta.
So, is it possible to add an option to the config file to allow dynamic ip addresses?
And is it also possible to let this server assign an ip address to the network device, that is used to listen on?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DNS Servers are not supposed to have dynamic/variable IP Address, as all other machines need this address to resolve hostnames. If DNS Server has dynamic/variable IP Address, which server would resolve this ?. Similarly DHCP Renew requests are sent to DHCP Server's IP Address straightaway. If this is dynamic and changes, Clients would not be able to renew their lease.
Hope this clarifies the point.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand why DNS servers are not supposed to have dynamic/variable IP addresses.
The reason why I believed allowing dynamic ips would improve the usability of the server is that it can be used for monitoring local DNS requests.
Currently this requires the following steps (for windows):
1. If using DHCP change your IP to static, with the same ip address
2. Configure windows to use your own ip as dns server.
3. Run the server listening to your own ip address.
4. Read the log-files
When done:
5. Change Ip configuration back to dynamic.
Being able to run the server on a dynamic ip address would remove the need to do step 1 and 5, which are quite annoying.
However, a better solution would be to enable the server to listen on 127.0.0.1.
That would make step 2 and 3 easier as well, since they don't have to be changed every time your ip address changes.
This way the DNS server can be used on local machines for monitoring (and caching) local DNS requests. This would enlarge the group of possible users.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From time to time we organize a lan-party at some place where no internet connection is available.
We usually change the ip-configuration of each computer to a unique static ip, somewhere in the range 192.168.0.2 to 192.168.0.250. This often requires a lot of time and also gives a lot of problems. For example: some participants couldn't connect to the internet anymore, because the settings weren't reversed.
I tried using a router, with DHCP support, to solve this problem, this was without any success.
When I found this server I thought it might solve these problems.
I haven't tested it yet, but I think it works quite well.
The reason why I asked for dynamic ips for the DHCP server has a similar reason as for the DNS server.
I don't like microsofts ip-configuration tool.
So if I add a few line in my configuration:
[00:41:42:41:42:05] # The mac address of the computer running the server
IP_Addr=192.168.0.1
Then running the server, would configure my ip address automatically. Saving me the hassle of changing my ip-configuration myself.
The problem is: the server would still think that the ip-address is variable, though it actually never changes.
(I guess the server would also argue about the fact that, when starting the server, there is no network device using 192.168.0.1. Having an option to ignore any warnings produced by a specified address, might solve this.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Add my vote to allow running the service on a dynamic IP.
Being able to either let it listen on 127.0.0.1 or add an ini setting (the default should be not to allow), will allow for easy adaptation for different needs.
For example, I am a web developer, being able to use the DNS locally without needing to change my ip to static will be a big bonus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using this program to monitor dns requests made by other programs on my computer, but I've the problem that the program won't run on dynamic ip addresses. Now I've changed the ip to static (still the same ip as in dynamic mode) and the program runs nicely, but it requires quite a lot of work to change my ip to static and also requires a lot of work to change it back to dynamic when connecting to another network. Is it possible to add some option in the ini-file to allow running the server on a network device that uses a dynamic address.
I was also wondering if it is possible to let the server assign an ip address, defined in the ini-file, to the network device it listens on. This would be a great tool for lan-parties were no internet connection is available, since it doesn't require assigning all computers a static ip.
I'm using windows xp and dualserver 6.0beta.
So, is it possible to add an option to the config file to allow dynamic ip addresses?
And is it also possible to let this server assign an ip address to the network device, that is used to listen on?
DNS Servers are not supposed to have dynamic/variable IP Address, as all other machines need this address to resolve hostnames. If DNS Server has dynamic/variable IP Address, which server would resolve this ?. Similarly DHCP Renew requests are sent to DHCP Server's IP Address straightaway. If this is dynamic and changes, Clients would not be able to renew their lease.
Hope this clarifies the point.
I understand why DNS servers are not supposed to have dynamic/variable IP addresses.
The reason why I believed allowing dynamic ips would improve the usability of the server is that it can be used for monitoring local DNS requests.
Currently this requires the following steps (for windows):
1. If using DHCP change your IP to static, with the same ip address
2. Configure windows to use your own ip as dns server.
3. Run the server listening to your own ip address.
4. Read the log-files
When done:
5. Change Ip configuration back to dynamic.
Being able to run the server on a dynamic ip address would remove the need to do step 1 and 5, which are quite annoying.
However, a better solution would be to enable the server to listen on 127.0.0.1.
That would make step 2 and 3 easier as well, since they don't have to be changed every time your ip address changes.
This way the DNS server can be used on local machines for monitoring (and caching) local DNS requests. This would enlarge the group of possible users.
From time to time we organize a lan-party at some place where no internet connection is available.
We usually change the ip-configuration of each computer to a unique static ip, somewhere in the range 192.168.0.2 to 192.168.0.250. This often requires a lot of time and also gives a lot of problems. For example: some participants couldn't connect to the internet anymore, because the settings weren't reversed.
I tried using a router, with DHCP support, to solve this problem, this was without any success.
When I found this server I thought it might solve these problems.
I haven't tested it yet, but I think it works quite well.
The reason why I asked for dynamic ips for the DHCP server has a similar reason as for the DNS server.
I don't like microsofts ip-configuration tool.
So if I add a few line in my configuration:
[00:41:42:41:42:05] # The mac address of the computer running the server
IP_Addr=192.168.0.1
Then running the server, would configure my ip address automatically. Saving me the hassle of changing my ip-configuration myself.
The problem is: the server would still think that the ip-address is variable, though it actually never changes.
(I guess the server would also argue about the fact that, when starting the server, there is no network device using 192.168.0.1. Having an option to ignore any warnings produced by a specified address, might solve this.)
Add my vote to allow running the service on a dynamic IP.
Being able to either let it listen on 127.0.0.1 or add an ini setting (the default should be not to allow), will allow for easy adaptation for different needs.
For example, I am a web developer, being able to use the DNS locally without needing to change my ip to static will be a big bonus