This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2744
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2744
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680301
Title:
Digging through the latest code in the bazaar repo, it seems
VNET_DOMAINNAME is now a configuration option, (handled in
cluster/handlers.c and project/cluster/handlers.c according to grep),
which does the above.
--
You received this bug notification because you are a member of Ubuntu
Server
Digging through the latest code in the bazaar repo, it seems
VNET_DOMAINNAME is now a configuration option, (handled in
cluster/handlers.c and project/cluster/handlers.c according to grep),
which does the above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I think this is the same as an issue I've been trying to fix.
On a freshly started up instance (with DISABLE_DNS=n), running hostname
-f or dnsdomainname fails (causing issues with running Puppet, as, I
would expect it would with other applications).
As a temporary workaround, I used a user-data
Its actually simpler than that :)
L1032 of net/vnetwork.c is
fprintf(fp, subnet %s netmask %s {\n option subnet-mask %s;\n option
broadc .
change it to ..
fprintf(fp, subnet %s netmask %s {\n option domain-name
\eucalyptus.internal\;\n option subnet-mask %s;\n option broadc ...
and
Also re (I'm using the CLC private IP, because when using the public
IP, the returning packets are from the local address, and dns doesn't
like it.) ..
Thats a mix of two issues i think ..
Lets say your instance FQDN is euca-172-19-1-2.eucalyptus.internal /
The user-data script sets the options in /etc/dhcp3/dhclient.conf.
The supersede and prepend tags make sure that when the lease is renewed, those
options supersede and prepend the ones retrieved via dhcp. So those options
should always override, at least, that's how I understand it, and also,
Aha - I didn't noticed it was /etc/dhcp3/dhclient.conf you were editing,
rather than /etc/resolv.conf
Re the change to net/vnetwork.c .. The only config option that would
require that line to change (when DNS is delegated correctly) is when
DISABLE_DNS=Y it should use the original version .. No
The CLC is only there temporarily, the cloud is currently in test phase,
once we get it put into place properly, the DNS will be sorted.
Thanks for the help, I'll let you know how it goes!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I think this is the same as an issue I've been trying to fix.
On a freshly started up instance (with DISABLE_DNS=n), running hostname
-f or dnsdomainname fails (causing issues with running Puppet, as, I
would expect it would with other applications).
As a temporary workaround, I used a user-data
Its actually simpler than that :)
L1032 of net/vnetwork.c is
fprintf(fp, subnet %s netmask %s {\n option subnet-mask %s;\n option
broadc .
change it to ..
fprintf(fp, subnet %s netmask %s {\n option domain-name
\eucalyptus.internal\;\n option subnet-mask %s;\n option broadc ...
and
Also re (I'm using the CLC private IP, because when using the public
IP, the returning packets are from the local address, and dns doesn't
like it.) ..
Thats a mix of two issues i think ..
Lets say your instance FQDN is euca-172-19-1-2.eucalyptus.internal /
The user-data script sets the options in /etc/dhcp3/dhclient.conf.
The supersede and prepend tags make sure that when the lease is renewed, those
options supersede and prepend the ones retrieved via dhcp. So those options
should always override, at least, that's how I understand it, and also,
Aha - I didn't noticed it was /etc/dhcp3/dhclient.conf you were editing,
rather than /etc/resolv.conf
Re the change to net/vnetwork.c .. The only config option that would
require that line to change (when DNS is delegated correctly) is when
DISABLE_DNS=Y it should use the original version .. No
The CLC is only there temporarily, the cloud is currently in test phase,
once we get it put into place properly, the DNS will be sorted.
Thanks for the help, I'll let you know how it goes!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680301
Title:
DNS
** Changed in: eucalyptus
Assignee: (unassigned) = Daniel Nurmi (nurmi)
--
DNS Search Domain in instance /etc/resov.conf should be set by DHCP
https://bugs.launchpad.net/bugs/680301
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: eucalyptus
Assignee: (unassigned) = Daniel Nurmi (nurmi)
--
DNS Search Domain in instance /etc/resov.conf should be set by DHCP
https://bugs.launchpad.net/bugs/680301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
