Skip to content

Aruba DNS & syslog - #3796

Merged
ipspace merged 4 commits into
ipspace:devfrom
sdargoeuves:aruba_dns
Aug 18, 2026
Merged

Aruba DNS & syslog#3796
ipspace merged 4 commits into
ipspace:devfrom
sdargoeuves:aruba_dns

Conversation

@sdargoeuves

Copy link
Copy Markdown
Collaborator

ArubaCX: #3760

@ipspace ipspace left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The DNS resolution through a VRF does not work for me. What version of ArubaCX are you using?

Also, considering so many other platforms cannot do DNS resolution through a VRF, maybe we disable it for ArubaCX as well?

ipspace added a commit that referenced this pull request Aug 18, 2026
@ipspace

ipspace commented Aug 18, 2026

Copy link
Copy Markdown
Owner

OK, I figured out the details

ip dns domain-list cicd.local vrf oob_nms
ip dns server-address 172.16.0.2 vrf oob_nms

... configures DNS resolution within the VRF -- DNS client runs in the VRF and is used for commands like ping X vrf Y. ArubaCX does not seem to have the "global DNS client using VRF for the transport" functionality. I'll change the feature flags, rerun the DNS-in-VRF test, and merge the PR.

@ipspace ipspace left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The modified feature flags work. Merging.

Thank you for the PR!

@ipspace
ipspace merged commit bf7af6f into ipspace:dev Aug 18, 2026
4 checks passed
@sdargoeuves

Copy link
Copy Markdown
Collaborator Author

Thanks for the correction. I have to admit I was relying on their documentation... next on my todo list:

  • start using the integration tests
  • stop assuming something will work just because you think it could, or you've read it somewhere in the vendor docs!

@ipspace

ipspace commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Thanks for the correction. I have to admit I was relying on their documentation

I looked at that documentation and said "That's fishy. There's no way it does what I want it to do" ;)) Must have seen too many vendor docs for one lifetime ;)

start using the integration tests

👍

stop assuming something will work just because you think it could, or you've read it somewhere in the vendor docs!

That's always a dangerous assumption.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants