Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • dns-query.monitor problems

    1 answers - 1188 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Hey all,
    I've made a modification to dns-query.monitor to accept a config file
    for the underlying NET::DNS::Resolver. That works fine.
    However, no matter what I do, i cannot get it to stop adding my search
    path onto the domain I want to check. Because I want to check specific
    subdomains, they always pass.
    I've been trying to use
    recurse
    dnsrch
    options in my config file, but they don't seem to work. I will post a
    patch if anyone wants this once I figure out how to effectively make
    patch files :)
    If anyone else has done this that would be great.
    basically if I put in a bad domain name like www.bddddomain.com, it
    tries that, then tries it again, adding my local search domain and says
    its good.
    I thought dnsrch would have helped
    [yesterday our internet connection went down, thanks to Mon I knew about
    it about a minute after it happened and had our provider on the phone
    minutes before the first complaint rolled in had an e-mail out
    internally after that to head off the rest of them thanks mon]
    mon mailing list
    mon (AT) linux (DOT) kernel.org
  • No.1 | | 1936 bytes | |

    How about adding a trailing '.' to the name?

    I have dns_lut.monitor (lut = 'lookup time') which logs the response time.

    I thought that I had released it, but now I see that I have not added the
    pod man page, so that is why it was not released.

    Here are my options, with tiny documentation:

    "n|name=s" =\$NameToLookup, # FQDN should terminate with a "." to prevent recursion
    "v|verbose" =\$Verbose,
    "p|pingfirst" =\$PingFirst, # Don't try DNS lookup if down
    "t|timeout=i" =\$T,
    "T|alarmtime=i" =\$AlarmTime,
    "l|log=s" =\$LogFile,
    "d|debug" =\$Debug,

    Jon

    Thu, 19 2006, Bill Chmura wrote:

    Hey all,

    I've made a modification to dns-query.monitor to accept a config file
    for the underlying NET::DNS::Resolver. That works fine.

    However, no matter what I do, i cannot get it to stop adding my search
    path onto the domain I want to check. Because I want to check specific
    subdomains, they always pass.

    I've been trying to use

    recurse
    dnsrch

    options in my config file, but they don't seem to work. I will post a
    patch if anyone wants this once I figure out how to effectively make
    patch files :)

    If anyone else has done this that would be great.

    basically if I put in a bad domain name like www.bddddomain.com, it
    tries that, then tries it again, adding my local search domain and says
    its good.

    I thought dnsrch would have helped

    [yesterday our internet connection went down, thanks to Mon I knew about
    it about a minute after it happened and had our provider on the phone
    minutes before the first complaint rolled in had an e-mail out
    internally after that to head off the rest of them thanks mon]

    mon mailing list
    mon (AT) linux (DOT) kernel.org

    mon mailing list
    mon (AT) linux (DOT) kernel.org

Re: dns-query.monitor problems


max 4000 letters.
Your nickname that display:
In order to stop the spam: 5 + 4 =
QUESTION ON "Networking"

EMSDN.COM