[plug] Bind / Dhcp / Dynamic DNS

[Adam Davin]

Hi Adrian, 

On Wed, 06 May 2009 13:17:12 +0800
Adrian Woodley <adrian at diskworld.com.au> wrote:

> 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:
> 
pooh:/home/badger# dig scarfaceclaw

; <<>> DiG 9.5.1-P2 <<>> scarfaceclaw
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8964
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;scarfaceclaw.			IN	A

;; AUTHORITY SECTION:
.			10800	IN	SOA
a.root-servers.net. nstld.verisign-grs.com. 2009050700 1800 900 604800
86400

;; Query time: 335 msec
;; SERVER: 192.168.0.149#53(192.168.0.149)
;; WHEN: Thu May  7 19:48:41 2009
;; MSG SIZE  rcvd: 105

Doesn't seem to resolve the name as part of the local domain. However, 

pooh:/home/badger# dig scarfaceclaw.bytemeit.local

does return something more promising.

; <<>> DiG 9.5.1-P2 <<>> owl.bytemeit.local
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41884
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;owl.bytemeit.local.		IN	A

;; ANSWER SECTION:
owl.bytemeit.local.	86400	IN	A	192.168.0.178

;; AUTHORITY SECTION:
bytemeit.local.		86400	IN	NS
ns1.bytemeit.local. bytemeit.local.		86400
IN	NS	ns2.bytemeit.local.

;; ADDITIONAL SECTION:
ns1.bytemeit.local.	86400	IN	A	192.168.0.149
ns2.bytemeit.local.	86400	IN	A	192.168.0.199

;; Query time: 2 msec
;; SERVER: 192.168.0.149#53(192.168.0.149)
;; WHEN: Thu May  7 19:47:34 2009
;; MSG SIZE  rcvd: 120

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

I found the avahi-daemon was running, I stopped this and now it seems
to be resolving local hosts with both the hostname and also the local
domain so it would seem that avahi was definitely getting in the way. 

It is all resolving as long as the avahi daemon is not running. I think
it may all be working now. 

On the '.local' subject, what is suggested for internal domains ?

Thanks and Regards, 

-- 

Adam Davin
Byteme IT Services
Mob: 0422 893 898
Fax: 08 9493 4462
Email: byteme-its at westnet.com.au