I cannot seem to get Fedora 13 (or any other Linux distro)  to register with
our local nameserver.

I feel like this should be a simple process  (maybe it is and I'm just slow)

So far, all my attempts and man page/InterWeb research have come up short.

The system looks like it's trying to register but all requests go to a
multicast addr (224.0.0.251) and the protocol is MDNS. Since it's multicast,
there's no guarantee I'll ever get a response (positive or negative), but it
clearly does not work because I can't reach the machine via hostname or
fqdn.

On windoze I see no MulticastDNS requests, but I do see standard SOA request
directly to the nameserver, followed by a dynamic update exchange indicating
the PTR was successfully updated.  All my winders boxes seem to have no
problem dynamically registering to the nameserver, but none of my linux
systems (dhcp or static addr) are resolvable without having IT manually add
a PTR.  I've asked a couple other *nix hackers in the office, but they all
shake their heads and say "Let me know if you get it to work"

Following the suggestion found in several threads on linuxquestions.org and
the fedora forums I've tweaked various network files that should make it
work.

sysconfig/network and resolv.conf are fine.

sysconfig/network-scripts/ifcfg-eth0 has an entry:
DHCP_CLIENT_ID=<my_hostname>

I see NetworkManager generated/updated the file
/var/run/nm-dhclient-eth0.conf  with:
send  dhcp-client-identifier "<my_hostname>"

None of it made a difference.

Now I turn to the all-knowing gnhlug... Any ideas?

Regards,
-- Joel
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Reply via email to