Just a silly question: why do I need rDNS from an ISP?

https://www.cloudflare.com/learning/dns/glossary/reverse-dns/

lxsw20:

 

https://www.cloudflare.com/learning/dns/glossary/reverse-dns/

 

Thanks. But you didn't understand my question.

Again: Why reverse DNS from an ISP?

Tinkerisk:

 

Again: Why reverse DNS from an ISP?

 

Because they are the ones who own the IP address?

Tinkerisk:

 

lxsw20:

 

https://www.cloudflare.com/learning/dns/glossary/reverse-dns/

 

 

Thanks. But you didn't understand my question.

 

Again: Why reverse DNS from an ISP?

 

Who would you expect to supply it?

Well, Akamai on a VPS, just for an example.

Would that be a Linode VPS? 😉

Most VPS's allow rDNS.

I usually set them as it makes logs for others a little more tidy as to who exactly is the client connecting from a private organisation/domain, rather than ISP network only point of view.

Same with running trace routes to check on a server, I prefer to see the host/domain name of the organisation, not the ISP's default PTR, just an OCD thing when you want things to look a bit more polished/professional.

These days the only mandatory need for them are for mail server security/authorisation (if you know the dangers and mandatory security/admin that come with running them).

The compute VPS's on Quic also allow to set PTR, as does the Fibre connection's IP address. I was doing that for a short test, but I would rather have my web/audio streaming/xmpp server on the end of the fibre connection with tidied up PTR records. Hence the /31.

Cheers,

Gavin.

yitz:

 

Would that be a Linode VPS? 😉

 

Nope, Ionos.

@kiwirock: On to the topic, of rDNS, is there any chance of this happening for /31 subnets in the future etc...?

This is already a thing (I've got it on my /30) however there are a number of bugs with the rDNS module they use on their admin portal meaning it doesn't work for everyone.

If this is not appearing for you then lodge a problem ticket under Support --> Submit Problem Report with the IP's and the rDNS records you're wanting applied and somebody will sort it for you from Quic's end.

Cheers.

Sent through a submission earlier in the week. Hopefully they have a little time to review it.

Would it be worth cancelling it and trying to add-on again, like it's hit and miss, or if it doesn't work chances are it wont work again?

Gavin.

kiwirock:

 

These days the only mandatory need for them are for mail server security/authorisation (if you know the dangers and mandatory security/admin that come with running them).

 

This is actually not true. No RFC formalises this requirement.

The confusion comes about through historic practices and an incorrect understanding of what the term "Fully Qualified Domain Name" means. RFC 2505 uses the term in a way that is inconsistent with both RFC 1035 and 1912, implying there is a requirement for a PTR. It is, to put it simply, wrong. The RFC 1035 definition is both a standard itself and referred to explicitly by the current SMTP standards, while RFC 2505 is informational.