© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Do you know where NetworkManager is pulling it's FQDN info from if it is not getting it from DHCP?
The behavior I noticed pre 10.04, is whatever domain the machine gets on install (either assigned by DHCP or manually during install) is the one that NetworkManager uses no mater what network you connect to. Although I cannot find anywhere that this is set on the system. This is from memory and I have not specifically tested for it, so I might not be 100% correct here.
For example machines I build at work get work's domain set by DHCP, and when I bring them home their FQDN does not change.
I don't know how NetworkManager is designed to handle this situation. But I do know, in my case if NetworkManager changes the FQDN between home and work this will cause issues w/ Duplicity backup. That said, if NM is expected to change the FQDN to the network it is on, then I can put in place workarounds to get Duplicity backup working again.