Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

[DNS] DNS entries obtained by DHCP still exist in /etc/resolv.conf after apply config_db.json with static IP #12907

Closed
ppikh opened this issue Dec 1, 2022 · 0 comments · Fixed by #13516
Closed

[DNS] DNS entries obtained by DHCP still exist in /etc/resolv.conf after apply config_db.json with static IP #12907

ppikh opened this issue Dec 1, 2022 · 0 comments · Fixed by #13516
Assignees
@oleksandrivantsiv
Labels
NVIDIA Triaged this issue has been triaged

Comments

@ppikh
Copy link
Contributor

ppikh commented Dec 1, 2022

Description

DNS entries obtained by DHCP still exist in /etc/resolv.conf after apply config_db.json with static IP

Steps to reproduce the issue:

  1. Install image via ONIE
  2. Check /etc/resolv.conf - should be available DNS servers obtained by DHCP after first boot
  3. Apply config_db.json with static IP
  4. Check /etc/resolv.conf

Describe the results you received:

/etc/resolv.conf still have DNS servers obtained from DHCP server, but static IP address used

Describe the results you expected:

/etc/resolv.conf does not have DNS servers which are obtained from DHCP after configure static IP address

Output of show version:

SONiC.202205_1_rc.2-632e16451_Internal

Output of show techsupport:

[sonic_dump_r-bulldog-02_20221121_131257.tar.gz](https://github.com/sonic-net/sonic-buildimage/files/10133363/sonic_dump_r-bulldog-02_20221121_131257.tar.gz)
@oleksandrivantsiv oleksandrivantsiv self-assigned this Dec 6, 2022
@tjchadaga tjchadaga added Triaged this issue has been triaged NVIDIA labels Dec 7, 2022
This was referenced Jan 25, 2023
Closed
Merged
liat-grozovik pushed a commit that referenced this issue Jan 30, 2023
@oleksandrivantsiv
Clear DNS configuration received from DHCP during networking reconfig…
c7ecd92 
…uration in Linux. (#13516)

- Why I did it
fixes #12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
mssonicbld pushed a commit to mssonicbld/sonic-buildimage that referenced this issue Feb 6, 2023
@oleksandrivantsiv @mssonicbld
Clear DNS configuration received from DHCP during networking reconfig…
1dfb489 
…uration in Linux. (sonic-net#13516)

- Why I did it
fixes sonic-net#12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
oleksandrivantsiv added a commit to oleksandrivantsiv/sonic-buildimage that referenced this issue Feb 7, 2023
@oleksandrivantsiv
Clear DNS configuration received from DHCP during networking reconfig…
119cd10 
…uration in Linux. (sonic-net#13516)

- Why I did it
fixes sonic-net#12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
yxieca pushed a commit that referenced this issue Feb 10, 2023
@oleksandrivantsiv
Clear DNS configuration received from DHCP during networking reconfig…
d1fa414 
…uration in Linux. (#13516) (#13695)

- Why I did it
fixes #12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
mssonicbld pushed a commit that referenced this issue Feb 16, 2023
@oleksandrivantsiv @mssonicbld
Clear DNS configuration received from DHCP during networking reconfig…
5ef488f 
…uration in Linux. (#13516)

- Why I did it
fixes #12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
StormLiangMS pushed a commit to StormLiangMS/sonic-buildimage that referenced this issue Mar 1, 2023
@oleksandrivantsiv @StormLiangMS
Clear DNS configuration received from DHCP during networking reconfig…
42ed785 
…uration in Linux. (sonic-net#13516)

- Why I did it
fixes sonic-net#12907

When the management interface IP address configuration changes from dynamic to static the DNS configuration (retrieved from the DHCP server) in /etc/resolv.conf remains uncleared. This leads to a DNS configuration pointing to the wrong nameserver. To make the behavior clear DNS configuration received from DHCP should be cleared.

- How I did it
Use resolvconf package for managing DNS configuration. It is capable of tracking the source of DNS configuration and puts the configuration retrieved from the DHCP servers into a separate file. This allows the implementation of DNS configuration cleanup retrieved from DHCP during networking reconfiguration.

- How to verify it
Ensure that the management interface has no static configuration.
Check that /etc/resolv.conf has DNS configuration.
Configure a static IP address on the management interface.
Verify that /etc/resolv.conf has no DNS configuration.
Remove the static IP address from the management interface.
Verify that /etc/resolv.conf has DNS configuration retrieved form DHCP server.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@oleksandrivantsiv oleksandrivantsiv

Labels
NVIDIA Triaged this issue has been triaged
Projects
None yet
Milestone
No milestone
3 participants
@oleksandrivantsiv @ppikh @tjchadaga