Looking to use Gravity as a primary DNS Server for a bunch of airgap linux hosts, but having issues with CNAME resolution. Gravity is 100% authoritative for all records in the zone, but when pointing to gravity as a dns resolver, it fails CNAME lookups.
nslookup cname1.test.me
Server: 127.0.0.1
Address: 127.0.0.1#53
cname.test.me canonical name = cname1.test.me
Returns dig returns with Recursion not available!
But the followup A record is within an authoritative zone, so I'm not sure why recursion is needed at all.
In coreDNS you can work around this with header module:
header {
response set ra # set RecursionAvailable flag
}
Is there a way to do this in gravity?
EDIT:
Added info:
Removing the memory handler allows this to work within the same zone.
-type: memory
So this might be a work around for this specific use case
Looking to use Gravity as a primary DNS Server for a bunch of airgap linux hosts, but having issues with CNAME resolution. Gravity is 100% authoritative for all records in the zone, but when pointing to gravity as a dns resolver, it fails CNAME lookups.
nslookup cname1.test.me
Server: 127.0.0.1 Address: 127.0.0.1#53
cname.test.me canonical name = cname1.test.me
Returns dig returns with Recursion not available!
But the followup A record is within an authoritative zone, so I'm not sure why recursion is needed at all.
In coreDNS you can work around this with header module: header { response set ra # set RecursionAvailable flag }
Is there a way to do this in gravity?
EDIT: Added info: Removing the memory handler allows this to work within the same zone. -type: memory
So this might be a work around for this specific use case