This may be a coincidence, but a few minutes after I saw the
csf/lfd auto update email, I could no longer access my linux server.
So, I'm just checking if anyone else is seeing any dyndns problems.
My csf.dyndns file has two lines. Something like:
tcp|in|d=993|s=test1.exampledomain
test2.exampledomain
When I tried to access my server from test2, I got connection refused.
Other notes
-----------------------
o dyndns had been working fine for several months
o i'm not using ipv6
o pretty sure the ip# for test2 also was also listed in csf.allow
csf v7.50 change to dyndns may have affected my install
-
- Moderator
- Posts: 1524
- Joined: 01 Oct 2008, 09:24
Re: csf v7.50 change to dyndns may have affected my install
You can check two things to see if DYNDNS is working:
1. Check the iptables chain:
iptables -L ALLOWDYNIN -nv
host test2.exampledomain
2. Check the lfd log to see if there are any DYNDNS errors - /var/log/lfd.log
1. Check the iptables chain:
iptables -L ALLOWDYNIN -nv
host test2.exampledomain
2. Check the lfd log to see if there are any DYNDNS errors - /var/log/lfd.log
Re: csf v7.50 change to dyndns may have affected my install
After reading the Report Bugs section post titled
After upgrading to 7.51 - bug with csf.allow
I'm pretty certain I have the same problem because
I also did the "chattr +i /etc/resolv.conf".
I'm locked out of my remote server, and might
have to reformat to gain access.
After upgrading to 7.51 - bug with csf.allow
I'm pretty certain I have the same problem because
I also did the "chattr +i /etc/resolv.conf".
I'm locked out of my remote server, and might
have to reformat to gain access.