Enlisting fails due to it trying to use external DNS servers instead of maas-internal

Users
,
1

I am trying to get several servers enlisted into MAAS. It boots, finds ens1f0 and continues loading stuff. After downloading some packages it tries to connect to http://.maas-internal:5248/MAAS/api/2.0/machines/?op=is_registered… But this fails because it is trying to use the upstream DNS servers configured in MAAS instead of the internal DNS server of MAAS.

Any idea what is wrong in my configuration?

2

Looking at that DHCP configuration, I see:

option domain-name-servers 10.241.96.21, 10.241.80.40, 10.241.80.41;

Comparing this to the tcpdump, I never see the enlisting image trying to access 10.241.96.21 (MAAS) when querying for http://10.241.96.0--24.maas-internal/

3

@uzimmermann, can you give us this kind of information so we can (hopefully) help?

4

I figured out to do it this way:

  • Use Peer proxy instead of just external proxy
  • Removed DNS servers from the subnet and let just the MAAS provide DNS.
1 Like
5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.