I have a DNS test that is returning a NOT ok message, however a dig/nslookup against it is working just fine. I ran a bbcmd test and all I see for debug output is:
2006-08-15 22:52:54 Adding to combo msg: status dns01,[snip].dns red <!-- [flags:ordastLe] --> Tue Aug 15 22:51:36 2006 dns NOT ok
Is there more info I can get to tell me exactly why this test is failing?
On Tue, Aug 15, 2006 at 07:07:34PM -0400, Epp, Matthew Contractor PEO EIS AKO wrote:
I have a DNS test that is returning a NOT ok message, however a dig/nslookup against it is working just fine. I ran a bbcmd test and all I see for debug output is:
2006-08-15 22:52:54 Adding to combo msg: status dns01,[snip].dns red <!-- [flags:ordastLe] --> Tue Aug 15 22:51:36 2006 dns NOT ok
Is there more info I can get to tell me exactly why this test is failing?
The "dig" command equivalent of the standard dns test in Hobbit is
dig @your.server.name your.server.name A
i.e. an A record lookup for the DNS servers' own hostname.
So - does that work?
Regards, Henrik
participants (2)
-
henrik@hswn.dk
-
matthew.epp@us.army.mil