| Anonymous | Login | 2024-04-19 14:03 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0000319 | ClearOS | app-dns - DNS Server | public | 2011-07-16 13:55 | 2013-07-29 13:54 | ||||
| Reporter | timb80 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 5.2-SP1 | ||||||||
| Target Version | 6.4.0 Updates | Fixed in Version | 6.4.0 Updates | ||||||
| Summary | 0000319: Enable localhost to ping hostnames stored via dnsmasq | ||||||||
| Description | Dnsmasq 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 | ||||||||
| Additional Information | This is particularly important for BackupPC which uses ping from the local machine to determine if a host is up | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|||||||||||
|
|||||||||||
 Relationships |
|
Notes |
|
|
(0000528) timb80 (developer) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-07-16 13:55 | timb80 | New Issue | |
| 2011-07-16 13:56 | timb80 | Summary | Enable localhost to resolve hostnames stored via dnsmasq => Enable localhost to ping hostnames stored via dnsmasq |
| 2011-08-16 10:31 | user2 | Status | new => confirmed |
| 2012-06-09 15:53 | timb80 | Note Added: 0000528 | |
| 2013-02-02 10:58 | user2 | Target Version | => 6.4.0 Beta 2 |
| 2013-02-02 10:59 | user2 | Note Added: 0000680 | |
| 2013-02-12 17:49 | user2 | Relationship added | related to 0000890 |
| 2013-02-12 17:49 | user2 | Relationship added | related to 0000891 |
| 2013-02-12 17:50 | user2 | Category | app-dhcp - DHCP Server => app-dns - DNS Server |
| 2013-02-21 20:00 | user2 | Target Version | 6.4.0 Beta 2 => 6.4.0 |
| 2013-03-14 11:56 | user2 | Target Version | 6.4.0 => 6.4.0 Updates |
| 2013-07-29 13:54 | user2 | Note Added: 0000958 | |
| 2013-07-29 13:54 | user2 | Status | confirmed => resolved |
| 2013-07-29 13:54 | user2 | Fixed in Version | => 6.4.0 Updates |
| 2013-07-29 13:54 | user2 | Resolution | open => fixed |
| 2013-07-29 13:54 | user2 | Assigned To | => user2 |
| 2013-07-29 13:54 | user2 | Status | resolved => closed |
|
Issue History |