"A" record query from Linux nslookup returns the answer, but after returns an unexpected error

[justein230]

Describe the bug
When running an authoritative zone, an A record lookup request on nslookup in Linux will return the correct response and then immediately after return NXDOMAIN. From the logs, it looks like it gets the A record, then continues to attempt to look for more record types, and fails on AAAA.

NOTE: nslookup on Windows behaves as expected.

To Reproduce
Steps to reproduce the behavior:

1. Run nslookup on a Linux server
2. Set server to Gravity server
3. Make a request for an A record
4. See answer and error

Expected behavior
In step 4, the answer should be returned without the AAAA failure.

Screenshots

Logs

gravity-1  | {"level":"debug","ts":1734972089.0605125,"logger":"role.dns","msg":"sending request to handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"int_soa"}
gravity-1  | {"level":"debug","ts":1734972089.0605228,"logger":"role.dns","msg":"no reply, trying next handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"int_soa"}
gravity-1  | {"level":"debug","ts":1734972089.0605307,"logger":"role.dns","msg":"sending request to handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"memory"}
gravity-1  | {"level":"debug","ts":1734972089.0605474,"logger":"role.dns","msg":"returning reply from handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"memory"}
gravity-1  | {"level":"info","ts":1734972089.0606427,"logger":"role.dns","msg":"DNS Query","instance":"gravitytest","version":"0.19.0+1c9d9dbf","runtime":0,"client":"172.22.18.22","response":"NOERROR","queryNames":["foo.zone1.test."],"queryTypes":["A"],"answerRecords":["1.1.1.1"],"answerTypes":["A"]}
gravity-1  | {"level":"debug","ts":1734972089.0606663,"logger":"role.dns","msg":"dispatching event","instance":"gravitytest","version":"0.19.0+1c9d9dbf","topic":"roles.tsdb.inc"}
gravity-1  | {"level":"debug","ts":1734972089.0606785,"logger":"role.tsdb","msg":"tsdb inc","instance":"gravitytest","version":"0.19.0+1c9d9dbf","key":"/dns/memory"}
gravity-1  | {"level":"debug","ts":1734972089.061731,"logger":"role.dns","msg":"routing request to zone","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"/dns/zones/zone1.test."}
gravity-1  | {"level":"debug","ts":1734972089.0620086,"logger":"role.dns","msg":"sending request to handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"int_soa"}
gravity-1  | {"level":"debug","ts":1734972089.062091,"logger":"role.dns","msg":"no reply, trying next handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"int_soa"}
gravity-1  | {"level":"debug","ts":1734972089.062102,"logger":"role.dns","msg":"sending request to handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"memory"}
gravity-1  | {"level":"debug","ts":1734972089.0621147,"logger":"role.dns","msg":"no reply, trying next handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"memory"}
gravity-1  | {"level":"debug","ts":1734972089.0621202,"logger":"role.dns","msg":"sending request to handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"etcd"}
gravity-1  | {"level":"debug","ts":1734972089.0621283,"logger":"role.dns","msg":"fetching kv key","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"etcd","key":"/dns/zones/zone1.test./foo/AAAA"}
gravity-1  | {"level":"debug","ts":1734972089.0631201,"logger":"role.dns","msg":"fetching kv key","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"etcd","key":"/dns/zones/zone1.test./*/AAAA"}
gravity-1  | {"level":"debug","ts":1734972089.0637338,"logger":"role.dns","msg":"fetching kv key","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"etcd","key":"/dns/zones/zone1.test./foo/CNAME"}
gravity-1  | {"level":"debug","ts":1734972089.0641086,"logger":"role.dns","msg":"no reply, trying next handler","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test.","handler":"etcd"}
gravity-1  | {"level":"debug","ts":1734972089.0645092,"logger":"role.dns","msg":"no handler has a reply, fallback back to NX","instance":"gravitytest","version":"0.19.0+1c9d9dbf","zone":"zone1.test."}
gravity-1  | {"level":"info","ts":1734972089.064778,"logger":"role.dns","msg":"DNS Query","instance":"gravitytest","version":"0.19.0+1c9d9dbf","runtime":2,"client":"172.22.18.22","response":"NXDOMAIN","queryNames":["foo.zone1.test."],"queryTypes":["AAAA"],"answerRecords":[],"answerTypes":[]}
gravity-1  | {"level":"debug","ts":1734972092.3400645,"logger":"role.tsdb","msg":"writing metrics","instance":"gravitytest","version":"0.19.0+1c9d9dbf"}
gravity-1  | {"level":"debug","ts":1734972092.3401127,"logger":"role.tsdb","msg":"dispatching event","instance":"gravitytest","version":"0.19.0+1c9d9dbf","topic":"roles.tsdb.before_write"}
gravity-1  | {"level":"debug","ts":1734972092.340194,"logger":"role.tsdb","msg":"tsdb set","instance":"gravitytest","version":"0.19.0+1c9d9dbf","key":"/system/memory"}
gravity-1  | {"level":"debug","ts":1734972092.3404846,"logger":"role.tsdb","msg":"tsdb set","instance":"gravitytest","version":"0.19.0+1c9d9dbf","key":"/system/cpu"}

Version and Deployment:

• Gravity version: image id: 1c9d9db, commit id: 1c9d9db
• Deployment: docker-compose

Additional context
Add any other context about the problem here.

[sholdee]

I have the same problem as of v0.19.1. Versions earlier than this, including v0.19.0, work fine for me.

/app $ nslookup hass.mgmt.domain.net
Server:         10.43.0.10
Address:        10.43.0.10:53

Name:   hass.mgmt.domain.net
Address: 192.168.77.30

** server can't find hass.mgmt.domain.net: NXDOMAIN