[plug] Bind / Dhcp / Dynamic DNS

[Adrian Woodley]

Are you sure its not using Avahi/libnss-mdns for resolving the below
address? ".local" isn't a fantastic extension to use, as it collides with
the mdns namespace.

Try using dig to test domain name resolution, rather than ping. ie:

dig scarefaceclaw

This will use only DNS to resolve names, rather than all the methods listed
in /etc/nsswitch.conf (usually dns, hosts file and mdns).

Cheers,

Adrian

On Mon, 4 May 2009 22:47:33 +0800, Adam Davin <byteme-its at westnet.com.au>
wrote:
> Hi All, 
> 
> I have finally gotten around to setting up a bind / dhcp server with
> dynamic updates for clients. 
> 
> It seems to be working very well, resolving local hostnames etc,
> except... 
> 
> I can ping hostnames from the clients and it all resolves nicely:
> 
> pooh:/home/badger# ping scarfaceclaw
> PING scarfaceclaw.bytemeit.local (192.168.0.149) 56(84) bytes of data.
> 64 bytes from scarfaceclaw.bytemeit.local (192.168.0.149): ...
> 
> However if I try to ping the fqdn, I get "unknown host".
> 
> pooh:/home/badger# ping scarfaceclaw.bytemeit.local
> ping: unknown host scarfaceclaw.bytemeit.local
> 
> /etc/resolv.conf is as follows:
> 
> nameserver 192.168.0.149 
> nameserver 192.168.0.199
> search bytemeit.local
> 
> /var/cache/bind/db.192.168.0 excerpt
> 
> 			NS	ns1.bytemeit.local.
> 			NS	ns2.bytemeit.local.
> $ORIGIN 0.168.192.in-addr.arpa.
> $TTL 300	; 5 minutes
> 11			PTR	pooh.bytemeit.local.
> $TTL 86400	; 1 day
> ;149			PTR	ns1.bytemeit.local.
> 
> /var/cache/bind/db.bytemeit.local excerpt
> 			NS	ns1.bytemeit.local.
> 			NS	ns2.bytemeit.local.
> $ORIGIN bytemeit.local.
> ns1			A	192.168.0.149
> ns2			A	192.168.0.199
> scarfaceclaw		A	192.168.0.149
> $TTL 300	; 5 minutes
> pooh			A	192.168.0.11
> 
> Any other information or thoughts would be greatly appreciated...
> 
> Thanks and Regards,