Skip to content
Split Reverse DNS
Got a problem with Viscosity or need help? Ask here!
When using split DNS I get expected behavior by putting comma separated domain names into the field at Networking ▸ DNS Settings: ▸ Domains
Forward lookups work great for the listed domains, but PTR lookups are still going to my LAN DNS not the one at the remote site.
I tried adding 1.16.172.in-addr.arpa to the Domains list but it still sends PTRs to my local DNS. How can I set it up to do this the right way?
This is Viscosity for macOS 1.8.5 (1537)
Forward lookups work great for the listed domains, but PTR lookups are still going to my LAN DNS not the one at the remote site.
I tried adding 1.16.172.in-addr.arpa to the Domains list but it still sends PTRs to my local DNS. How can I set it up to do this the right way?
This is Viscosity for macOS 1.8.5 (1537)
Hi msy,
That is all that is required to correctly handle split reverse DNS lookups. However a common mistake when testing this is to use legacy tools (nslookup, dig, and host) that don't use the macOS resolver system. These are the only processes that don't use the resolver system. For more information please see:
https://www.sparklabs.com/support/kb/ar ... unix-users
To test a reverse DNS lookup, please use something like the following (place x.x.x.x with the IP address to perform the reverse lookup for):
James
That is all that is required to correctly handle split reverse DNS lookups. However a common mistake when testing this is to use legacy tools (nslookup, dig, and host) that don't use the macOS resolver system. These are the only processes that don't use the resolver system. For more information please see:
https://www.sparklabs.com/support/kb/ar ... unix-users
To test a reverse DNS lookup, please use something like the following (place x.x.x.x with the IP address to perform the reverse lookup for):
Code: Select all
Cheers,dscacheutil -q host -a ip_address x.x.x.x
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hi James - thanks for the info. I had forgotten that I also had 172.16.1.* in the string as a test and once I took that entry out it's all working properly. I think I just had too many balls in the air at once trying to figure this out and not enough coffee.
3 posts
Page 1 of 1