Well, if you take a look at the other thread and actually follow the steps we did over there, you'll see find the object that's causing the message. Just watch out for spaces in the hostname.
dig mail.myxcom.com
; <>> DiG 9.5.0-P2 <>> mail.myxcom.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<>> DiG 9.5.0-P2 <>> mail.vsnl.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER
cc get_object REF_pGVulaKhWJ
get_object returned {
'autoname' => 0,
'class' => 'network',
'data' => {
'addresses' => [
'67.215.65.132',
'67.215.77.132'
],
'addresses6' => [],
'comment' => '',
'hostname' => 'pop.vsnl.net',
'interface' => '',
'name' => 'pop.vsnl.net',
'resolved' => 1,
'resolved6' => 0,
'timeout' => 604800
},
'hidden' => 0,
'lock' => '',
'nodel' => '',
'ref' => 'REF_pGVulaKhWJ',
'type' => 'dns_group'
}
acenn:/home/login # cc get_object REF_XZCMfwqnzm
get_object returned {
'autoname' => 0,
'class' => 'network',
'data' => {
'addresses' => [
'67.215.65.132',
'67.215.77.132'
],
'addresses6' => [],
'comment' => '',
'hostname' => 'myxcom',
'interface' => '',
'name' => 'myxcom',
'resolved' => 1,
'resolved6' => 0,
'timeout' => 604800
},
'hidden' => 0,
'lock' => '',
'nodel' => '',
'ref' => 'REF_XZCMfwqnzm',
'type' => 'dns_group'
216.219.112.0 / 20 (REF_STzYlmeJAn)
karvid (REF_XZCMfwqnzm)
question :if i am not using pop and smtp related objects in active configration do i suppose to get error ?
Yes. The DNS resolution is done for all objects, even when you are not "actively" using them.
You are not adding any information for the astaro team to go on. I asked you where the two objects were being used and you haven't figured that out. Dig and nslookup have nothing to do with the error in system logs. Its the conversion process which you are completely ignoring.
Therefore not a bug since nobody can see it besides you.
