[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wget in cron issue with dns resolution of local server
From: |
Tim Rühsen |
Subject: |
Re: wget in cron issue with dns resolution of local server |
Date: |
Tue, 17 Dec 2019 15:36:19 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 |
Hi,
are you sure that " and * are not somehow removed / expanded ?
To test, put the wget command into a shell script and start that script
in the crontab. Does this make a difference ?
Regards, Tim
On 12/17/19 2:55 PM, Álvaro Pinel Bueno wrote:
> Hello,
>
> I realized using wget secheduled in cron always ask to my dns
> server local-hostname resolution.
>
> If I try in bash it doesn't happen but in root cron I receive in my dns
> server at first the resolution of the hostname of the host with the cron
> scheduled and after the resolution of the domain indicated in the
> wget command.
>
> For example:
>
> *alv4ro@dummy# crontab -l*
> *# m h dom mon dow command*
> ** * * * * **/usr/bin/wget -q --no-check-certificate -O -
> --user-agent=WgetDummy/1.1 --post-data
> "user=example&password=passexample&host=domain.com
> <http://domain.com>&ip=" "https://otherdomain.com/plain/
> <https://otherdomain.com/plain/>"*
>
> In my dns server I receive:
> *1. dummy resolution*
> *2. otherdomain.com <http://otherdomain.com> resolution*
>
> It's that ok?
>
> Is there any way to disable this behavior?
>
> Thanks in advance,
>
> alv4ro.
>
signature.asc
Description: OpenPGP digital signature