1 |
2013/8/12 Alan McKinnon <alan.mckinnon@×××××.com>: |
2 |
> On 12/08/2013 09:13, gevisz wrote: |
3 |
>> The response of the first router contained an error that prevented all the |
4 |
>> other applications to use it, the system knew about it (for example from |
5 |
>> the output of the host utility) but, nevertheless did not proceeded with |
6 |
>> the next router listed in resolv.conf. |
7 |
>> |
8 |
>> I do undersand that this may be because of the layered structure of the |
9 |
>> networked software. But, nevertheless, I think that something is fundamentally |
10 |
>> wrong with this. |
11 |
> |
12 |
> What kind of error did you get? |
13 |
|
14 |
As I have already wrote it earlier, with three different DNS in |
15 |
/etc/resolv.conf and /etc/conf.d/net files, the host utility correctly |
16 |
reported IP address of a site (eg, www.google.com) but added |
17 |
the following message: |
18 |
;; Warning: query response not set |
19 |
|
20 |
With only the first (my local DNS) in /etc/resolv.conf and |
21 |
/etc/conf.d/net files, |
22 |
the output of the host utility was as follows: |
23 |
|
24 |
# host www.google.com |
25 |
www.google.com has address 74.125.232.52 |
26 |
www.google.com has address 74.125.232.48 |
27 |
www.google.com has address 74.125.232.49 |
28 |
www.google.com has address 74.125.232.50 |
29 |
www.google.com has address 74.125.232.51 |
30 |
;; Warning: query response not set |
31 |
;; Warning: query response not set |
32 |
Host www.google.com not found: 4(NOTIMP) |
33 |
|
34 |
In both cases above no internet application (eg, links or firefox) |
35 |
could convert site names to IP adresses and only after deleting |
36 |
the first (local) DNS from /etc/resolv.conf and /etc/conf.d/net files, |
37 |
internet applications started to work as expected (and the host |
38 |
utility, in this case, returned no error or warning message) |
39 |
|
40 |
That have proved to myself that |
41 |
|
42 |
"The response of the first router contained an error |
43 |
that prevented all the other applications to use it, |
44 |
the system knew about it (for example from |
45 |
the output of the host utility) but, nevertheless, |
46 |
did not proceeded with the next router listed in |
47 |
resolv.conf [or /etc/conf.d/net]. |
48 |
I do undersand that this may be because of |
49 |
the layered structure of the networked software. |
50 |
But, nevertheless, I think that something is fundamentally |
51 |
wrong with this." |
52 |
|
53 |
> If complete garbage came back, I'm not sure what the resolver does with |
54 |
> that (oddly enough, I never tested that) |
55 |
> |
56 |
> The more usual case is you get a proper DNS result of NXDOMAIN which |
57 |
> indicates the query is valid, but the entry is not in DNS. It's |
58 |
> pointless trying another cache as per DNS, they should all then return |
59 |
> that result. |
60 |
> |
61 |
> This is why the router did not try the other entries in resolv.conf - |
62 |
> that usually only happens when a cache does not respond. So the |
63 |
> behaviour you saw is probably correct albeit not the behaviour you wanted. |
64 |
> |
65 |
> |
66 |
> -- |
67 |
> Alan McKinnon |
68 |
> alan.mckinnon@×××××.com |
69 |
> |
70 |
> |