Hi all,
please have a look into my configurations. I have been running cobbler sync, restarted cobblerd, booted machine etc. but nothing helped to get the etcd.kubernetes.internal zone working (no file created in /etc/named/).
Any help is appreciated.
Thanks!
cobbler --version Cobbler 2.6.11
pastebins: /etc/cobbler/settings http://pastebin.com/2mtPYqfR /cat /etc/cobbler/named.template http://pastebin.com/MYC4Yu61 /etc/cobbler/zone_templates/etcd.kubernetes.internal http://pastebin.com/kJH8dnWq
according to /etc/cobbler/named.template, you write your configs to:
directory "/var/named";
Am 2016-07-12 09:35, schrieb Stefan Vetter:
Hi all,
please have a look into my configurations. I have been running cobbler sync, restarted cobblerd, booted machine etc. but nothing helped to get the etcd.kubernetes.internal zone working (no file created in /etc/named/).
Any help is appreciated.
Thanks!
cobbler --version Cobbler 2.6.11
pastebins: /etc/cobbler/settings http://pastebin.com/2mtPYqfR [1] /cat /etc/cobbler/named.template http://pastebin.com/MYC4Yu61 [2] /etc/cobbler/zone_templates/etcd.kubernetes.internal http://pastebin.com/kJH8dnWq [3]
Links:
[1] http://pastebin.com/2mtPYqfR [2] http://pastebin.com/MYC4Yu61 [3] http://pastebin.com/kJH8dnWq
cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
Ahhh sure... :D
Ok, I can see the files created in /var/named and loaded.
startup log from named.run: zone 1.168.192.in-addr.arpa/IN: loaded serial 2016071214 zone etcd.kubernetes.internal/IN: loaded serial 2016071214 managed-keys-zone ./IN: loaded serial 5 running
but why isn't my host added to dns?
cobbler system report: Name : KubeMaster1 TFTP Boot Files : {} Comment : testcluster1 Enable gPXE? : False Fetchable Files : {} Gateway : 192.168.1.1 Hostname : kubemaster1.kubernetes.cluster.local Image : IPv6 Autoconfiguration : False IPv6 Default Device : Kernel Options : {} Kernel Options (Post Install) : {} Kickstart : /var/lib/cobbler/kickstarts/Kube_Master_Cloud_Init.yaml Kickstart Metadata : {} LDAP Enabled : False LDAP Management Type : authconfig Management Classes : [] Management Parameters : <<inherit>> Monit Enabled : False Name Servers : ['192.168.1.1'] Name Servers Search Path : [] Netboot Enabled : True Owners : <<inherit>> Power Management Address : Power Management ID : Power Management Password : Power Management Type : ipmitool Power Management Username : Profile : coreos-1010.6.0-KubeMaster Internal proxy : <<inherit>> Red Hat Management Key : <<inherit>> Red Hat Management Server : <<inherit>> Repos Enabled : False Server Override : <<inherit>> Status : production Template Files : {} Virt Auto Boot : 0 Virt CPUs : <<inherit>> Virt Disk Driver Type : <<inherit>> Virt File Size(GB) : <<inherit>> Virt Path : <<inherit>> Virt PXE Boot : 0 Virt RAM (MB) : <<inherit>> Virt Type : xenpv Interface ===== : eth0 Bonding Opts : Bridge Opts : CNAMES : [] InfiniBand Connected Mode : False DHCP Tag : DNS Name : kubemaster-1.etcd.kubernetes.internal Per-Interface Gateway : Master Interface : Interface Type : IP Address : IPv6 Address : IPv6 Default Gateway : IPv6 MTU : IPv6 Prefix : IPv6 Secondaries : [] IPv6 Static Routes : [] MAC Address : 08:00:27:C4:00:F9 Management Interface : False MTU : Subnet Mask : Static : False Static Routes : [] Virt Bridge : xenbr0
2016-07-12 12:27 GMT+02:00 Stefan Hermes stefan@hermes-net.de:
according to /etc/cobbler/named.template, you write your configs to:
directory "/var/named";
Am 2016-07-12 09:35, schrieb Stefan Vetter:
Hi all,
please have a look into my configurations. I have been running cobbler sync, restarted cobblerd, booted machine etc. but nothing helped to get the etcd.kubernetes.internal zone working (no file created in /etc/named/).
Any help is appreciated.
Thanks!
cobbler --version Cobbler 2.6.11
pastebins: /etc/cobbler/settings http://pastebin.com/2mtPYqfR [1] /cat /etc/cobbler/named.template http://pastebin.com/MYC4Yu61 [2] /etc/cobbler/zone_templates/etcd.kubernetes.internal http://pastebin.com/kJH8dnWq [3]
Links:
[1] http://pastebin.com/2mtPYqfR [2] http://pastebin.com/MYC4Yu61 [3] http://pastebin.com/kJH8dnWq
cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
Did See that before, not sure what the reason was. Die you define your system before configuring DNS in cobbler?
Try creating another host with dnsname Option an See if it appears in your zonefile.
Am 12. Juli 2016 13:48:41 MESZ, schrieb Stefan Vetter scvetter@gmail.com:
Ahhh sure... :D
Ok, I can see the files created in /var/named and loaded.
startup log from named.run: zone 1.168.192.in-addr.arpa/IN: loaded serial 2016071214 zone etcd.kubernetes.internal/IN: loaded serial 2016071214 managed-keys-zone ./IN: loaded serial 5 running
but why isn't my host added to dns?
cobbler system report: Name : KubeMaster1 TFTP Boot Files : {} Comment : testcluster1 Enable gPXE? : False Fetchable Files : {} Gateway : 192.168.1.1 Hostname : kubemaster1.kubernetes.cluster.local Image : IPv6 Autoconfiguration : False IPv6 Default Device : Kernel Options : {} Kernel Options (Post Install) : {} Kickstart : /var/lib/cobbler/kickstarts/Kube_Master_Cloud_Init.yaml Kickstart Metadata : {} LDAP Enabled : False LDAP Management Type : authconfig Management Classes : [] Management Parameters : <<inherit>> Monit Enabled : False Name Servers : ['192.168.1.1'] Name Servers Search Path : [] Netboot Enabled : True Owners : <<inherit>> Power Management Address : Power Management ID : Power Management Password : Power Management Type : ipmitool Power Management Username : Profile : coreos-1010.6.0-KubeMaster Internal proxy : <<inherit>> Red Hat Management Key : <<inherit>> Red Hat Management Server : <<inherit>> Repos Enabled : False Server Override : <<inherit>> Status : production Template Files : {} Virt Auto Boot : 0 Virt CPUs : <<inherit>> Virt Disk Driver Type : <<inherit>> Virt File Size(GB) : <<inherit>> Virt Path : <<inherit>> Virt PXE Boot : 0 Virt RAM (MB) : <<inherit>> Virt Type : xenpv Interface ===== : eth0 Bonding Opts : Bridge Opts : CNAMES : [] InfiniBand Connected Mode : False DHCP Tag : DNS Name : kubemaster-1.etcd.kubernetes.internal Per-Interface Gateway : Master Interface : Interface Type : IP Address : IPv6 Address : IPv6 Default Gateway : IPv6 MTU : IPv6 Prefix : IPv6 Secondaries : [] IPv6 Static Routes : [] MAC Address : 08:00:27:C4:00:F9 Management Interface : False MTU : Subnet Mask : Static : False Static Routes : [] Virt Bridge : xenbr0
2016-07-12 12:27 GMT+02:00 Stefan Hermes stefan@hermes-net.de:
according to /etc/cobbler/named.template, you write your configs
to:
directory "/var/named";
Am 2016-07-12 09:35, schrieb Stefan Vetter:
Hi all,
please have a look into my configurations. I have been running cobbler sync, restarted cobblerd, booted machine etc. but nothing helped to get the etcd.kubernetes.internal zone working (no file created in /etc/named/).
Any help is appreciated.
Thanks!
cobbler --version Cobbler 2.6.11
pastebins: /etc/cobbler/settings http://pastebin.com/2mtPYqfR [1] /cat /etc/cobbler/named.template http://pastebin.com/MYC4Yu61 [2] /etc/cobbler/zone_templates/etcd.kubernetes.internal http://pastebin.com/kJH8dnWq [3]
Links:
[1] http://pastebin.com/2mtPYqfR [2] http://pastebin.com/MYC4Yu61 [3] http://pastebin.com/kJH8dnWq
cobbler mailing list cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
cobbler mailing list cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
cobbler@lists.fedorahosted.org