ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000319ClearOSapp-dns - DNS Serverpublic2011-07-16 13:552013-07-29 13:54
Reportertimb80 
Assigned Touser2 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version5.2-SP1 
Target Version6.4.0 UpdatesFixed in Version6.4.0 Updates 
Summary0000319: Enable localhost to ping hostnames stored via dnsmasq
DescriptionDnsmasq uses it's own internal DHCP daemon to store the hostname records of DHCP clients.

Default configuration means that nslookup or dig may work but ping doesn't. Windows hosts or other clients configured via DHCP can succesfully ping other hosts by 'ping myhost' but ClearOS (tested via Putty) cannot.

On the local machine 'ping myhost' will not work but 'ping myhost.' will (note the full stop append). The issue is to do with local name resolution as noted in the dnsmasq FAQ.
http://www.thekelleys.org.uk/dnsmasq/docs/FAQ [^]

To fix this issue, specify 'domain mydomain.com' in /etc/resolv.conf

The domain here should be that already specified in the webconfig and stored in /etc/dnsmasq.conf
Steps To Reproduce
Additional InformationThis is particularly important for BackupPC which uses ping from the local machine to determine if a host is up
TagsNo tags attached.
Relationships
related to 0000890closed user2 Add new resolver support - /etc/resolv-peerdns.conf 
related to 0000891closed user2 Add new resolver support - /etc/resolv-peerdns.conf 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-07-16 13:55timb80New Issue
2011-07-16 13:56timb80SummaryEnable localhost to resolve hostnames stored via dnsmasq => Enable localhost to ping hostnames stored via dnsmasq
2011-08-16 10:31user2Statusnew => confirmed
2012-06-09 15:53timb80Note Added: 0000528
2013-02-02 10:58user2Target Version => 6.4.0 Beta 2
2013-02-02 10:59user2Note Added: 0000680
2013-02-12 17:49user2Relationship addedrelated to 0000890
2013-02-12 17:49user2Relationship addedrelated to 0000891
2013-02-12 17:50user2Categoryapp-dhcp - DHCP Server => app-dns - DNS Server
2013-02-21 20:00user2Target Version6.4.0 Beta 2 => 6.4.0
2013-03-14 11:56user2Target Version6.4.0 => 6.4.0 Updates
2013-07-29 13:54user2Note Added: 0000958
2013-07-29 13:54user2Statusconfirmed => resolved
2013-07-29 13:54user2Fixed in Version => 6.4.0 Updates
2013-07-29 13:54user2Resolutionopen => fixed
2013-07-29 13:54user2Assigned To => user2
2013-07-29 13:54user2Statusresolved => closed

Notes
(0000528)
timb80   
2012-06-09 15:53   
An additional requirement is that /etc/resolv.conf includes the local name server so that it queries dnsmasq first before your ISP DNS servers...the logs state that this is ignored but it does change the behaviour

nameserver 127.0.0.1
(0000680)
user2   
2013-02-02 10:59   
The new DNS/Resolver implementation in 6.4.0 simplifies things. Bumping priority.
(0000958)
user2   
2013-07-29 13:54   
It looks like this one was fixed in 6.4.0 or 6.4.0 updates.