dig command does not show A records
0
I brought up a DNS server on a Fortigate 60D.
However, instead of dig giving me all the A records I defined (about 80 of them), all I see is this (note the lack of any lines of the formlocal. 172719 IN A 192.168.1.97):
$ dig local all
; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> local all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15919
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;local. IN A
;; AUTHORITY SECTION:
. 1293 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 109
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;all. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 107
Where I expected to something similar to:
;; ANSWER SECTION:
local. 86400 IN NS dns.local.
local. 86400 IN A 192.168.1.97
local. 86400 IN A 192.168.1.98
Can you suggest a way to make dig display the A records?
dns mdns fortigate
asked Jan 23 at 22:08
boardriderboardrider
2902719
add a comment |
0
I brought up a DNS server on a Fortigate 60D.
However, instead of dig giving me all the A records I defined (about 80 of them), all I see is this (note the lack of any lines of the formlocal. 172719 IN A 192.168.1.97):
$ dig local all
; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> local all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15919
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;local. IN A
;; AUTHORITY SECTION:
. 1293 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 109
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;all. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 107
Where I expected to something similar to:
;; ANSWER SECTION:
local. 86400 IN NS dns.local.
local. 86400 IN A 192.168.1.97
local. 86400 IN A 192.168.1.98
Can you suggest a way to make dig display the A records?
dns mdns fortigate
asked Jan 23 at 22:08
boardriderboardrider
2902719
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13
add a comment |
0
0
0
I brought up a DNS server on a Fortigate 60D.
However, instead of dig giving me all the A records I defined (about 80 of them), all I see is this (note the lack of any lines of the formlocal. 172719 IN A 192.168.1.97):
$ dig local all
; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> local all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15919
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;local. IN A
;; AUTHORITY SECTION:
. 1293 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 109
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;all. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 107
Where I expected to something similar to:
;; ANSWER SECTION:
local. 86400 IN NS dns.local.
local. 86400 IN A 192.168.1.97
local. 86400 IN A 192.168.1.98
Can you suggest a way to make dig display the A records?
dns mdns fortigate
asked Jan 23 at 22:08
boardriderboardrider
2902719
I brought up a DNS server on a Fortigate 60D.
However, instead of dig giving me all the A records I defined (about 80 of them), all I see is this (note the lack of any lines of the formlocal. 172719 IN A 192.168.1.97):
$ dig local all
; <<>> DiG 9.9.4-RedHat-9.9.4-72.el7 <<>> local all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15919
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;local. IN A
;; AUTHORITY SECTION:
. 1293 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 109
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;all. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019012302 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Wed Jan 23 13:52:42 PST 2019
;; MSG SIZE rcvd: 107
Where I expected to something similar to:
;; ANSWER SECTION:
local. 86400 IN NS dns.local.
local. 86400 IN A 192.168.1.97
local. 86400 IN A 192.168.1.98
Can you suggest a way to make dig display the A records?
dns mdns fortigate
dns mdns fortigate
asked Jan 23 at 22:08
boardriderboardrider
2902719
asked Jan 23 at 22:08
boardriderboardrider
2902719
asked Jan 23 at 22:08
boardriderboardrider
2902719
asked Jan 23 at 22:08
boardriderboardrider
2902719
asked Jan 23 at 22:08
boardriderboardrider
2902719
2902719
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13
add a comment |
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13
add a comment |
2 Answers
2
active
oldest
votes
1
dig local A
This will request only A records for the domain "local". I normally specify a server -
dig @server.name domain.name A
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
As you can see in the example I gave in the OP, the replay fordig local alldoes not include any A records. When I dodig local Aordig @192.168.1.99 local A, I get the same results as when I dodig local all, namely - no A records are displayed, besides;; QUESTION SECTION: ;local. IN A.
– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the commanddia test application dnsprox 8on the Fortigate 60D, not to mention that name resolution works in my LAN machines.
– boardrider
Jan 26 at 1:03
add a comment |
0
The following is a workaround to get A records, but it's better than nothing:
(echo "diag test app dnsproxy 8"; echo "exit") | ssh -tt <user>@<Fortigate IP>
The above will display all A records on the shell line.
answered Feb 19 at 20:51
boardriderboardrider
2902719
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397664%2fdig-command-does-not-show-a-records%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
dig local A
This will request only A records for the domain "local". I normally specify a server -
dig @server.name domain.name A
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
As you can see in the example I gave in the OP, the replay fordig local alldoes not include any A records. When I dodig local Aordig @192.168.1.99 local A, I get the same results as when I dodig local all, namely - no A records are displayed, besides;; QUESTION SECTION: ;local. IN A.
– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the commanddia test application dnsprox 8on the Fortigate 60D, not to mention that name resolution works in my LAN machines.
– boardrider
Jan 26 at 1:03
add a comment |
1
dig local A
This will request only A records for the domain "local". I normally specify a server -
dig @server.name domain.name A
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
As you can see in the example I gave in the OP, the replay fordig local alldoes not include any A records. When I dodig local Aordig @192.168.1.99 local A, I get the same results as when I dodig local all, namely - no A records are displayed, besides;; QUESTION SECTION: ;local. IN A.
– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the commanddia test application dnsprox 8on the Fortigate 60D, not to mention that name resolution works in my LAN machines.
– boardrider
Jan 26 at 1:03
add a comment |
1
1
1
dig local A
This will request only A records for the domain "local". I normally specify a server -
dig @server.name domain.name A
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
dig local A
This will request only A records for the domain "local". I normally specify a server -
dig @server.name domain.name A
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
answered Jan 23 at 22:14
davidgodavidgo
44.3k75292
44.3k75292
As you can see in the example I gave in the OP, the replay fordig local alldoes not include any A records. When I dodig local Aordig @192.168.1.99 local A, I get the same results as when I dodig local all, namely - no A records are displayed, besides;; QUESTION SECTION: ;local. IN A.
– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the commanddia test application dnsprox 8on the Fortigate 60D, not to mention that name resolution works in my LAN machines.
– boardrider
Jan 26 at 1:03
add a comment |
As you can see in the example I gave in the OP, the replay fordig local alldoes not include any A records. When I dodig local Aordig @192.168.1.99 local A, I get the same results as when I dodig local all, namely - no A records are displayed, besides;; QUESTION SECTION: ;local. IN A.
– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the commanddia test application dnsprox 8on the Fortigate 60D, not to mention that name resolution works in my LAN machines.
– boardrider
Jan 26 at 1:03
As you can see in the example I gave in the OP, the replay for
dig local all does not include any A records. When I do dig local A or dig @192.168.1.99 local A, I get the same results as when I do dig local all, namely - no A records are displayed, besides ;; QUESTION SECTION: ;local. IN A.– boardrider
Jan 24 at 20:25
As you can see in the example I gave in the OP, the replay for
dig local all does not include any A records. When I do dig local A or dig @192.168.1.99 local A, I get the same results as when I do dig local all, namely - no A records are displayed, besides ;; QUESTION SECTION: ;local. IN A.– boardrider
Jan 24 at 20:25
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
Wouldn't it then be reasonable to conclude that the A records have not been loaded for the zone?
– davidgo
Jan 24 at 23:16
However, I can see the A records with the command
dia test application dnsprox 8 on the Fortigate 60D, not to mention that name resolution works in my LAN machines.– boardrider
Jan 26 at 1:03
However, I can see the A records with the command
dia test application dnsprox 8 on the Fortigate 60D, not to mention that name resolution works in my LAN machines.– boardrider
Jan 26 at 1:03
add a comment |
0
The following is a workaround to get A records, but it's better than nothing:
(echo "diag test app dnsproxy 8"; echo "exit") | ssh -tt <user>@<Fortigate IP>
The above will display all A records on the shell line.
answered Feb 19 at 20:51
boardriderboardrider
2902719
add a comment |
0
The following is a workaround to get A records, but it's better than nothing:
(echo "diag test app dnsproxy 8"; echo "exit") | ssh -tt <user>@<Fortigate IP>
The above will display all A records on the shell line.
answered Feb 19 at 20:51
boardriderboardrider
2902719
add a comment |
0
0
0
The following is a workaround to get A records, but it's better than nothing:
(echo "diag test app dnsproxy 8"; echo "exit") | ssh -tt <user>@<Fortigate IP>
The above will display all A records on the shell line.
answered Feb 19 at 20:51
boardriderboardrider
2902719
The following is a workaround to get A records, but it's better than nothing:
(echo "diag test app dnsproxy 8"; echo "exit") | ssh -tt <user>@<Fortigate IP>
The above will display all A records on the shell line.
answered Feb 19 at 20:51
boardriderboardrider
2902719
answered Feb 19 at 20:51
boardriderboardrider
2902719
answered Feb 19 at 20:51
boardriderboardrider
2902719
answered Feb 19 at 20:51
boardriderboardrider
2902719
2902719
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397664%2fdig-command-does-not-show-a-records%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does your DNS software use syntax similar to a Bind9 zonefile? If so, did you update the serial? Did you reload the service after the data change?
– ivanivan
Jan 23 at 23:13