Old IPv6's still listed in user's httpd.conf's

[LawsHosting]

Ok, so I stupidly used the ipswap.sh, not only for my IPv4's, but I tried my IPv6's too. Now the old IPv6's are suck in the user's httpd.conf's... There are no mentions of the old IPs anywhere in /usr/local/directadmin/data/users/* files, and a config rewrite doesn't help.

eg.

[warn] VirtualHost 2001:41d0:1:xxxx:0:0:4:443 overlaps with VirtualHost 2001:41d0:1:xxxx:0:0:0:4:443, the first has precedence, perhaps you need a NameVirtualHost directive

Any ideas?

Martynas tried to help but was unsuccessful.

 

[zEitEr]

Hello,

remove them from

/usr/local/directadmin/data/admin/ip.list
/usr/local/directadmin/data/admin/ips/

and rewrite apache's configs.

 

[LawsHosting]

Theyre not there

 

[LawsHosting]

To follow up, I've mailed John this thread link and I realised I linked my IPv4's to my IPv6's...... and indeed this was why. I guess the ipswap.sh doesn't check for linked IP's?

 

[DirectAdmin Support]

I guess the ipswap.sh doesn't check for linked IP's?

ah, you might be right on that.

I'll have to check the script, as it's not been updated in quite a while.. likely from before the linked-IP feature existed.
Thanks,

John

 

[DirectAdmin Support]

Correction, I do already see the code in there...
try running this in debug mode:

cd /usr/local/directadmin
echo "action=ipswap&value=linked_ips&old=2001:41d0:1:92d0:XXXX:XXXXX::XXXX&new=2001:41d0:a:XXXX:XXXXX::XXXX" >> data/task.queue.cb; ./dataskq d2000 --custombuild

And then confirm if they get updated in:

/usr/local/directadmin/data/admin/ips/*

where applicable. (there is a variable there).

John