Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: dwater on December 28, 2004, 04:03:12 AM

Title: dns dhcp lan addresses
Post by: dwater on December 28, 2004, 04:03:12 AM
Hi,

How can I make SME's dns resolve addresses it gives out via DHCP?

Max.
Title: Re: dns dhcp lan addresses
Post by: dwater on December 28, 2004, 11:08:17 AM
Hrmph.

Actually, this seems to work intermittently. EG, here it resolves with 'host' but not with 'dig' :

Code: [Select]

$ host ricardo
ricardo.x.x has address 192.168.x.11
$ dig ricardo

; <<>> DiG 9.2.1 <<>> ricardo
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47894
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ricardo.                       IN      A

;; Query time: 1 msec
;; SERVER: 192.168.x.1#53(192.168.x.1)
;; WHEN: Wed Dec 29 02:17:15 2004
;; MSG SIZE  rcvd: 25


Any ideas?

Max.
Title: dns dhcp lan addresses
Post by: smeghead on December 28, 2004, 12:26:24 PM
DHCP to DNS synchroniser

http://www.activeservice.co.uk/sme/contribs/
Title: dns dhcp lan addresses
Post by: dwater on December 28, 2004, 12:48:30 PM
Quote from: "smeghead"
DHCP to DNS synchroniser

http://www.activeservice.co.uk/sme/contribs/


Thanks. It sounds like it should have done the job, but it didn't seem to make any difference.

I have just noticed one more thing though; dig will resolve fine if I give fully qualified names :

Code: [Select]

$ dig ricardo

; <<>> DiG 9.2.1 <<>> ricardo
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16031
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ricardo.                       IN      A

;; Query time: 1 msec
;; SERVER: 192.168.x.1#53(192.168.x.1)
;; WHEN: Wed Dec 29 03:58:51 2004
;; MSG SIZE  rcvd: 25

[mwaterman@truth ~]$ dig ricardo.x.x

; <<>> DiG 9.2.1 <<>> ricardo.x.x
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62933
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ricardo.x.x.           IN      A

;; ANSWER SECTION:
ricardo.x.x.    86171   IN      A       192.168.x.11

;; Query time: 1 msec
;; SERVER: 192.168.x.1#53(192.168.x.1)
;; WHEN: Wed Dec 29 03:58:59 2004
;; MSG SIZE  rcvd: 53


Any ideas? Perhaps this is 'by design' since 'host' seems to work.

I will see if trouble symptoms are still there (printers disappearing).

Thanks!

Max.
Title: dns dhcp lan addresses
Post by: smeghead on December 28, 2004, 12:56:08 PM
.. you will need to refresh your leases on your w/s's in order for the SME box to track the system name/ip allocation.

This contrib has worked for me on 30 plus systems without fail!
Title: dns dhcp lan addresses
Post by: dwater on December 28, 2004, 01:04:33 PM
Quote from: "smeghead"
.. you will need to refresh your leases on your w/s's in order for the SME box to track the system name/ip allocation.

This contrib has worked for me on 30 plus systems without fail!


Hrm. I think this might be a slightly different problem.

I mean, even the dhcp/dns server itself does not resolve (and I'm doing this while logged into that server) :

Code: [Select]

[x@truth ~]$ host truth
truth.x.x has address 192.168.x.1
[x@truth ~]$ dig truth

; <<>> DiG 9.2.1 <<>> truth
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56927
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;truth.                         IN      A

;; Query time: 1 msec
;; SERVER: 192.168.x.1#53(192.168.x.1)
;; WHEN: Wed Dec 29 04:11:36 2004
;; MSG SIZE  rcvd: 23


I used to use dnsmasq to do this when I was running on Fedora Core, and I don't recall the same problem - though I don't often use 'dig'.

I don't know what this issue is, but I don't think it is the cause of my 'woes', so I'll let it drop.

It does seem to have solved the strange hostnames it was giving the clients, so that is it's purpose, I think.

I'll take my printing woes to another thread.

Thanks for solving that problem at least :)

Max.