Facebook
Twitter
Hello!
I host my server behind a firewall.
Server has the ip 192.168.1.20
DNS has config files for every domain in:
/var/named/run-root/var/ directory.
I changed in every file that matches domain name the local ip address to that external which is seen from the web.
It works well, although every time I update Plesk or Bind I have to go those files and fix them again: change local ip there to that external.
My question is: I have one more file there so called reverse DNS one...
It has name like 1.168.192.in-addr.arpa
/thanks.
Actually it does not affect my sites directly, but when I browsed web reading about reverse DNS functionality it stand in many place that it is good for security, spam protection and so on.
This 1.168.192.in-addr.arpa file has no records to any domain I host and reflects the whole server.
Have I leave as it is or it better to the name that reflects the external IP?
I do not want to try before I know because every DNS issue causes significant problems - full recovering takes up to 24 hours and even more time... I mean to restore full traffic
I host my server behind a firewall.
Server has the ip 192.168.1.20
DNS has config files for every domain in:
/var/named/run-root/var/ directory.
I changed in every file that matches domain name the local ip address to that external which is seen from the web.
It works well, although every time I update Plesk or Bind I have to go those files and fix them again: change local ip there to that external.
My question is: I have one more file there so called reverse DNS one...
It has name like 1.168.192.in-addr.arpa
/thanks.
Actually it does not affect my sites directly, but when I browsed web reading about reverse DNS functionality it stand in many place that it is good for security, spam protection and so on.
This 1.168.192.in-addr.arpa file has no records to any domain I host and reflects the whole server.
Have I leave as it is or it better to the name that reflects the external IP?
I do not want to try before I know because every DNS issue causes significant problems - full recovering takes up to 24 hours and even more time... I mean to restore full traffic
