I installed dnsmasq to run DNS and DHCP servers on my little home network of 4
PCs and a couple of laptops, and everything was going fine, internet browsing,
ssh, ftp by IP address etc.

Now I am trying to get DNS to work for local machines but it won't co-operate. I
spent the last couple of hours pouring over HOWTOs and FAQs trying to work out
the problem but I'm stuck with a few errors messages which I suspect point to
something totally obvious to those in the know.

My server isengard runs dnsmasq to provide the dhcp clients. However it doesn't
recognise any internal network domain name:

isengard:~# hostname
isengard
isengard:~# hostname --fqdn
hostname: Unknown host
isengard:~# nslookup gondor
Server: 194.74.65.69
Address: 194.74.65.69#53

** server can't find gondor: NXDOMAIN



I worked out the domain name should go into /etc/resolv.conf (
http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that this is
under the control of something else.

isengard is running etch, installed from scratch, so I figured I made an error
in the config setup.

On my main client, gondor, I have a similar problem. Plus programs such as xfce
give me warning messages that I should put my hostname in my /etc/hosts file.

Any insights would be welcome,

Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 12:39:56PM +0100, Adam Hardy wrote:
> I installed dnsmasq to run DNS and DHCP servers on my little home network
> of 4 PCs and a couple of laptops, and everything was going fine, internet
> browsing, ssh, ftp by IP address etc.
>
> Now I am trying to get DNS to work for local machines but it won't
> co-operate. I spent the last couple of hours pouring over HOWTOs and FAQs
> trying to work out the problem but I'm stuck with a few errors messages
> which I suspect point to something totally obvious to those in the know.

Please send us your /etc/hosts file. Every box needs a minimal
/etc/hosts file with at least its own hostname (though I'v never used
DHCP). The box running dnsmasq should have all the hosts on your
network listed in /etc/hosts for dnsmasq to read.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 12:39:56PM +0100, Adam Hardy wrote:
> I installed dnsmasq to run DNS and DHCP servers on my little home network
> of 4 PCs and a couple of laptops, and everything was going fine, internet
> browsing, ssh, ftp by IP address etc.
>
> Now I am trying to get DNS to work for local machines but it won't
> co-operate. I spent the last couple of hours pouring over HOWTOs and FAQs
> trying to work out the problem but I'm stuck with a few errors messages
> which I suspect point to something totally obvious to those in the know.

Please send us your /etc/hosts file. Every box needs a minimal
/etc/hosts file with at least its own hostname (though I'v never used
DHCP). The box running dnsmasq should have all the hosts on your
network listed in /etc/hosts for dnsmasq to read.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Douglas Allan Tutty on 06/08/07 14:27, wrote:
> On Mon, Aug 06, 2007 at 12:39:56PM +0100, Adam Hardy wrote:
>> I installed dnsmasq to run DNS and DHCP servers on my little home network
>> of 4 PCs and a couple of laptops, and everything was going fine, internet
>> browsing, ssh, ftp by IP address etc.
>>
>> Now I am trying to get DNS to work for local machines but it won't
>> co-operate. I spent the last couple of hours pouring over HOWTOs and FAQs
>> trying to work out the problem but I'm stuck with a few errors messages
>> which I suspect point to something totally obvious to those in the know.
>
> Please send us your /etc/hosts file. Every box needs a minimal
> /etc/hosts file with at least its own hostname (though I'v never used
> DHCP). The box running dnsmasq should have all the hosts on your
> network listed in /etc/hosts for dnsmasq to read.

adam@gondor:~$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

So I should put gondor in there on the same line as the localhost?

And on the dnsmasq box it's the same. I can enter the IP address of the box's
NIC on the internal network into /etc/hosts because it's fixed, but all the DHCP
clients?





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 06:50:21PM +0100, Adam Hardy wrote:
> Douglas Allan Tutty on 06/08/07 14:27, wrote:
> >On Mon, Aug 06, 2007 at 12:39:56PM +0100, Adam Hardy wrote:
> >>I installed dnsmasq to run DNS and DHCP servers on my little home network
> >>of 4 PCs and a couple of laptops, and everything was going fine, internet
> >>browsing, ssh, ftp by IP address etc.
> >>
> >>Now I am trying to get DNS to work for local machines but it won't
> >>co-operate. I spent the last couple of hours pouring over HOWTOs and FAQs
> >>trying to work out the problem but I'm stuck with a few errors messages
> >>which I suspect point to something totally obvious to those in the know.
> >
> >Please send us your /etc/hosts file. Every box needs a minimal
> >/etc/hosts file with at least its own hostname (though I'v never used
> >DHCP). The box running dnsmasq should have all the hosts on your
> >network listed in /etc/hosts for dnsmasq to read.
>
> adam@gondor:~$ cat /etc/hosts
> 127.0.0.1 localhost localhost.localdomain
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>
> So I should put gondor in there on the same line as the localhost?
>
> And on the dnsmasq box it's the same. I can enter the IP address of the
> box's NIC on the internal network into /etc/hosts because it's fixed, but
> all the DHCP clients?
>

You should only have to put your hosts in the /etc/hosts file on the
dnsmasq box. No, you should not touch the 127.0.0.1 line. They should
go on their own line, one per IP. I don't know about the DHCP clients.

Doug.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Aug 6, 2007, at 10:50 AM, Adam Hardy wrote:
>> Please send us your /etc/hosts file. Every box needs a minimal
>> /etc/hosts file with at least its own hostname (though I'v never used
>> DHCP). The box running dnsmasq should have all the hosts on your
>> network listed in /etc/hosts for dnsmasq to read.
>
> adam@gondor:~$ cat /etc/hosts
> 127.0.0.1 localhost localhost.localdomain
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>
> So I should put gondor in there on the same line as the localhost?
>
> And on the dnsmasq box it's the same. I can enter the IP address of
> the box's NIC on the internal network into /etc/hosts because it's
> fixed, but all the DHCP clients?

If the machine has a fixed IP, you want that on the /etc/hosts line
for its name, generally speaking. Putting it on the same line as
127.0.0.1 can confuse some software.

So if you have a machine named foo.bar.net with an IP of
192.168.127.50, the /etc/hosts entry would look like this:

192.168.127.50 foo.bar.net foo

This associates the names "foo.bar.net" and "foo" with that IP.

I'm not entirely clear on what you're trying to do, but dnsmasq can
probably serve DNS records for your DHCP clients if you configure it
properly. If you explain a little more what you're trying to do and
what's not working I might be able to more.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

David Brodbeck on 06/08/07 19:11, wrote:
> On Aug 6, 2007, at 10:50 AM, Adam Hardy wrote:
>>
>> adam@gondor:~$ cat /etc/hosts
>> 127.0.0.1 localhost localhost.localdomain
>>
>> # The following lines are desirable for IPv6 capable hosts
>> ::1 ip6-localhost ip6-loopback
>> fe00::0 ip6-localnet
>> ff00::0 ip6-mcastprefix
>> ff02::1 ip6-allnodes
>> ff02::2 ip6-allrouters
>> ff02::3 ip6-allhosts
>>
>> So I should put gondor in there on the same line as the localhost?
>>
>> And on the dnsmasq box it's the same. I can enter the IP address of
>> the box's NIC on the internal network into /etc/hosts because it's
>> fixed, but all the DHCP clients?
>
> If the machine has a fixed IP, you want that on the /etc/hosts line for
> its name, generally speaking. Putting it on the same line as 127.0.0.1
> can confuse some software.
>
> So if you have a machine named foo.bar.net with an IP of 192.168.127.50,
> the /etc/hosts entry would look like this:
>
> 192.168.127.50 foo.bar.net foo
>
> This associates the names "foo.bar.net" and "foo" with that IP.
>
> I'm not entirely clear on what you're trying to do, but dnsmasq can
> probably serve DNS records for your DHCP clients if you configure it
> properly. If you explain a little more what you're trying to do and

I'm trying to enable DNS on my internal network. I think you missed the first
email I sent but this is one of the main symptoms:


isengard:~# hostname
isengard
isengard:~# hostname --fqdn
hostname: Unknown host
isengard:~# nslookup gondor
Server: 194.74.65.69
Address: 194.74.65.69#53

** server can't find gondor: NXDOMAIN

It seems to me that my internal network does not have domain configured properly
and that this is causing dnsmasq to try to look it up on the internet, but I
can't find any info on it.

On my dnsmasq/dhcp server, I can put the IP for the internal NIC into the
/etc/hosts. However I can't do that for the DHCP clients. Perhaps this is purely
down to a dnsmasq config issue but I think that it needs me to change something
more basic such as the domain, to something like 'localdomain'.

Other symptoms include xfce showing this error:

Could not look up internet address for gondor. It may be possible to correct the
problem by adding gondor to the file /etc/hosts.



Thanks
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

David Brodbeck on 06/08/07 19:11, wrote:
> On Aug 6, 2007, at 10:50 AM, Adam Hardy wrote:
>>
>> adam@gondor:~$ cat /etc/hosts
>> 127.0.0.1 localhost localhost.localdomain
>>
>> # The following lines are desirable for IPv6 capable hosts
>> ::1 ip6-localhost ip6-loopback
>> fe00::0 ip6-localnet
>> ff00::0 ip6-mcastprefix
>> ff02::1 ip6-allnodes
>> ff02::2 ip6-allrouters
>> ff02::3 ip6-allhosts
>>
>> So I should put gondor in there on the same line as the localhost?
>>
>> And on the dnsmasq box it's the same. I can enter the IP address of
>> the box's NIC on the internal network into /etc/hosts because it's
>> fixed, but all the DHCP clients?
>
> If the machine has a fixed IP, you want that on the /etc/hosts line for
> its name, generally speaking. Putting it on the same line as 127.0.0.1
> can confuse some software.
>
> So if you have a machine named foo.bar.net with an IP of 192.168.127.50,
> the /etc/hosts entry would look like this:
>
> 192.168.127.50 foo.bar.net foo
>
> This associates the names "foo.bar.net" and "foo" with that IP.
>
> I'm not entirely clear on what you're trying to do, but dnsmasq can
> probably serve DNS records for your DHCP clients if you configure it
> properly. If you explain a little more what you're trying to do and

I'm trying to enable DNS on my internal network. I think you missed the first
email I sent but this is one of the main symptoms:


isengard:~# hostname
isengard
isengard:~# hostname --fqdn
hostname: Unknown host
isengard:~# nslookup gondor
Server: 194.74.65.69
Address: 194.74.65.69#53

** server can't find gondor: NXDOMAIN

It seems to me that my internal network does not have domain configured properly
and that this is causing dnsmasq to try to look it up on the internet, but I
can't find any info on it.

On my dnsmasq/dhcp server, I can put the IP for the internal NIC into the
/etc/hosts. However I can't do that for the DHCP clients. Perhaps this is purely
down to a dnsmasq config issue but I think that it needs me to change something
more basic such as the domain, to something like 'localdomain'.

Other symptoms include xfce showing this error:

Could not look up internet address for gondor. It may be possible to correct the
problem by adding gondor to the file /etc/hosts.



Thanks
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> I installed dnsmasq to run DNS and DHCP servers on my little home network
of
> 4
> PCs and a couple of laptops, and everything was going fine, internet
> browsing,
> ssh, ftp by IP address etc.
>
> Now I am trying to get DNS to work for local machines but it won't co-
> operate. I
> spent the last couple of hours pouring over HOWTOs and FAQs trying to work
> out
> the problem but I'm stuck with a few errors messages which I suspect point
to
> something totally obvious to those in the know.
>
> My server isengard runs dnsmasq to provide the dhcp clients. However it
> doesn't
> recognise any internal network domain name:
>
> isengard:~# hostname
> isengard
> isengard:~# hostname --fqdn
> hostname: Unknown host
> isengard:~# nslookup gondor
> Server: 194.74.65.69
> Address: 194.74.65.69#53
>
> ** server can't find gondor: NXDOMAIN
>
>
>
> I worked out the domain name should go into /etc/resolv.conf (
> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
this
> is
> under the control of something else.

The domain name should go into /etc/resolv.conf
You also have to assign the first nameserver to be _your_ nameserver and not
your ISP's.

# cat /etc/resolv.conf
search isengard.net
nameserver 127.0.0.1
nameserver ...
nameserver ...

>
> isengard is running etch, installed from scratch, so I figured I made an
> error
> in the config setup.
>
> On my main client, gondor, I have a similar problem. Plus programs such as
> xfce
> give me warning messages that I should put my hostname in my /etc/hosts
file.
>
> Any insights would be welcome,
>
> Adam

Good luck, Rein


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>> doesn't
>> recognise any internal network domain name:
>>
>> isengard:~# hostname
>> isengard
>> isengard:~# hostname --fqdn
>> hostname: Unknown host
>> isengard:~# nslookup gondor
>> Server: 194.74.65.69
>> Address: 194.74.65.69#53
>>
>> ** server can't find gondor: NXDOMAIN
>>
>>
>>
>> I worked out the domain name should go into /etc/resolv.conf (
>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
> this
>> is
>> under the control of something else.
>
> The domain name should go into /etc/resolv.conf
> You also have to assign the first nameserver to be _your_ nameserver and not
> your ISP's.
>
> # cat /etc/resolv.conf
> search isengard.net
> nameserver 127.0.0.1
> nameserver ...
> nameserver ...

Something is rewriting my resolv.conf at least every minute. I suspected it must
be dnsmasq attempting to do the DNS but I just stopped dnsmasq, and yet
resolv.conf is still being updated. I had a look over my ps output but dont see
anything that could be controlling resolv.conf.

This is the only entry in it:

nameserver 194.74.65.69

which is the British Telecom DNS.

Thanks
Adam





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>> doesn't
>> recognise any internal network domain name:
>>
>> isengard:~# hostname
>> isengard
>> isengard:~# hostname --fqdn
>> hostname: Unknown host
>> isengard:~# nslookup gondor
>> Server: 194.74.65.69
>> Address: 194.74.65.69#53
>>
>> ** server can't find gondor: NXDOMAIN
>>
>>
>>
>> I worked out the domain name should go into /etc/resolv.conf (
>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
> this
>> is
>> under the control of something else.
>
> The domain name should go into /etc/resolv.conf
> You also have to assign the first nameserver to be _your_ nameserver and not
> your ISP's.
>
> # cat /etc/resolv.conf
> search isengard.net
> nameserver 127.0.0.1
> nameserver ...
> nameserver ...

Something is rewriting my resolv.conf at least every minute. I suspected it must
be dnsmasq attempting to do the DNS but I just stopped dnsmasq, and yet
resolv.conf is still being updated. I had a look over my ps output but dont see
anything that could be controlling resolv.conf.

This is the only entry in it:

nameserver 194.74.65.69

which is the British Telecom DNS.

Thanks
Adam





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Aug 7, 2007, at 3:40 PM, Adam Hardy wrote:
> Something is rewriting my resolv.conf at least every minute. I
> suspected it must be dnsmasq attempting to do the DNS but I just
> stopped dnsmasq, and yet resolv.conf is still being updated. I had
> a look over my ps output but dont see anything that could be
> controlling resolv.conf.
>
> This is the only entry in it:
>
> nameserver 194.74.65.69
>
> which is the British Telecom DNS.

It's probably your DHCP client, but I'm not sure how to change that.
I don't currently have any Debian systems that get an IP dynamically.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Aug 7, 2007, at 3:40 PM, Adam Hardy wrote:
> Something is rewriting my resolv.conf at least every minute. I
> suspected it must be dnsmasq attempting to do the DNS but I just
> stopped dnsmasq, and yet resolv.conf is still being updated. I had
> a look over my ps output but dont see anything that could be
> controlling resolv.conf.
>
> This is the only entry in it:
>
> nameserver 194.74.65.69
>
> which is the British Telecom DNS.

It's probably your DHCP client, but I'm not sure how to change that.
I don't currently have any Debian systems that get an IP dynamically.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 7 Aug 2007, Adam Hardy wrote:

> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>>> doesn't
>>> recognise any internal network domain name:
>>>
>>> isengard:~# hostname
>>> isengard
>>> isengard:~# hostname --fqdn
>>> hostname: Unknown host
>>> isengard:~# nslookup gondor
>>> Server: 194.74.65.69
>>> Address: 194.74.65.69#53
>>>
>>> ** server can't find gondor: NXDOMAIN
>>>
>>>
>>>
>>> I worked out the domain name should go into /etc/resolv.conf (
>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>> this
>>> is
>>> under the control of something else.
>>
>> The domain name should go into /etc/resolv.conf
>> You also have to assign the first nameserver to be _your_ nameserver and
>> not
>> your ISP's.
>>
>> # cat /etc/resolv.conf
>> search isengard.net
>> nameserver 127.0.0.1
>> nameserver ...
>> nameserver ...
>
> Something is rewriting my resolv.conf at least every minute. I suspected it
> must be dnsmasq attempting to do the DNS but I just stopped dnsmasq, and yet
> resolv.conf is still being updated. I had a look over my ps output but dont
> see anything that could be controlling resolv.conf.
>
> This is the only entry in it:
>
> nameserver 194.74.65.69
>
> which is the British Telecom DNS.
>
> Thanks
> Adam
>

Do you have the resolvconf package installed?


-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 7 Aug 2007, Adam Hardy wrote:

> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>>> doesn't
>>> recognise any internal network domain name:
>>>
>>> isengard:~# hostname
>>> isengard
>>> isengard:~# hostname --fqdn
>>> hostname: Unknown host
>>> isengard:~# nslookup gondor
>>> Server: 194.74.65.69
>>> Address: 194.74.65.69#53
>>>
>>> ** server can't find gondor: NXDOMAIN
>>>
>>>
>>>
>>> I worked out the domain name should go into /etc/resolv.conf (
>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>> this
>>> is
>>> under the control of something else.
>>
>> The domain name should go into /etc/resolv.conf
>> You also have to assign the first nameserver to be _your_ nameserver and
>> not
>> your ISP's.
>>
>> # cat /etc/resolv.conf
>> search isengard.net
>> nameserver 127.0.0.1
>> nameserver ...
>> nameserver ...
>
> Something is rewriting my resolv.conf at least every minute. I suspected it
> must be dnsmasq attempting to do the DNS but I just stopped dnsmasq, and yet
> resolv.conf is still being updated. I had a look over my ps output but dont
> see anything that could be controlling resolv.conf.
>
> This is the only entry in it:
>
> nameserver 194.74.65.69
>
> which is the British Telecom DNS.
>
> Thanks
> Adam
>

Do you have the resolvconf package installed?


-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Jeff D on 08/08/07 00:34, wrote:
> On Tue, 7 Aug 2007, Adam Hardy wrote:
>> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>>>> doesn't recognise any internal network domain name:
>>>>
>>>> isengard:~# hostname
>>>> isengard
>>>> isengard:~# hostname --fqdn
>>>> hostname: Unknown host
>>>> isengard:~# nslookup gondor
>>>> Server: 194.74.65.69
>>>> Address: 194.74.65.69#53
>>>>
>>>> ** server can't find gondor: NXDOMAIN
>>>>
>>>>
>>>>
>>>> I worked out the domain name should go into /etc/resolv.conf (
>>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>>> this is under the control of something else.
>>>
>>> The domain name should go into /etc/resolv.conf
>>> You also have to assign the first nameserver to be _your_ nameserver
>>> and not your ISP's.
>>>
>>> # cat /etc/resolv.conf
>>> search isengard.net
>>> nameserver 127.0.0.1
>>> nameserver ...
>>> nameserver ...
>>
>> Something is rewriting my resolv.conf at least every minute. I
>> suspected it must be dnsmasq attempting to do the DNS but I just
>> stopped dnsmasq, and yet resolv.conf is still being updated. I had a
>> look over my ps output but dont see anything that could be controlling
>> resolv.conf.
>>
>> This is the only entry in it:
>>
>> nameserver 194.74.65.69
>>
>> which is the British Telecom DNS.
>
> Do you have the resolvconf package installed?

No. That looks like a culprit, but no. Not installed.

Checking out the dhclient3 and dhclient.conf man pages, it makes no reference to
resolv.conf but it does claim to be able to do dynamic DNS updates.

I would have to try disabling the dhclient3 NIC to test if it is this program
rewriting resolv.conf, but i have to wait until the others using the net have
finished.

How exactly would I set the domain name on the machine - the name I thought I'd
chosen when setting up the system from CD?

At the moment on this machine when I run 'hostname --domain' it returns nothing.

Thanks
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, 9 Aug 2007, Adam Hardy wrote:

> Jeff D on 08/08/07 00:34, wrote:
>> On Tue, 7 Aug 2007, Adam Hardy wrote:
>>> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>>>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>>>>> doesn't recognise any internal network domain name:
>>>>>
>>>>> isengard:~# hostname
>>>>> isengard
>>>>> isengard:~# hostname --fqdn
>>>>> hostname: Unknown host
>>>>> isengard:~# nslookup gondor
>>>>> Server: 194.74.65.69
>>>>> Address: 194.74.65.69#53
>>>>>
>>>>> ** server can't find gondor: NXDOMAIN
>>>>>
>>>>>
>>>>>
>>>>> I worked out the domain name should go into /etc/resolv.conf (
>>>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>>>> this is under the control of something else.
>>>>
>>>> The domain name should go into /etc/resolv.conf
>>>> You also have to assign the first nameserver to be _your_ nameserver and
>>>> not your ISP's.
>>>>
>>>> # cat /etc/resolv.conf
>>>> search isengard.net
>>>> nameserver 127.0.0.1
>>>> nameserver ...
>>>> nameserver ...
>>>
>>> Something is rewriting my resolv.conf at least every minute. I suspected
>>> it must be dnsmasq attempting to do the DNS but I just stopped dnsmasq,
>>> and yet resolv.conf is still being updated. I had a look over my ps output
>>> but dont see anything that could be controlling resolv.conf.
>>>
>>> This is the only entry in it:
>>>
>>> nameserver 194.74.65.69
>>>
>>> which is the British Telecom DNS.
>>
>> Do you have the resolvconf package installed?
>
> No. That looks like a culprit, but no. Not installed.
>
> Checking out the dhclient3 and dhclient.conf man pages, it makes no reference
> to resolv.conf but it does claim to be able to do dynamic DNS updates.
>
> I would have to try disabling the dhclient3 NIC to test if it is this program
> rewriting resolv.conf, but i have to wait until the others using the net have
> finished.
>
> How exactly would I set the domain name on the machine - the name I thought
> I'd chosen when setting up the system from CD?
>
> At the moment on this machine when I run 'hostname --domain' it returns
> nothing.
>
> Thanks
> Adam
>

to set the domain name, add it into /etc/hosts, for example:
127.0.0.1 localhost
127.0.1.1 mybox.mynet.net mybox

in /etc/hostname :
mybox

at start up /etc/init.d/hostname.sh runs, parses these and comes up the
domain name.

to turn off dhcp provided /etc/host info, edit /etc/dhcp3/dhclient.conf,
there is a line that starts with request. Remove domain-name-servers from
that list and dhcp wont supply it. If you read down further, you can
supply your own through the option variables.

for more dhcpclient goodness man dhclient.conf

hth,
jeff

-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, 9 Aug 2007, Adam Hardy wrote:

> Jeff D on 08/08/07 00:34, wrote:
>> On Tue, 7 Aug 2007, Adam Hardy wrote:
>>> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>>>> My server isengard runs dnsmasq to provide the dhcp clients. However it
>>>>> doesn't recognise any internal network domain name:
>>>>>
>>>>> isengard:~# hostname
>>>>> isengard
>>>>> isengard:~# hostname --fqdn
>>>>> hostname: Unknown host
>>>>> isengard:~# nslookup gondor
>>>>> Server: 194.74.65.69
>>>>> Address: 194.74.65.69#53
>>>>>
>>>>> ** server can't find gondor: NXDOMAIN
>>>>>
>>>>>
>>>>>
>>>>> I worked out the domain name should go into /etc/resolv.conf (
>>>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>>>> this is under the control of something else.
>>>>
>>>> The domain name should go into /etc/resolv.conf
>>>> You also have to assign the first nameserver to be _your_ nameserver and
>>>> not your ISP's.
>>>>
>>>> # cat /etc/resolv.conf
>>>> search isengard.net
>>>> nameserver 127.0.0.1
>>>> nameserver ...
>>>> nameserver ...
>>>
>>> Something is rewriting my resolv.conf at least every minute. I suspected
>>> it must be dnsmasq attempting to do the DNS but I just stopped dnsmasq,
>>> and yet resolv.conf is still being updated. I had a look over my ps output
>>> but dont see anything that could be controlling resolv.conf.
>>>
>>> This is the only entry in it:
>>>
>>> nameserver 194.74.65.69
>>>
>>> which is the British Telecom DNS.
>>
>> Do you have the resolvconf package installed?
>
> No. That looks like a culprit, but no. Not installed.
>
> Checking out the dhclient3 and dhclient.conf man pages, it makes no reference
> to resolv.conf but it does claim to be able to do dynamic DNS updates.
>
> I would have to try disabling the dhclient3 NIC to test if it is this program
> rewriting resolv.conf, but i have to wait until the others using the net have
> finished.
>
> How exactly would I set the domain name on the machine - the name I thought
> I'd chosen when setting up the system from CD?
>
> At the moment on this machine when I run 'hostname --domain' it returns
> nothing.
>
> Thanks
> Adam
>

to set the domain name, add it into /etc/hosts, for example:
127.0.0.1 localhost
127.0.1.1 mybox.mynet.net mybox

in /etc/hostname :
mybox

at start up /etc/init.d/hostname.sh runs, parses these and comes up the
domain name.

to turn off dhcp provided /etc/host info, edit /etc/dhcp3/dhclient.conf,
there is a line that starts with request. Remove domain-name-servers from
that list and dhcp wont supply it. If you read down further, you can
supply your own through the option variables.

for more dhcpclient goodness man dhclient.conf

hth,
jeff

-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Jeff D on 09/08/07 00:55, wrote:
> On Thu, 9 Aug 2007, Adam Hardy wrote:
>> Jeff D on 08/08/07 00:34, wrote:
>>> On Tue, 7 Aug 2007, Adam Hardy wrote:
>>>> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>>>>> My server isengard runs dnsmasq to provide the dhcp clients.
>>>>>> However it
>>>>>> doesn't recognise any internal network domain name:
>>>>>>
>>>>>> isengard:~# hostname
>>>>>> isengard
>>>>>> isengard:~# hostname --fqdn
>>>>>> hostname: Unknown host
>>>>>> isengard:~# nslookup gondor
>>>>>> Server: 194.74.65.69
>>>>>> Address: 194.74.65.69#53
>>>>>>
>>>>>> ** server can't find gondor: NXDOMAIN
>>>>>>
>>>>>> I worked out the domain name should go into /etc/resolv.conf (
>>>>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems
>>>>>> that
>>>>> this is under the control of something else.
>>>>>
>>>>> The domain name should go into /etc/resolv.conf
>>>>> You also have to assign the first nameserver to be _your_
>>>>> nameserver and not your ISP's.
>>>>>
>>>>> # cat /etc/resolv.conf
>>>>> search isengard.net
>>>>> nameserver 127.0.0.1
>>>>> nameserver ...
>>>>> nameserver ...
>>>>
>>>> Something is rewriting my resolv.conf at least every minute. I
>>>> suspected it must be dnsmasq attempting to do the DNS but I just
>>>> stopped dnsmasq, and yet resolv.conf is still being updated. I had a
>>>> look over my ps output but dont see anything that could be
>>>> controlling resolv.conf.
>>>>
>>>> This is the only entry in it:
>>>>
>>>> nameserver 194.74.65.69
>>>>
>>>> which is the British Telecom DNS.
>>>
>>> Do you have the resolvconf package installed?
>>
>> No. That looks like a culprit, but no. Not installed.
>>
>> Checking out the dhclient3 and dhclient.conf man pages, it makes no
>> reference to resolv.conf but it does claim to be able to do dynamic
>> DNS updates.
>>
>> I would have to try disabling the dhclient3 NIC to test if it is this
>> program rewriting resolv.conf, but i have to wait until the others
>> using the net have finished.
>>
>> How exactly would I set the domain name on the machine - the name I
>> thought I'd chosen when setting up the system from CD?
>>
>> At the moment on this machine when I run 'hostname --domain' it
>> returns nothing.
>
> to set the domain name, add it into /etc/hosts, for example:
> 127.0.0.1 localhost
> 127.0.1.1 mybox.mynet.net mybox
>
> in /etc/hostname :
> mybox
>
> at start up /etc/init.d/hostname.sh runs, parses these and comes up the
> domain name.
>
> to turn off dhcp provided /etc/host info, edit /etc/dhcp3/dhclient.conf,
> there is a line that starts with request. Remove domain-name-servers
> from that list and dhcp wont supply it. If you read down further, you
> can supply your own through the option variables.
>
> for more dhcpclient goodness man dhclient.conf

Yes I tried to work out what was going on by reading the man pages, but I didn't
find it so illuminating. My problem is that the DHCP and DNS server running
dnsmasq is actually the gateway server and has a second NIC connected to a
modem, from which it gets its ip via DHCP, hence the reason why this box is
running dnsmasq for one NIC and dhclient3 for the other.

It is the resolv.conf on this machine that is being rewritten constantly by
something.

In that context, do those instructions for setting the domain name on the
machine still hold? It slightly throws me that you quote the ip address 127.0.1.1


Thanks
Adam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, 9 Aug 2007, Adam Hardy wrote:

> Jeff D on 09/08/07 00:55, wrote:
>> On Thu, 9 Aug 2007, Adam Hardy wrote:
>>> Jeff D on 08/08/07 00:34, wrote:
>>>> On Tue, 7 Aug 2007, Adam Hardy wrote:
>>>>> debian@reinketelaars.nl on 06/08/07 21:04, wrote:
>>>>>>> My server isengard runs dnsmasq to provide the dhcp clients. However
>>>>>>> it
>>>>>>> doesn't recognise any internal network domain name:
>>>>>>>
>>>>>>> isengard:~# hostname
>>>>>>> isengard
>>>>>>> isengard:~# hostname --fqdn
>>>>>>> hostname: Unknown host
>>>>>>> isengard:~# nslookup gondor
>>>>>>> Server: 194.74.65.69
>>>>>>> Address: 194.74.65.69#53
>>>>>>>
>>>>>>> ** server can't find gondor: NXDOMAIN
>>>>>>>
>>>>>>> I worked out the domain name should go into /etc/resolv.conf (
>>>>>>> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html ) but then it seems that
>>>>>> this is under the control of something else.
>>>>>>
>>>>>> The domain name should go into /etc/resolv.conf
>>>>>> You also have to assign the first nameserver to be _your_ nameserver
>>>>>> and not your ISP's.
>>>>>>
>>>>>> # cat /etc/resolv.conf
>>>>>> search isengard.net
>>>>>> nameserver 127.0.0.1
>>>>>> nameserver ...
>>>>>> nameserver ...
>>>>>
>>>>> Something is rewriting my resolv.conf at least every minute. I suspected
>>>>> it must be dnsmasq attempting to do the DNS but I just stopped dnsmasq,
>>>>> and yet resolv.conf is still being updated. I had a look over my ps
>>>>> output but dont see anything that could be controlling resolv.conf.
>>>>>
>>>>> This is the only entry in it:
>>>>>
>>>>> nameserver 194.74.65.69
>>>>>
>>>>> which is the British Telecom DNS.
>>>>
>>>> Do you have the resolvconf package installed?
>>>
>>> No. That looks like a culprit, but no. Not installed.
>>>
>>> Checking out the dhclient3 and dhclient.conf man pages, it makes no
>>> reference to resolv.conf but it does claim to be able to do dynamic DNS
>>> updates.
>>>
>>> I would have to try disabling the dhclient3 NIC to test if it is this
>>> program rewriting resolv.conf, but i have to wait until the others using
>>> the net have finished.
>>>
>>> How exactly would I set the domain name on the machine - the name I
>>> thought I'd chosen when setting up the system from CD?
>>>
>>> At the moment on this machine when I run 'hostname --domain' it returns
>>> nothing.
>>
>> to set the domain name, add it into /etc/hosts, for example:
>> 127.0.0.1 localhost
>> 127.0.1.1 mybox.mynet.net mybox
>>
>> in /etc/hostname :
>> mybox
>>
>> at start up /etc/init.d/hostname.sh runs, parses these and comes up the
>> domain name.
>>
>> to turn off dhcp provided /etc/host info, edit /etc/dhcp3/dhclient.conf,
>> there is a line that starts with request. Remove domain-name-servers from
>> that list and dhcp wont supply it. If you read down further, you can supply
>> your own through the option variables.
>>
>> for more dhcpclient goodness man dhclient.conf
>
> Yes I tried to work out what was going on by reading the man pages, but I
> didn't find it so illuminating. My problem is that the DHCP and DNS server
> running dnsmasq is actually the gateway server and has a second NIC connected
> to a modem, from which it gets its ip via DHCP, hence the reason why this box
> is running dnsmasq for one NIC and dhclient3 for the other.
>
> It is the resolv.conf on this machine that is being rewritten constantly by
> something.
>
> In that context, do those instructions for setting the domain name on the
> machine still hold? It slightly throws me that you quote the ip address
> 127.0.1.1
>
>
> Thanks
> Adam

You can put your IP in /etc/hosts as:
192.168.1.150 mybox.mynet.net mybox

i just had 127.0.0.1 in mine, sorry for the confusion on that.

This machine also gets its network info through dhcp, which also over
writes /etc/resolv.conf. If you want to keep certian info in there , like
a search domain and specify a namserver, add to /etc/dhcp3/dhclient.conf :
supersede domain-name "mynet.net mynet.local";
prepend domain-name-servers 127.0.0.1;

then, /etc/init.d/networking restart

and you should see in /etc/resolv.conf:
search mynet.net mynet.local
nameserver 127.0.0.1
nameserver 192.168.1.10

you will still need to have your ISPs dns server listed in
/etc/resolv.conf , as dnsmasq uses that as its name server.

then, you can add in hosts into /etc/hosts , restart dnsmasq and it will
reread /etc/resolv.conf and /etc/hosts

I hope that clears up things a little.

Jeff

-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org