can't do host/rDNS lookups for local IPs
Posted: Thu Jun 30, 2016 12:39 pm
I'm posting this in this section on the off-chance it might be to do with the ASL firewall. I really doubt it though and to be honest I think I'm clutching at straws. So obviously move it if needed.
Anyhooo...
What's happening is that on a particular machine I've set up for testing, with Plesk 12, Centos 7, and ASL, I can't do host/rDNS lookups on IPs within the range allocated to me.
It happily does lookups for IPs further afield, however.
For example:
host x.x.x.x gives me NXDOMAIN, where x.x.x.x is within my range.
(similar NXDOMAIN results for dig @localhost -x x.x.x.x)
As you might expect, dig @8.8.8.8 -x x.x.x.x works fine, as I'm using an external nameserver.
Where things get interesting is this:
host x.x.y.x where y is x+1 takes me well out of the range assigned to me, and gives a good result!
"y" remains within my co-lo provider's IP range though.
I just don't get it. It is like IPs around me are somehow out of reach.
named is running and working on the system just fine. It allows forward lookups with no errors.
Port 53 is open for TCP and UDP.
All the other machines I have on the same range all happily do reverse lookups with no issues at all.
Named.conf has nothing strange in it. It has not been manually altered.
allow-recursion {
localnets;
};
I'm baffled.
Anyhooo...
What's happening is that on a particular machine I've set up for testing, with Plesk 12, Centos 7, and ASL, I can't do host/rDNS lookups on IPs within the range allocated to me.
It happily does lookups for IPs further afield, however.
For example:
host x.x.x.x gives me NXDOMAIN, where x.x.x.x is within my range.
(similar NXDOMAIN results for dig @localhost -x x.x.x.x)
As you might expect, dig @8.8.8.8 -x x.x.x.x works fine, as I'm using an external nameserver.
Where things get interesting is this:
host x.x.y.x where y is x+1 takes me well out of the range assigned to me, and gives a good result!
"y" remains within my co-lo provider's IP range though.
I just don't get it. It is like IPs around me are somehow out of reach.
named is running and working on the system just fine. It allows forward lookups with no errors.
Port 53 is open for TCP and UDP.
All the other machines I have on the same range all happily do reverse lookups with no issues at all.
Named.conf has nothing strange in it. It has not been manually altered.
allow-recursion {
localnets;
};
I'm baffled.