my BIND-referenced IPv4 rDNS or PTR not Being Issued following IPv4 Address Lookup
hello all.
i am presently running a nanode box with debian 10, apache and BIND.
i have configured BIND to reference my 2 (non-Linode) nameservers (e.g. ns1.mynameserver.tld and ns2.anothernameserver.tld).
i have also configured another domain with BIND that i am hosting on my nanode box (e.g. mydomain.tld).
the static IPv4 address of my nanode box (hosting mydomain.tld) is, say, 1.2.3.4
i have assigned the nameservers ns1.mynameserver.tld and ns2.anothernameserver.tld (above) to mydomain.tld (above) via my domain name registrar.
all zone files (with appropriate A Records, etc.) for the aforementioned (sub)domains exist on my nanode box.
none of the aforementioned domain names have been included within my Linode Account Manager 'Domains' section (https://cloud.linode.com/domains).
after installing BIND, assigning the 2 aforementioned nameservers (ns1.mynameserver.tld and ns2.anothernameserver.tld) to mydomain.tld via my domain name registrar, and waiting for propagation (about 24 hours), running 'host mydomain.tld' or 'nslookup mydomain.tld' from a local Terminal returns the correct IPv4 address (1.2.3.4) associated with mydomain.tld.
furthermore, apache2 loads the appropriate page when calling mydomain.tld via any web browser client.
the problem - IPv4 reverse DNS:
although BIND and apache appear to be behaving, i am having trouble overriding Linode's setting for reverse DNS (rDNS or PTR).
with rDNS set via Linode Account Manager (Linodes > Linode Label > Networking > IPv4 reverse DNS Setting) to 'li*-.members.linode.com' or any other entry i care to add (that has an appropriate A Record entry, e.g. linode-ptr.mydomain.tld), and waiting for propagation, running 'host 1.2.3.4' or 'nslookup 1.2.3.4' via a local Terminal returns the Linode Account Manager-set rDNS, e.g.
nslookup 1.2.3.4
>
4.3.2.1.in-addr.arpa name = li*-.members.linode.com (or linode-ptr.mydomain.tld, as detailed above)
what i would like to do is override (disable/negate) Linode's reverse DNS setting/facility and utilize my BIND configuration to set the rDNS.
i have an appropriately configured reverse zone file (e.g. 4.3.2.1.in-addr.arpa or 3.2.1.in-addr.arpa) with PTR assigned within that file on my nanode box.
BIND has also been configured for that reverse zone file.
regardless of the PTR within the BIND reverse zone file on my nanode box (e.g. bind-ptr.mydomain.tld), the PTR that is returned from any reverse IPv4 address lookup (e.g. via 'host 1.2.3.4', 'nslookup 1.2.3.4', mxtoolbox etc.) is always that set via the Linode Account Manager (Linodes > Linode Label > Networking > IPv4 reverse DNS Setting) (e.g. li*-.members.linode.com or linode-ptr.mydomain.tld, as detailed above).
in my ignorance, i tried disabling 'Network Helper' from within the Linode Account Manager and included my nameservers (ns1.mynameserver.tld and ns2.anothernameserver.tld) within /etc/resolv.conf of my nanode box hosting mydomain.tld, but the same linode-set (non-BIND) PTR (e.g. li*-.members.linode.com or linode-ptr.mydomain.tld) was returned with an IPv4 address lookup.
is it possible to override Linode's PTR setting/facility and utilize my BIND-configured setting of PTR (using an appropriate BIND-referenced reverse zone file, e.g. 4.3.2.1.in-addr.arpa or 3.2.1.in-addr.arpa)?
any advice would be greatly appreciated. thank you.
tetsujin28
.
4 Replies
is it possible to override Linode's PTR setting/facility and utilize my BIND-configured setting of PTR (using an appropriate BIND-referenced reverse zone file, e.g. 4.3.2.1.in-addr.arpa or 3.2.1.in-addr.arpa)?
It's not possible to use your own nameservers to serve the reverse-lookup zones for Linode's IP ranges.
Even though the IP is allocated to you, it is still owned by Linode, and it's up to them how they serve the DNS records for those IPs.
If the reverse DNS hostname you are specifying in Cloud Manager is not taking effect, you'd be better off raising a support ticket. If you post the actual IP here, I can also tell you if it's resolving correctly externally to your Linode.
thanks andysh.
rDNS set via Linode's 'Cloud Manager' has always worked for me.
i thought it might be possible to utilize reverse zone entries on my nanode (via BIND) to set the rDNS, and therefore complete my BIND-mediated tasks on my nanode.
tetsujin28
.
i thought it might be possible to utilize reverse zone entries on my nanode (via BIND) to set the rDNS, and therefore complete my BIND-mediated tasks on my nanode.
Unfortunately not. Your own domain is yours, so you can control the DNS for it. The IPs are not - they are Linode's, and just allocated to you for the space of time in which your Linode is active.
Therefore the DNS control is Linode's.
cheers.
tetsujin28
.