Score:0

Realm join registers additional bridge IP in DNS

in flag

I was just joining an Ubuntu Server 22.04 LTS machine with an existing Docker environment to our AD domain, but got a slightly odd result with the DNS registration.

When installing Docker, a bridge interface, docker0, is automatically created for it's internal network. Here it's 172.17.0.1/16.

I followed this guide: https://ubuntu.com/server/docs/samba-active-directory, which worked fine. But after joining I saw two entries for the server in our Windows DNS, one mapped to the LAN interface IP, which has the search domain and nameserver set in the netplan config, the other one mapped to the Docker bridge network which I do not want.

I tried updating my hosts file according to https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member, and then leaving and re-joining. The guide mentions changing the FQDN to map to the interface IP instead of 127.0.0.1, and removing the 127.0.1.1 line. This made no difference.

I'm a bit new to using Linux in a domain environment, is this expected behaviour, can I prevent this from happening somehow?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.