[SOLVED] how to delete FDQN

mfoley · 01-22-2024, 12:14 PM

I'm getting bounce messages from mfoley@addns.ohprs.org. I think this addns subdomain was set up many years ago, I forget why. I'm trying to remove it, but it does not show up at the DNS host, network solutions, in any A, CNAME or other record for the ohprs.org domain.

How can I track this down and kill it?

wpeckham · 01-22-2024, 12:43 PM

You had an email account at the Ohio Highway Patrol Retirement System?

mfoley · 01-29-2024, 10:11 PM

Quote:

Originally Posted by wpeckham

You had an email account at the Ohio Highway Patrol Retirement System?

Yes, and still do, but the one in my OP is not it.

I think I had configured that address long ago for use on the Samba mailList. I believe I've solved my problem my unregistering that address with the Samba mailList. Since doing so I haven't seen those bounce messages from Exchange.

If you have additional curiosity about my OHPRS email, mail me at my personal address: mfoley@novatec-inc.com.

scasey · 01-30-2024, 06:37 PM

AFAIK, subdomains are not “visible” when querying a domain name. To query for a subdomain, one must know the FQDN of the subdomain.

Code:

dig @8.8.8.8 addns.ohprs.org any
addns.ohprs.org.        3600    IN      HINFO   "RFC8482" ""

mfoley · 01-30-2024, 11:06 PM

Quote:

Originally Posted by scasey

AFAIK, subdomains are not “visible” when querying a domain name. To query for a subdomain, one must know the FQDN of the subdomain.

Code:

dig @8.8.8.8 addns.ohprs.org any
addns.ohprs.org.        3600    IN      HINFO   "RFC8482" ""

'm not sure I follow you on that. For one thing, addns.ohprs.org was a host name, not a subdomain. The way the DNS is set up at Network Solutions, any hostname will resolve to 98.102.63.107 unless there is a specific A record:

Code:

$ host booga.ohprs.org
booga.ohprs.org has address 98.102.63.107

$ host sasquatch.ohprs.org
sasquatch.ohprs.org has address 98.102.63.107

$ host webserver.ohprs.org
webserver.ohprs.org has address 98.102.63.106   <-- a real host

I think the issue was that the Samba mailList was sending to mfoley@addns.ohprs.org which was resolving the MX record at Exchange, but Exchange didn't like that FDQN. When I removed mfoley@addns.ohprs.org from the mailList, no more bounces.