{"action":"created","issue":{"url":"https://api.github.com/repos/omega8cc/boa/issues/1089","repository_url":"https://api.github.com/repos/omega8cc/boa","labels_url":"https://api.github.com/repos/omega8cc/boa/issues/1089/labels{/name}","comments_url":"https://api.github.com/repos/omega8cc/boa/issues/1089/comments","events_url":"https://api.github.com/repos/omega8cc/boa/issues/1089/events","html_url":"https://github.com/omega8cc/boa/issues/1089","id":186086510,"number":1089,"title":"How should the \"nodns\" option work and be used?","user":{"login":"ar-jan","id":1176293,"avatar_url":"https://avatars.githubusercontent.com/u/1176293?v=3","gravatar_id":"","url":"https://api.github.com/users/ar-jan","html_url":"https://github.com/ar-jan","followers_url":"https://api.github.com/users/ar-jan/followers","following_url":"https://api.github.com/users/ar-jan/following{/other_user}","gists_url":"https://api.github.com/users/ar-jan/gists{/gist_id}","starred_url":"https://api.github.com/users/ar-jan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ar-jan/subscriptions","organizations_url":"https://api.github.com/users/ar-jan/orgs","repos_url":"https://api.github.com/users/ar-jan/repos","events_url":"https://api.github.com/users/ar-jan/events{/privacy}","received_events_url":"https://api.github.com/users/ar-jan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-29T16:11:26Z","updated_at":"2016-11-03T15:02:20Z","closed_at":null,"body":"I was doing an installation on Scaleway, where the servers have a private and a public IP address, and BOA is unable to pick up the public IP (it's not visible directly in eth0 config).\n\nSo I used `boa in-stable public web01.example.nl info@email.com o1 none nodns`. This failed the DNS test - perhaps expected, because I had not yet configured _MY_OWNIP correctly because .barracuda.cnf did not yet exist. First question: **what is the correct way to use the nodns option (i.e. how to provide the correct _MY_OWNIP on first run)?**\n\nSo after the first `boa in-stable` attempt I corrected the _MY_OWNIP configuration in the now available .barracuda.cnf, and ran `boa in-stable public web01.example.nl info@email.com o1 none nodns` again. But this still failed the DNS test, even though all settings were now correct:\n\n> BOA [15:21:47] ==> EXIT on error due to invalid DNS setup\n> \n> ```\n> * Your custom _MY_OWNIP is set to \"12.34.56.78\"\n> * Your custom _MY_HOSTN is set to \"web01.example.nl\"\n> * Your custom _MY_FRONT is set to \"master.web01.example.nl\"\n> \n> * Your _MY_HOSTN and/or _MY_FRONT doesn't match your _MY_OWNIP,\n>   or your hostname is not set properly yet.\n> ```\n\nMy configuration:\n\n> web01:~# uname -n\n> web01.example.nl\n> web01:~# curl icanhazip.com\n> 12.34.56.78\n> web01:~# host web01.example.nl\n> web01.example.nl has address 12.34.56.78\n> web01:~# host master.web01.example.nl\n> master.web01.example.nl has address 12.34.56.78\n\nSo the displayed _MY_OWNIP in the error message actually does match both _MY_FRONT and _MY_HOSTN; and DNS settings have propagated. It looks like the DNS test is actually still run, but the test does not use the values configured in .barracuda.cnf, although it does display them later on.\nIt also looks like the `nodns` argument should have written `_DNS_SETUP_TEST=NO` in .barracuda.cnf, but it was absent. After manually adding _DNS_SETUP_TEST=NO to .barracuda.cnf the installation succeeds. Second question: **is it a bug that _DNS_SETUP_TEST was not written to /root/.barracuda.cnf with the nodns option?**\n"},"comment":{"url":"https://api.github.com/repos/omega8cc/boa/issues/comments/258168365","html_url":"https://github.com/omega8cc/boa/issues/1089#issuecomment-258168365","issue_url":"https://api.github.com/repos/omega8cc/boa/issues/1089","id":258168365,"user":{"login":"omega8cc","id":128547,"avatar_url":"https://avatars.githubusercontent.com/u/128547?v=3","gravatar_id":"","url":"https://api.github.com/users/omega8cc","html_url":"https://github.com/omega8cc","followers_url":"https://api.github.com/users/omega8cc/followers","following_url":"https://api.github.com/users/omega8cc/following{/other_user}","gists_url":"https://api.github.com/users/omega8cc/gists{/gist_id}","starred_url":"https://api.github.com/users/omega8cc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/omega8cc/subscriptions","organizations_url":"https://api.github.com/users/omega8cc/orgs","repos_url":"https://api.github.com/users/omega8cc/repos","events_url":"https://api.github.com/users/omega8cc/events{/privacy}","received_events_url":"https://api.github.com/users/omega8cc/received_events","type":"User","site_admin":false},"created_at":"2016-11-03T15:02:20Z","updated_at":"2016-11-03T15:02:20Z","body":"Hmm.. The `nodns` option was intended mainly for debugging and may not work on all systems, because of the environment differences BOA is not aware of. It is also possible that it got broken at some point, because we didn't need/test it for a very long time.\r\n\r\nThat said, the `nodns` is not a replacement for vendor specific support, like for Amazon EC2."}}
{"actor":{"display_login":"omega8cc"}}