© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@vtapia, did you also test if 'ping' and/or 'telnet' DNS resolution was fixed as well? i.e. currently:
ubuntu@lp1804487:~$ ping testing.
ping: testing.
ubuntu@lp1804487:~$ telnet testing.
telnet: could not resolve testing.
ubuntu@lp1804487:~$ ssh testing.
ssh: Could not resolve hostname testing.
ubuntu@lp1804487:~$ host testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
testing.
That doesn't appear fixed with the latest systemd...?
ubuntu@lp1804487:~$ dpkg -l |grep 'ii systemd '
ii systemd 239-7ubuntu10.5 amd64 system and service manager
ubuntu@lp1804487:~$ ping testing.
ping: testing.
ubuntu@lp1804487:~$ telnet testing.
telnet: could not resolve testing.
ubuntu@lp1804487:~$ ssh testing.
ssh: Could not resolve hostname testing.