[Debian-l10n-devel] News about churro?

César Gómez Martín cesar.gomez at gmail.com
Tue Sep 29 08:38:01 UTC 2009


On Tue, Sep 29, 2009 at 10:34 AM, Michael Bramer <grisu at deb-support.de> wrote:
>
>
> César Gómez Martín schrieb:
>>
>> On Tue, Sep 29, 2009 at 9:42 AM, César Gómez Martín
>> <cesar.gomez at gmail.com> wrote:
>>>
>>> On Tue, Sep 29, 2009 at 9:40 AM, Michael Bramer <grisu at deb-support.de>
>>> wrote:
>>>>
>>>> Nicolas François schrieb:
>>>>>
>>>>> Hi César,
>>>>>
>>>>> On Mon, Sep 28, 2009 at 09:19:35AM +0200, César Gómez Martín wrote:
>>>>>>
>>>>>> Try now.
>>>>>>
>>>>>> The Junta of Extremadura is using a new firewall and we are having
>>>>>
>>>>> I could successfully connect to churro by ssh.
>>>>>
>>>>> It seems however that churro cannot resolve any host.
>>>>> 'dig www.google.es' results in a timeout.
>>>>>
>>>>> Was there any changes in the DNS setup?
>>>>
>>>> The firewall is blocking dns...
>>>>
>>>>
>>>> grisu at churro:~$ ping 217.69.73.2
>>>> PING 217.69.73.2 (217.69.73.2) 56(84) bytes of data.
>>>> 64 bytes from 217.69.73.2: icmp_seq=1 ttl=53 time=52.2 ms
>>>> ^C
>>>> --- 217.69.73.2 ping statistics ---
>>>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>>>> rtt min/avg/max/mdev = 52.240/52.240/52.240/0.000 ms
>>>> grisu at churro:~$ dig www.webmotive.net @217.69.73.2
>>>>
>>>> ; <<>> DiG 9.5.1-P3 <<>> www.webmotive.net @217.69.73.2
>>>> ;; global options:  printcmd
>>>> ;; connection timed out; no servers could be reached
>>>>
>>>>
>>>> dig is working outsite from churro.
>>>>
>>>> can you open the firewall?
>>>
>>> I will ping the Firewall man today.
>>>
>>> Sorry for the inconveniences :(
>>
>> They say all the ports are open.
>>
>> What is the DNS configuration of churro? (I am in Trujillo and my ssh
>> key is not in the authorized_keys, so I can not access churro from).
>>
>
> dig is not working... he know, that dns is using udp and tcp?
>
> the dns config:
> grisu at churro:~$ cat /etc/resolv.conf
> nameserver 62.42.230.24
> nameserver 62.42.63.52
> nameserver 62.81.16.129

Please, try to use 62.175.249.101 and 102 as DNS servers. I think that
should fix the problem.

Best regards,
César.



More information about the Debian-l10n-devel mailing list