Re: autodns-dhcp
Am Don, 2002-10-31 um 21.05 schrieb Pete Clarke:
> Hi there guru's! :-)
>
> I have switched from Suse & Redhat linux to Debian, and have to say that I
> love it!
>
> I have not learnt so much about Linux until I started with Debian, and I
> cannot stop - it's great (gotta love apt-get!).
>
> Anyway, this message does actually have a point to it.
> I have a home network consisting of 2 Debian servers, 2 Linux workstations,
> and 5 Windows workstations .. I currently use dhcp to provide ip addresses
> to my clients.
>
> I am using a Debian box as a dial-up router, and all works well, apart from
> getting unwanted dial-outs at random intervals when Bind tries to update it
> records..
>
> My question is two-fold:
>
> 1. How can I get Bind to stop requesting updates all the time, so that I can
> control the dial-outs?
> 2. Would I gain any benefit to using autodns-dhcp .. some of the dialouts
> are to resolve internal name..
>
> My internal domain is "wimbledon" .. each machine is named after a Womble
> (:-) .. orinoco, tomsk, wellington etc. etc.
> I have Bind set up so that I can issue a:
>
[...]
> orinoco:/etc/bind# dig orinoco
>
> ; <<>> DiG 9.2.1 <<>> orinoco
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1559
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;orinoco. IN A
>
> ;; AUTHORITY SECTION:
> . 8893 IN SOA A.ROOT-SERVERS.NET.
> NSTLD.VERISIGN-GRS.COM. 2002103100 1800 900 604800 86400
Your local bind did not find the host, so it used your ISPs DNS.
> ;; Query time: 5 msec
> ;; SERVER: 192.168.0.1#53(192.168.0.1)
> ;; WHEN: Thu Oct 31 15:39:48 2002
> ;; MSG SIZE rcvd: 100
>
> It doesn't recognise the name ... my /etc/hosts files looks like this:
>
> orinoco:/etc/bind# cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> 192.168.0.1 orinoco.wimbledon orinoco
> 192.168.0.2 router.wimbledon router
Looks OK to me.
I am not sure what you mean by autodns-dhcp. I think that means using
the dhcpd to update your bind which is nice if you do not use fixed IPs.
What you may want to look at, is the file /etc/resolv.conf.
Add the "search" line to it and see if it helps:
search wimbledon
nameserver $IP_OF_YOUR_DNS
This tells bind to search the domain "wimbledon" first, if it can't
resolve a hostname.
So when bind can't find the host orinoco, it will then try
orinoco.wimbledon which it should find.
--
Matthias Hentges
[www.hentges.net] -> PGP + HTML are welcome
ICQ: 97 26 97 4 -> No files, no URLs
My OS: Debian Woody: Geek by Nature, Linux by Choice
Reply to: