** Changed in: dhcp3 (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/10239
Title:
dhcp3-client: Does not send hostname to server by default
T
i don't know toomuch about these things and am completely new to
ubuntu...but...i have been hacked for 4 years and, among other things am
on a network controlled by others who set permissions, global policy etc
and hide themselves effectively..so nothing new here
--
You received this bug notific
Wow. A 6+ year old bug in basic network connectivity. My home router
runs DD-WRT with DNSMasq enabled which "...is designed to provide DNS
and, optionally, DHCP, to a small network. It can serve the names of
local machines which are not in the global DNS."
But DNSMasq was unable to resolve a hostn
Dec. 2010; bug is still present in Mint Linux Debian Edition.
A nice way to fix this would be to modify dhclient, adding a function to its
Data Expression parser called, something like, hostname that would simply
return the client's hostname. Or, solve this and the whole class of related
probl
Sept. 2010; bug is still present, I still have to comment the "send
host-name "";" for Network Manager to send the string entered
into the 'DHCP Client ID' field. Otherwise it simply gets ignored.
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
Y
The same here on Ubuntu Lucid 10.4, even though /etc/dhcp3/dhclient.conf
has "send host-name "";" by default in it.
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a member of Ubuntu
Bugs, which
I still have this problem even though it says it is fixed.
** Description changed:
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubu
** Changed in: dhcp3 (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: dhcp3 (Ubuntu)
Status: Fix Committed => Fix Released
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you
I'm not entirely sure if this is the same bug, I can always open a new
one, but my University wired network requires me to send my student ID
(e.g. an arbitrary string) as hostname. Uni laptops have their hostname
setup as heir student ID. Of course, I could just setup my hostname as
my student ID
Thanks for your quick response Mat.
The default was the first I've tried.
I thought I had tried everything, but I overlooked post #23 about the FRITZ!Box
that I have as well. The solution mentioned there works for me too !!
I don't understand the logic behind it, the FRITZ!Box already knows the
On Sat, Oct 24, 2009 at 07:08:35PM -, Adrie wrote:
> A week ago I installed Xubuntu 9.04 Jaunty Jackalope on my old Pentium Pro
> machine and this bug still seems to exists.
> Spend days with trying to solve this, found many posts about it, none where
> recent though.
> I have installed all t
A week ago I installed Xubuntu 9.04 Jaunty Jackalope on my old Pentium Pro
machine and this bug still seems to exists.
Spend days with trying to solve this, found many posts about it, none where
recent though.
I have installed all the available updates, still the problem persists.
--
dhcp3-clie
** Changed in: dhcp3 (Debian)
Status: Fix Released => Confirmed
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
I tested today a jaunty virtual machine in an AD network: it does a dynamic DNS
update out of the box.
Until now I had to use additional lines in dhclient.conf (#send fqdn.fqdn
"hostname.mydomain.it."; #send fqdn.server-update on;) or use nsupdate in a
hook script.
Thanks for fixing this bug.
-
** Changed in: dhcp3 (Debian)
Status: Confirmed => Fix Released
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
Update: I now have a fresh installation and after adding the line "send
fqdn.server-update on" to dhcient.conf (the default one after
installation) it works here, I can lookup my IP via nslookup
again. Without it it doesn't work.
--
dhcp3-client: Does not send hostname to server by default
https
** Changed in: dhcp3 (Debian)
Status: New => Confirmed
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
dhclient does send the hostname with the patch (I verified via
wireshark), but it doesn't send a client identifier (cid). A fritz box
(DSL router, market leader in germany) won't update it's dns records
with the sent hostname without a cid, and some other DSL routers show
this behavior, too, at lea
Just checked: I don't have any DHCP related errors in the log file.
When I did a "nslookup hostname" or "nslookup hostname.domain.com" it
returned an old IP address I had a few weeks ago. Then I did "sudo
dhclient -r eth0" to release, replaced in dhclient.conf with
the actual hostname followed by
Weird, I just checked my router's log, and my hostname is still
transfered correctly. Do you have any DHCP related error in
/var/log/daemon.log?
--
dhcp3-client: Does not send hostname to server by default
https://bugs.launchpad.net/bugs/10239
You received this bug notification because you are a
I now have dhcp3 3.0.4-12ubuntu4 here, and it seems like the
"" fix doesn't work anymore on my Feisty installation. It
worked with the 3.0.4-12ubuntu2 version.
I haven't changed my dhclient.conf (attached)
** Attachment added: "dhclient.conf"
http://librarian.launchpad.net/7279832/dhclient.con
dhcp3 (3.0.4-12ubuntu2) feisty; urgency=low
.
* Add debian/patches/dynamic-hostname.dpatch:
- Add support for a new string type 'h' which behaves like 't' except
that '' is changed to the current hostname.
- Change 'host-name' DHCP option type from 't' to 'h'.
- Based
** Changed in: dhcp3 (Ubuntu)
Assignee: (unassigned) => Martin Pitt
Status: Confirmed => In Progress
--
dhcp3-client: Does not send hostname to server by default
https://launchpad.net/bugs/10239
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
** Bug 43594 has been marked a duplicate of this bug
--
dhcp3-client: Does not send hostname to server by default
https://launchpad.net/bugs/10239
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 54203 has been marked a duplicate of this bug
--
dhcp3-client: Does not send hostname to server by default
https://launchpad.net/bugs/10239
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Here's a simple patch against dhcp3-3.0.3-6ubuntu7 . It lets you use
send host-name "";
(that is, the above line literally - paste it as is into your
dhclient.conf)
dhclient will then send your computer's hostname to the DHCP server.
--
dhcp3-client: Does not send hostname to server by default
** Bug 51478 has been marked a duplicate of this bug
--
dhcp3-client: Does not send hostname to server by default
https://launchpad.net/bugs/10239
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
27 matches
Mail list logo
