This repository has been archived by the owner. It is now read-only.

DNS Problem #130

Closed
tpradeep opened this Issue Mar 4, 2013 · 5 comments

Comments

Projects
None yet
3 participants
Contributor

tpradeep commented Mar 4, 2013

I deployed bosh-boostrap on OpenStack, after ssh into inception VM, I tried deploying cloud foundry. I got the dns error as follows.

When I change the resolve.conf file, it reverts back to original settings after running bosh cf.

vcap@inception-vm:~$ bosh cf prepare system production
Path for to store all CloudFoundry systems: |/var/vcap/store/systems|
Creating new system demo directory
CloudFoundry system set to /var/vcap/store/systems/demo
Current BOSH is 'http://172.24.4.225:25555'
Path to store all BOSH releases: |/var/vcap/store/releases|
Path to store downloaded/created stemcells: |/var/vcap/store/stemcells|
Main public IP address (press Enter to provision new IP):
Provisioning openstack public IP address...
Root DNS (e.g. mycompany.com): test.com
Checking that DNS api.test.com resolves to IP address 172.24.4.226... W, [2013-03-04T08:27:15.013405 #16938] WARN -- : Nameserver 10.0.0.1 not responding within UDP timeout, trying next one
F, [2013-03-04T08:27:15.013528 #16938] FATAL -- : No response from nameservers list
/usr/local/lib/ruby/gems/1.9.1/gems/net-dns-0.7.1/lib/net/dns/resolver.rb:1007:in query': No response from nameservers list (Net::DNS::Resolver::NoResponseError) from /usr/local/lib/ruby/gems/1.9.1/gems/net-dns-0.7.1/lib/net/dns/resolver.rb:866:insearch'
from /usr/local/lib/ruby/gems/1.9.1/gems/net-dns-0.7.1/lib/net/dns/resolver.rb:135:in start' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.0/lib/bosh/cli/commands/cf.rb:508:invalidate_dns_a_record'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.0/lib/bosh/cli/commands/cf.rb:477:in validate_root_dns_maps_to_core_ip' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.0/lib/bosh/cli/commands/cf.rb:272:inconfirm_or_prompt_for_system_requirements'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.0/lib/bosh/cli/commands/cf.rb:43:in prepare_system' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/command_handler.rb:57:inrun'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:61:in run' from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:18:inrun'
from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/bin/bosh:16:in <top (required)>' from /usr/local/bin/bosh:23:inload'
from /usr/local/bin/bosh:23:in `

'

How do I resolve this dns problem ?

Contributor

tpradeep commented Mar 4, 2013

To prevent resolve.conf from getting modified, I write protected the file after modifying the dns. However, the error was the same but with a different message

vcap@inception-vm:~$ sudo bosh cf prepare system production
CloudFoundry system set to /var/vcap/store/systems/production
Current BOSH is 'http://172.24.4.225:25555'
Checking that DNS api.hsd1.ca.comcast.net resolves to IP address 172.24.4.227... ooh no!
Please setup your DNS:
Subdomain: * (wildcard)
IP address: 172.24.4.227
Domain api.hsd1.ca.comcast.net should resolve to IP address 172.24.4.227

Contributor

drnic commented Mar 4, 2013

Quick workaround: --skip-validations flag

On Mon, Mar 4, 2013 at 4:24 AM, tpradeep notifications@github.com wrote:

To prevent resolve.conf from getting modified, I write protected the file after modifying the dns. However, the error was the same but with a different message
vcap@inception-vm:~$ sudo bosh cf prepare system production
CloudFoundry system set to /var/vcap/store/systems/production
Current BOSH is 'http://172.24.4.225:25555'
Checking that DNS api.hsd1.ca.comcast.net resolves to IP address 172.24.4.227... ooh no!
Please setup your DNS:
Subdomain: * (wildcard)
IP address: 172.24.4.227

Domain api.hsd1.ca.comcast.net should resolve to IP address 172.24.4.227

Reply to this email directly or view it on GitHub:
StarkAndWayne#130 (comment)

Contributor

tpradeep commented Mar 4, 2013

But thats just skipping a step. Won't the error shoot up problems during deployment ?

rkoster commented Mar 14, 2013

I'm not yet sure how dns fully works in OpenStack but I think the problem has to do with the resolv.conf file being updated by the information provided by OpenStack over DHCP. As is explained in this comment.

You could try to add a prepend domain to /etc/dhcp3/dhclient.conf. This is what bosh does on the stemcells.

@drnic drnic closed this Jul 18, 2013

Contributor

drnic commented Jul 18, 2013

I closed this ticket with my eyes closed. So it evens out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.