You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently deployed OMNIA version: v1.6.1-4-g9eb3885b
After a cluster was deployed on our nodes, we realized we needed our nodes to resolve dns names from a DNS server upstream from the CP (use case: install an ubuntu package)
We ran into problems trying to add a DNS Forwarder in named.conf on the CP. Normally, it is straightforward to add a forwarder by adding a "forwarders" entry in the options section and restarting the named service. Example:
We learned that due to dnssec validation being used in Omnia, "dnssec-validation no;" was also required for this to work properly
The Ask:
Consider adding something to the Documentation that instructs the user how to properly configure a DNS forwarder for cases like this.
Side Question:
We had added a DNS entry in the admin_network section of the network_spec.xml file and initially assumed that the nodes on this network would be configured to use this DNS. After some digging, we realized that xcat deploys bind DNS on the CP and that all the nodes were configured to use the CP for DNS.
Question:
If the user chooses to add a "DNS" entry in the network_spec.xml, under the admin_network section - how is this DNS IP used?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
We recently deployed OMNIA version: v1.6.1-4-g9eb3885b
After a cluster was deployed on our nodes, we realized we needed our nodes to resolve dns names from a DNS server upstream from the CP (use case: install an ubuntu package)
We ran into problems trying to add a DNS Forwarder in named.conf on the CP. Normally, it is straightforward to add a forwarder by adding a "forwarders" entry in the options section and restarting the named service. Example:
#generated by xCAT: /opt/xcat/sbin/makedns command
options {
directory "/var/lib/bind/";
allow-recursion { any; };
forwarders {192.168.102.100; }; <----
};
We learned that due to dnssec validation being used in Omnia, "dnssec-validation no;" was also required for this to work properly
The Ask:
Side Question:
We had added a DNS entry in the admin_network section of the network_spec.xml file and initially assumed that the nodes on this network would be configured to use this DNS. After some digging, we realized that xcat deploys bind DNS on the CP and that all the nodes were configured to use the CP for DNS.
Question:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: