We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am starting to use Gravity DNS, but I noticed that SOA records are not being resolved as expected.
The following is the records for zone1.test:
And here is the zone list:
Zone config:
When I run the following query using nslookup, I do not get the SOA for the zone as expected:
root@testkube:/home/localadmin# nslookup > server 172.22.18.78 Default server: 172.22.18.78 Address: 172.22.18.78#53 > foo.zone1.test Server: 172.22.18.78 Address: 172.22.18.78#53 Name: foo.zone1.test Address: 1.1.1.1 > set type=soa > zone1.test Server: 172.22.18.78 Address: 172.22.18.78#53 *** Can't find zone1.test: No answer > zone1.test. Server: 172.22.18.78 Address: 172.22.18.78#53 *** Can't find zone1.test.: No answer >
Thanks in advance for the help! Really enjoying Gravity so far.
The text was updated successfully, but these errors were encountered:
You are a wizard! Thank you for the quick fix and happy holidays 🙂
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I am starting to use Gravity DNS, but I noticed that SOA records are not being resolved as expected.
The following is the records for zone1.test:
And here is the zone list:
Zone config:
When I run the following query using nslookup, I do not get the SOA for the zone as expected:
Thanks in advance for the help! Really enjoying Gravity so far.
The text was updated successfully, but these errors were encountered: