| 1 |
Zac Slade wrote: |
| 2 |
> On Friday 26 May 2006 08:25, Alexander Skwar wrote: |
| 3 |
|
| 4 |
>> But I wonder what this DNSDOMAIN setting in /etc/conf.d/domainname is |
| 5 |
>> supposed to do. Because of |
| 6 |
> It sets the domain in /etc/resolv.conf |
| 7 |
|
| 8 |
No, it doesn't. |
| 9 |
|
| 10 |
>> # When setting up resolv.conf, what should take precedence? |
| 11 |
>> # If you wish to always override DHCP/whatever, set this to 1. |
| 12 |
>> OVERRIDE=1 |
| 13 |
>> |
| 14 |
>> I thought that this setting would have an effect. Seems not so... |
| 15 |
> This will determin whether DHCP will be allowed to replace your domain |
| 16 |
> statement in /etc/resolv.conf. |
| 17 |
|
| 18 |
That's not what happens. |
| 19 |
|
| 20 |
alexander@blatt ~ $ grep -v -e '#' -e '^$' /etc/conf.d/domainname |
| 21 |
OVERRIDE=1 |
| 22 |
DNSDOMAIN="bei.digitalprojects.com" |
| 23 |
NISDOMAIN="bei.digitalprojects.com" |
| 24 |
|
| 25 |
alexander@blatt ~ $ cat /etc/resolv.conf |
| 26 |
# Generated by dhcpcd for interface ath0 |
| 27 |
search bei.digitalprojects.com |
| 28 |
nameserver 192.168.1.1 |
| 29 |
nameserver 195.202.32.79 |
| 30 |
nameserver 82.207.232.1 |
| 31 |
nameserver 213.160.0.1 |
| 32 |
|
| 33 |
> I hope this clears it up. |
| 34 |
|
| 35 |
Nope :( |
| 36 |
|
| 37 |
Alexander Skwar |
| 38 |
-- |
| 39 |
Q: What happens when four WASPs find themselves in the same room? |
| 40 |
A: A dinner party. |
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives