New answers tagged reverse-dns
As I mentioned in a comment earlier, the addresses mentioned in the question belong to Google and therefore it's ultimately up to Google whether these addresses have a reverse PTR record or not. I haven't really dug into what exactly all of these addresses may be (maybe Pingdom made that information available to you?) but for instance 184.108.40.206 appears ...
DNS servers have cache, each change take time to be fully functional for all DNS servers. It may be fix in few hours. You can try nslookup -type=ns 220.127.116.11 to get a non cached answer
Actually this one seems to be missing reverse. Received: from my.webhosting-server.com (unknown [18.104.22.168]) btw. the IP should have matching A record as well (missing A record could lead to the PTR record being ignored)
ttportal.co.uk is currently delegated to a set of four name servers (the below according to nsd.nic.uk which is one of the servers authoritative for uk as well as co.uk): ;; AUTHORITY SECTION: ttportal.co.uk. 172800 IN NS ns-2015.awsdns-59.co.uk. ttportal.co.uk. 172800 IN NS ns-1407.awsdns-47.org. ttportal.co.uk. ...
Your DNS server isn't authoritative for the ip address that your server is using, your ISP is authoritative for the ip address. You need your ISP to create the PTR record for your server in their Reverse Lookup zone.
The immediate cause of error is the leading whitespace in your db.10 file. Correct: ; ; BIND reverse data file for local loopback interface ; $TTL 604800 @ IN SOA necacdnsone.necone.com. root.necone.com. ( 1 ; Serial 604800 ; Refresh 86400 ...
Nowadays the most frequent culptor is GSSAPI: /etc/ssh/sshd_config: GSSAPIAuthentication no The other three culptors for Linux platform have been mentioned in other answer: add to sshd a command line option -u0 set UseDNS no don't use from=hostname inside authorized_keys files
Top 50 recent answers are included