Bug 753656 - Domain set to hostname by default
Summary: Domain set to hostname by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnsmasq
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 01:18 UTC by Michel Kraus
Modified: 2013-01-12 15:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-27 04:39:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michel Kraus 2011-11-14 01:18:27 UTC
Version-Release number of selected component (if applicable):
2.58-2.fc16

Description of problem:
The dnsmasq.service-file sets the parameter -s (--domain) to $HOSTNAME.
A simple DHCP server created by adding only dhcp-range to the config file gives unwanted results that are different from previous versions of Fedora.

The results pretend that my machine is named server.example.com and the a dhcp-client is requesting client as hostname.

Actual results:
client gets known as client.server.example.com by default.

Expected results:
client should get client.example.com by default.


Additional info:
SysV-initscripts based versions up to Fedora 15 used the result of dnsdomainname if available. If no dnsdomainname could be found it did not set the parameter.

Suggestion:
Removing this parameter from dnsmasq.service and always let the user decide.

Comment 1 Fedora Admin XMLRPC Client 2012-10-22 13:21:14 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Marcos Mello 2012-11-13 23:04:50 UTC
I agree. And removing -s $HOSTNAME from the service file will solve Bug 822797

Comment 3 Tomáš Hozza 2012-11-19 10:07:19 UTC
Removing -s $HOSTNAME seems like the best solution at this time.

Comment 4 Fedora Update System 2012-11-19 12:22:26 UTC
dnsmasq-2.59-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/dnsmasq-2.59-5.fc16

Comment 5 Fedora Update System 2012-11-19 12:25:49 UTC
dnsmasq-2.63-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/dnsmasq-2.63-2.fc17

Comment 6 Fedora Update System 2012-11-19 12:29:34 UTC
dnsmasq-2.63-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-17789/dnsmasq-2.63-3.fc18

Comment 7 Marcos Mello 2012-11-19 15:41:02 UTC
Thanks Tomas. "EnvironmentFile=-/etc/sysconfig/network" is then unnecessary. At least in F18 where it is almost empty.

Comment 8 Fedora Update System 2012-11-19 19:34:31 UTC
Package dnsmasq-2.63-3.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnsmasq-2.63-3.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17789/dnsmasq-2.63-3.fc18
then log in and leave karma (feedback).

Comment 9 Tomáš Hozza 2012-11-20 07:59:55 UTC
(In reply to comment #7)
> Thanks Tomas. "EnvironmentFile=-/etc/sysconfig/network" is then unnecessary.
> At least in F18 where it is almost empty.

Will do, see Bug 878343. Thanks!

Comment 10 Fedora Update System 2012-11-27 04:39:59 UTC
dnsmasq-2.63-4.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2012-12-06 07:05:59 UTC
dnsmasq-2.59-5.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2013-01-12 15:24:56 UTC
dnsmasq-2.65-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.