Question about dns test
list Michael Lowery
I've read the manpage, but I don't understand this test. I thought I could use this to test if an A record exists for a certain host. For example: Host=mail.domain.com in the bb-hosts: 1.2.3.4 mail.domain.com # dns=A:mail.domain.com The test seems to be querying mail.domain.com com for the record, not querying the nameservers for the hobbit machine set in resolv.conf. Am I just wrong about what this test does? Thanks, Michael
list Terry Barnes
user-89d72f0c2e3d@xymon.invalid 4/15/05 5:41:41 PM >>>
▸
I've read the manpage, but I don't understand this test. I thought I could use this to test if an A record exists for a certain host. For example: Host=mail.domain.com in the bb-hosts: 1.2.3.4 mail.domain.com # dns=A:mail.domain.com The test seems to be querying mail.domain.com com for the record, not querying the nameservers for the hobbit machine set in resolv.conf.
Am
I just wrong about what this test does? Thanks, Michael
I have this setup and it works for me - not using an a record lookup though - maybe it doesn't like the uppercase "A". 1.2.3.4 my.domain.com # dns=ns:domain.com,ns:domain.org,mx:domain.org I get the nameservers for both the domain.com and domain.org and the mx record for domain.org returned. Hope this helps. Terry Barnes Siemens Com @ HFHS XXX-XXX-XXXX (Office) XXX-XXX-XXXX (Cellular) XXX-XXX-XXXX (Fax) user-34ea5ff61ded@xymon.invalid (Text Pager) user-0e29285d9a67@xymon.invalid ============================================================================== HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com. Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. ==============================================================================
list Michael Lowery
Sorry, I "uppercased" the "a" in the e-mail, but it's actually not uppercase in bb-hosts. I guess I don't understand the test. I was hoping that for any host, I could perform a lookup of its own A record on the dns servers of my choosing (or at least use the dns servers from resolv.conf). The host where I've placed the DNS test is not a DNS server, but I would like to verify that it's "A" record does exist. The reason I want this is that we have some customers that from time-to-time will fail to renew their domain-name, or make a DNS change and either change the IP address for a host or drop the hostname all together. I would like to use this test, or another, to gather the DNS information for the A record of a particular host so that I can verify or deny that this is a problem. Any suggestions? Currently I'm attempting to do it this way, but it doesn't do what I'm expecting: Snip from bb-hosts: 1.2.3.4 Host1.domain.com # dns=a:host1.domain.com I would expect this to lookup the "A" record for the host, host1.domain.com, from the DNS server in resolv.conf, but it seems to instead try to lookup the record from host1.domain.com, which is not a DNS server. Thanks! Michael
▸
-----Original Message----- From: Terry Barnes [mailto:user-0e29285d9a67@xymon.invalid] Sent: Friday, April 15, 2005 7:08 PM To: user-ae9b8668bcde@xymon.invalid Subject: Re: [hobbit] Question about dns test I have this setup and it works for me - not using an a record lookup though - maybe it doesn't like the uppercase "A". 1.2.3.4 my.domain.com # dns=ns:domain.com,ns:domain.org,mx:domain.org I get the nameservers for both the domain.com and domain.org and the mx record for domain.org returned. Hope this helps. Terry Barnes Siemens Com @ HFHS XXX-XXX-XXXX (Office) XXX-XXX-XXXX (Cellular) XXX-XXX-XXXX (Fax) user-34ea5ff61ded@xymon.invalid (Text Pager) user-0e29285d9a67@xymon.invalid ======================================================================== ====== HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com. Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. ======================================================================== ======
list Henrik Størner
▸
On Sun, Apr 17, 2005 at 09:28:22AM -0500, Lowery, Michael wrote:
I guess I don't understand the test. I was hoping that for any host, I could perform a lookup of its own A record on the dns servers of my choosing (or at least use the dns servers from resolv.conf). The host where I've placed the DNS test is not a DNS server, but I would like to verify that it's "A" record does exist.
OK, that's a different kind of test. The "dns" test is designed to verify that a DNS server is running on the host that has this test defined.
▸
The reason I want this is that we have some customers that from time-to-time will fail to renew their domain-name, or make a DNS change and either change the IP address for a host or drop the hostname all together. I would like to use this test, or another, to gather the DNS information for the A record of a particular host so that I can verify or deny that this is a problem.
Sounds like a reasonable thing to do, especially if you're hosting for people without controlling their DNS setup. I'll see if I can work that into a future version. We've got all of the bits and pieces needed to implement it, I just have to put them all together. Regards, Henrik
list Daniel J McDonald
▸
On Sun, 2005-04-17 at 17:04 +0200, Henrik Stoerner wrote:
On Sun, Apr 17, 2005 at 09:28:22AM -0500, Lowery, Michael wrote:I guess I don't understand the test. I was hoping that for any host, I could perform a lookup of its own A record on the dns servers of my choosing (or at least use the dns servers from resolv.conf). The host where I've placed the DNS test is not a DNS server, but I would like to verify that it's "A" record does exist.OK, that's a different kind of test. The "dns" test is designed to verify that a DNS server is running on the host that has this test defined.
But you have made it extensible enough to do what he wants. I check my records using this syntax: 0.0.0.0 ae-dns3.electric.ci.austin.tx.us # dig=SOA:austinenergy.com,SOA:electric.ci.austin.tx.us Yes, his DNS servers might end up with a rather long list, but the ability to see if a particular record is resolvable is present.
▸
The reason I want this is that we have some customers that from time-to-time will fail to renew their domain-name, or make a DNS change and either change the IP address for a host or drop the hostname all together. I would like to use this test, or another, to gather the DNS information for the A record of a particular host so that I can verify or deny that this is a problem.Sounds like a reasonable thing to do, especially if you're hosting for people without controlling their DNS setup. I'll see if I can work that into a future version. We've got all of the bits and pieces needed to implement it, I just have to put them all together. Regards, Henrik