Zone File

[CTClaude]

Hi Everyone,

So I am having a bit of a problem.
Someone in our company created a domain abc.com and edited the zone file (as per clients instructions) that has been changed by ISP to point to Amazon. This said we have a hosting option with ISP for the domain that we can create mailboxes.
So yes I try and send a test email to the new email account but it does not deliver to the mailbox.
So ISP tells me the Zone file is incorrect

There answer is the domain to be pointing to Amazon due to your broken zone file caused by replacing the @-A record with the @-CNAME record. As such, in order to correct your current DNS zone file, we would kindly like to recommend removing the specified CNAME and adding the correct A-record as this would allow the email service for the specified domain to resolve successfully.

Firstly everything is residing in amazon. Secondly, the client application apparently does not work without the @ - CNAME record.
The reasoning of the client is that the record must be like that as the IPs change frequently.

Is there no other way we can get past this. I need email working thus the @ record needs to change. But the staff member who edited the zone file as per customer details says it breaks everything when changing that.

Thanks in advance

 

[scudsucker]

To put it as simply as possible, the 'A record' is used to point the domain to an IP address (in this case, no doubt Amazon's IP) for website traffic, eg, a browser.

The 'CNAME' is used to point subdomains, eg, www.abc.com to abc.com ( and abc.com is pointed to the IP as above)

Email is handled by the MX record. This must be pointed to your ISP so that they can handle emails.

The easiest way to fix this will be to ask your ISP to do it for you.

 

[SauRoNZA]

Depends one what you are actually pointing to in AWS you can infect use the A-record with an alias to an IP....and then use a DNS name instead of an IP address in that field.

You have to do that with load balancers in AWS so the same should apply here.

Why is the IP changing so frequently if it’s inside AWS? And if it really does why isn’t the DNS name used instead of the IP?

 

[CTClaude]

We are using outsystems and outsystems resides on AWS and couple of weeks ago everything stopped working and we couldnt figure out what was going on and then we found out that the IPs changed and that is might happen frequently.
Xneelo is complaining our Zone File is broken because of the @ =CNAME

 

[Jade @ Absolute Hosting]

We are using outsystems and outsystems resides on AWS and couple of weeks ago everything stopped working and we couldnt figure out what was going on and then we found out that the IPs changed and that is might happen frequently.
Xneelo is complaining our Zone File is broken because of the @ =CNAME

View attachment 842185

I know that this is an old thread but have you reported the issue to Xneelo?

their dev team need to fix this as you cannot use a cname for a domains A record. Their konsole should catch this and prevent it - hence they need to be notified of the bug

 

[Gnome]

Someone in our company created a domain abc.com and edited the zone file (as per clients instructions)

It scares me that there are people out there charging money and don't understand what an A record or CNAME is.

The 'CNAME' is used to point subdomains, eg, www.abc.com to abc.com ( and abc.com is pointed to the IP as above)

Or another domain... There is no rule saying it has to be a sub-domain.

What likely happened here is they created a CNAME pointing to an EC2 instance. EC2 instances have a public DNS name with its publicly facing IP part of the name. So when they terminated or stop/started the instance the IP changed and thus the instance public DNS name.

There is nothing wrong with that per-se other than it is idiotic to create a CNAME to an instance public DNS name given it can change so easily.

I know that this is an old thread but have you reported the issue to Xneelo?

their dev team need to fix this as you cannot use a cname for a domains A record. Their konsole should catch this and prevent it - hence they need to be notified of the bug

But the pictures shows a CNAME, which he stated was the intention. Where does an A record factor into this?