[64studio-devel] quick network question DNS issue

Nate figlar sonorone at gmail.com
Wed May 2 15:29:53 UTC 2007


hey all good news,
ok as of Daniel James suggestion which I came to first I got a
workaround that is going good. it does still put the old bad addresses
underneath but still works good. now the only other question is I
tried to get the second DNS (backup) in there and for some reason it
didn't work could someone help me with the proper syntax. I have tried
two methods:

let's say our dns address are primary 127.0.0.2 and secondary of 127.0.0.3.

first I did this line

prepend domain-name-servers 127.0.0.2 127.0.0.3;

which did nothing but kept bad addresses.

now the second method was as follows

prepend domain-name-servers 127.0.0.2;
prepend domain-name-servers 127.0.0.3;

which gave me the primary but no secondary. like I said it does have
me running for now but if someone could let me in on what I am doing
wrong here I would be most appreciative. I just feel a little better
about knowing that secondary is there.

again thanks for helping me out
nate

On 5/2/07, Daniel James <daniel at 64studio.com> wrote:
> Hi Tim, hi Nate,
>
> > You should be able to edit /etc/resolv.conf by hand, but in my case,
> > this gets overwritten every time the network gets restarted.
>
> If dhclient is running, that's the correct behaviour. For example if you
> were a mobile user, you would want DNS settings to be updated as you
> moved between networks.
>
> There's a long discussion of the problem in the comments section here:
>
> http://www.debian-administration.org/articles/254
>
> Simplest solution: in the file /etc/dhclient.conf you should see a line
> like this:
>
> #prepend domain-name-servers 127.0.0.1;
>
> Uncomment this line and set the IP address of your DNS, then restart
> your network. dhclient should now honour the prepend statement when it
> writes the new /etc/resolv.conf file.
>
> Cheers!
>
> Daniel
>



More information about the 64studio-devel mailing list