Possible Account Modify IP Bug

[haywardweb]

v1.24.0

I not sure if you would consider this a bug, or an oversight on my part because of lack of instructions...

I just modifed a user account so that it was on a dedicated IP address. When I did this, accessing the site from the IP worked fine, but the domain name didn't work. When I pinged it, it was going to the old IP address, but the DNS settings in DA all pointed to the new IP. I logged into shell and restarted named. All was fine.

The issue:
Resellers don't have permission to log into root shell and restart named, thus they will not be able to modify IPs. Unless I missed something.

Fix?
Could the modify account script just restart named if the IP changes?

 

[jmstacey]

DirectAdmin should do this already.
What Operating System are you running?
Does 1.24.1 or the previous version 1.23.4 produce the same results?

You might want to make sure that DirectAdmin's service monitor is using the correct process id for named, and that the startup script in your rc.d or init.d directory is correct the same as DirectAdmin is looking for.

Is anythign reported in the error log about this?

 

[haywardweb]

What Operating System are you running?

Fedora 2

Does 1.24.1 or the previous version 1.23.4 produce the same results?

v1.24.0 is the only version I've ever had to modify an IP in, so I'm not sure what the results are in others.

You might want to make sure that DirectAdmin's service monitor is using the correct process id for named, and that the startup script in your rc.d or init.d directory is correct the same as DirectAdmin is looking for.

All looks sound in the service monitor. init.d starts up named, which is listed in the DA service monitor.

Is anythign reported in the error log about this?

2005:05:09-00:15:36: Ftp::swapIPs: old_owned: 0 have_old_ip: 0 have_new_ip: 0 new_free: 1 old: 64.27.216.180 new: 64.27.216.182
This was in the error log, but it's not related to dns.

 

[ClayRabbit]

I think that issue is related to DNS-cache of your internet-provider. AFAIK, DA always restart named after making any changes to DNS-zones.

 

[haywardweb]

My ISP does cache DNS, but I ruled out that problem. I tried it from a few servers with various ISPs. Even after I had manually restarted named, my ISP didn't work, but all of a sudden the other ISPs worked. There was an instant change when I restarted named. Unless these ISPs all decided to start caching DNS (they haven't in the past) AND they coincidentally updated their cache right when I restarted named, I don't think caching is my problem.