How to remove a local DNS entry [solved]

I have searched the forum for similar issues

on

This category is for general issues(=something is broken) regarding YunoHost, NOT apps.

on

This form is written in English but feel free to write in French if you’re more comfortable!

on

What type of hardware are you using

VPS bought online

What YunoHost version are you running

12.1.41.2 (stable)

How are you able to access your server

SSH

Are you in a special context or did you perform specific tweaking on your YunoHost instance ?

No.

Describe your issue

Since always kalum.ca MX records have been handled by Zoho (free) and I never changed when I started using YUNoHost. Various subdomains happily exist on my YH vps along with MX for everything except kalum.ca
The other day I stupidly sent the main domain to my vps and now I have an extra, high priority MX record that I don’t know how to get rid of. I thought once I deleted the zone entry it would time out, but, no, it’s stored somewhere on my vps, so now postfix can’t forward to it anymore:

root@gemlog 19:20:06 /etc> dig +short MX kalum.ca @127.0.0.1
5 kalum.ca. <<--------------- need to get rid of this!
root@gemlog 19:21:19 /etc> dig +short MX kalum.ca @1.1.1.1
10 mx.zoho.com.
20 mx2.zoho.com.

rndc flush or rndc reconfig both break:
rndc: neither /etc/bind/rndc.conf nor /etc/bind/rndc.key was found

There are ways of making them, but now I’m afraid of breaking the other emails that postfix is handling just fine… :-/

I did also try to grep -rin for ‘kalum’ in /etc, but… no luck. It must be in a db somewhere? Dunno.

Share relevant logs or error messages

rndc: neither /etc/bind/rndc.conf nor /etc/bind/rndc.key was found

If I understand you correctly maybe disabling mail_in in the domain settings could help, that should change a file below /etc/dnsmasq.d/.

Thank you so much! Yes! There was a file named kalum.ca in that dir. I moved it out of the way and restarted and it works now. Whew! What a bother - I knew I’d done a really dumb thing … just after I did it.

Now the remote MX records have higher priority again, as they should!

Thanks again bud.

Generally, configuring the domain is needed to be able to send emails from it, it’s perfectly ok.
Disabling mail_in in the UI of the domain should keep the external MX working.

Under certain circumstances there remain, however: Issues to fix email breakages caused by upgrades (regression) - #2 by tmb