Documentation Request - DNS Forwarder on CP

[jshawdell]

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:

• 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.

[abhishek-sa1]

@jshawdell This feature is part of release_1.7 branch - https://github.com/dell/omnia/tree/release_1.7. Omnia does not modify already released branches or tag. Can you use release_1.7 branch for this feature?

[jshawdell]

Thanks Abhishek, I will plan for another deployment using 1.7. * Jason Internal Use - Confidential From: Abhishek S A ***@***.***> Sent: Thursday, December 12, 2024 11:33 PM To: dell/omnia ***@***.***> Cc: Shaw, Jason ***@***.***>; Mention ***@***.***> Subject: Re: [dell/omnia] Documentation Request - DNS Forwarder on CP (Issue #2387) [EXTERNAL EMAIL] @jshawdell [github.com]<https://urldefense.com/v3/__https:/github.com/jshawdell__;!!LpKI!mFIq_ys5MCKctaZ4n0CKrdZpjfGrRYQf5xwDbya2AGHHMbWJGkwQ-o8FoIjVUQJ8g2jfLDolKZfst3vvRI8u7ebA$> This feature is part of release_1.7 branch - https://github.com/dell/omnia/tree/release_1.7 [github.com]<https://urldefense.com/v3/__https:/github.com/dell/omnia/tree/release_1.7__;!!LpKI!mFIq_ys5MCKctaZ4n0CKrdZpjfGrRYQf5xwDbya2AGHHMbWJGkwQ-o8FoIjVUQJ8g2jfLDolKZfst3vvRI1U0zse$>. Omnia does not modify already released branches or tag. Can you use release_1.7 branch for this feature? — Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https:/github.com/dell/omnia/issues/2387*issuecomment-2540588731__;Iw!!LpKI!mFIq_ys5MCKctaZ4n0CKrdZpjfGrRYQf5xwDbya2AGHHMbWJGkwQ-o8FoIjVUQJ8g2jfLDolKZfst3vvRAzitSwq$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BCWXWGSMDI2WZZKZDGX266D2FJWSNAVCNFSM6AAAAABS4I37HWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGU4DQNZTGE__;!!LpKI!mFIq_ys5MCKctaZ4n0CKrdZpjfGrRYQf5xwDbya2AGHHMbWJGkwQ-o8FoIjVUQJ8g2jfLDolKZfst3vvRDLyDzmX$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[priti-parate]

Closing this issue as Omnia 1.7 is released