Topic: DNS problem resolving local addresses

[gelcube]

I'm currently having an issue resolving local workstation FQDNs.  I use DHCP for all but one windows server, which has a static IP.  I have that one server's hostname in the "hostnames and addresses" panel, and it resolves fine.

But when I do a "ping workstation.domain.local", I get an unknown host error.  Reverse dns gets a pc-00045.domain.local result.

I've rebooted a couple of times, but it doesn't seem to help.

I don't believe this is a bug, since I've got another SME7 box that's working just fine.  Any ideas?

[gelcube]

Ok, an update.

The SME 7 that is working has a corporate DNS set, and is not the DHCP server.  So it's not in the same situation.  This could be a bug.  I'll hit the bug tracker.

Anyone else having this issue?

[CharlieBrady]

I'm currently having an issue resolving local workstation FQDNs.  I use DHCP for all but one windows server, which has a static IP.  I have that one server's hostname in the "hostnames and addresses" panel, and it resolves fine.

But when I do a "ping workstation.domain.local", I get an unknown host error.  Reverse dns gets a pc-00045.domain.local result.

DNS doesn't know anything about "workstation" unless you have entered "workstation" in the hostnames panel.

[gelcube]

DNS doesn't know anything about "workstation" unless you have entered "workstation" in the hostnames panel.

Shouldn't the workstation autoregister its name with the DNS?  I know that's the default on Microsoft DNS, as that's how I've got my Windows Servers set up.  

How do I go about reconfiguring TinyDNS to autoregister my DHCP workstations?  It's the best way to monitor and administer DHCP workstations remotely.

[CharlieBrady]

Shouldn't the workstation autoregister its name with the DNS?

That's a matter of opinion. I don't want my DNS managed by workstations I don't trust.

How do I go about reconfiguring TinyDNS to autoregister my DHCP workstations?

There's no built in support for that. I believe that there are contribs for doing that, which work my monitoring log files. Search, and ask in the Contribs forum if you can't find.

[gelcube]

Hmm.  Of course the first thing I did was do several searches of the Contribs, Howtos, and forums.  In fact, I went through every single contrib user folder on contribs.org.  THAT took a while.  

But I will post in the Contribs forum.  Thanks for confirming this isn't a bug, but by design.  Quick question, would it be TinyDNS or dnscache that would handle something like this?  I'm afraid I'm not too sure what the role of dnscache is.