Re: Debian/MIPS Jessie doesn't resolve hostnames?
Stuart Longland wrote:
>> gettimeofday({1432857770, 387273}, NULL) = 0
>> socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4
>> connect(4, {sa_family=AF_INET, sin_port=htons(53),
>> sin_addr=inet_addr("10.1.1.1")}, 16) = 0 gettimeofday({1432857770,
>> 393945}, NULL) = 0 poll([{fd=4, events=POLLOUT}], 1, 0) = 1 ([{fd=4,
>> revents=POLLOUT}]) send(4,
>> ">o\1\0\0\1\0\0\0\0\0\0\3www\6google\3com\2au\3v"..., 43, MSG_NOSIGNAL) =
>> 43 poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout) socket(PF_INET,
>> SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 5 connect(5, {sa_family=AF_INET,
>> sin_port=htons(53), sin_addr=inet_addr("10.87.130.254")}, 16) = 0
>> gettimeofday({1432857775, 414801}, NULL) = 0 poll([{fd=5,
>> events=POLLOUT}], 1, 0) = 1 ([{fd=5, revents=POLLOUT}]) send(5,
>> ">o\1\0\0\1\0\0\0\0\0\0\3www\6google\3com\2au\3v"..., 43, MSG_NOSIGNAL) =
>> 43 poll([{fd=5, events=POLLIN}], 1, 5000) = 0 (Timeout)
>> gettimeofday({1432857780, 431097}, NULL) = 0 poll([{fd=4,
>> events=POLLOUT}], 1, 0) = 1 ([{fd=4, revents=POLLOUT}]) send(4,
>> ">o\1\0\0\1\0\0\0\0\0\0\3www\6google\3com\2au\3v"..., 43, MSG_NOSIGNAL) =
>> 43 poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout)
>> gettimeofday({1432857785, 452744}, NULL) = 0 poll([{fd=5,
>> events=POLLOUT}], 1, 0) = 1 ([{fd=5, revents=POLLOUT}]) send(5,
>> ">o\1\0\0\1\0\0\0\0\0\0\3www\6google\3com\2au\3v"..., 43, MSG_NOSIGNAL) =
>> 43 poll([{fd=5, events=POLLIN}], 1, 5000) = 0 (Timeout) close(4)
>> = 0 close(5) = 0
>> write(2, "ping: unknown host www.google.co"..., 37) = 37
>> exit_group(2) = ?
>> +++ exited with 2 +++
>> root@qube:~#
>
> I'm tempted to try a newer kernel on the thing to see if that helps,
> since the stock Debian/MIPS Cobalt kernels are still at the 3.2 series.
What has the kernel to do with this precisely?
>
> By the sounds of things, it's something MIPS specific, so I might move
> this over to the Debian/MIPS mailing list next.
You get timeout on the nameservers you have in your resolv.conf file
10.1.1.1 and 10.87.130.254. Where are those values coming from?
Or perhaps could be some ipv4/6 issue.
To me it looks ok what its doing, you have to find out why you time out on
your DNS servers.
regards
Reply to: