| 1 |
> > |
| 2 |
> > Name resolution is name resolution, whether on the static line or |
| 3 |
> > the dynamic line. What difference does it make? |
| 4 |
> > |
| 5 |
> |
| 6 |
> If they are on different networks, one interface may not be able to |
| 7 |
> see the other interface, therefore not the name servers either. |
| 8 |
|
| 9 |
But if one /etc/resolv.conf dns points to what is served by one side, and |
| 10 |
another points to a DNS for the other side, then name resolution, regardless |
| 11 |
of the source, still works. |
| 12 |
|
| 13 |
The only conflict I see is if you have a different ip address for a host |
| 14 |
depending upon which nic you use - i.e. yahoo.com resolves to one address on |
| 15 |
the dhcp'd line, but a different address when resolved across the static |
| 16 |
line. Then you have issues. |
| 17 |
|
| 18 |
If the OP's problem was strictly the overwrite of /etc/resolv.conf by the |
| 19 |
dhcp app, he could disable the auto-overwrite of /etc/resolv.conf and use |
| 20 |
the scripting capabilities to massage the /etc/resolv.conf to include one or |
| 21 |
more of the dns servers provided by the dhcp process. |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives