Re: New question, do I really need a AAAA record?
On Thu, Aug 10, 2017 at 07:26:16PM +0100, Stuart Henderson wrote: > Rephrasing: if you make an outgoing SMTP connection, a reverse DNS PTR > record should exist for the source address you're connecting from (whether > that's v4 or v6), and an A (for v4) or (for v6) lookup for the name > in that PTR should give back the same address. > > For your example: > > 185.37.212.61 -> server.roquesor.com > server.roquesor.com -> 185.37.212.61 > > That looks good. > > If you are making outgoing SMTP connections from a v6 address, then you > should have matching PTR+ as well. OK. Huff!, it's just I got dizzy. After all the advises I got in this thread I started to doubt even about my existence. :-) Thank you Stuart!
Re: New question, do I really need a AAAA record?
On 2017/08/10 20:18, Walter Alejandro Iglesias wrote: > In article you wrote: > > Hi Stuart, > > > > In article you wrote: > > > On 2017-08-10, Rui Ribeiro wrote: > > > > An email server in a residential setting will fail PTR unless you are > > > > working with a medium sized/an ISP that cares about their customers. > > > > > > > > see answer here > > > > https://unix.stackexchange.com/questions/371329/bind-proper-reverse-config > > > > > > You can't expect to reliably deliver email unless you have a PTR record > > > and > > > an A/ record (at least within the same domain, though in some cases > > > the full hostname needs to match). > > > > > > > At this point things got a bit confusing. First of all I don't run my > > own DNS server, I use the free dns service from the registrar company > > where I bought my domain names. There I configured the records I need > > for the web and mail servers I run at home. Then, asking my ISP to add > > a PTR record on *their* DNS was the first thing I did when I contracted > > the service, and was the first thing I checked again last weekend after > > the problem I explain in this thread happened. Despite the negative > > results the website someone recommended me shows (dnsinspect.com) I > > think my PTR is working well, you can use host(1), dig(1) or nslookup(1) > > to check my IP (185.37.212.61) against yours or any public DNS to > > corroborate it. Or simply put the IP in your browser URL bar, press > > ENTER and see if it resolves to my web site. :-) > > > > Stated the above, now the new question. By A/ records I understand > > you mean the records on *my* side (not my ISP's), don't you? Well, > > since I'm not using ipv6 I didn't added any record. Do you > > recommend me to add it, anyways? > > > > > > Sorry, I think I didn't formulate the question well. What I meant was, > do I need also a static ipv6 to be considered by big smtp servers as a > legal sender? > Rephrasing: if you make an outgoing SMTP connection, a reverse DNS PTR record should exist for the source address you're connecting from (whether that's v4 or v6), and an A (for v4) or (for v6) lookup for the name in that PTR should give back the same address. For your example: 185.37.212.61 -> server.roquesor.com server.roquesor.com -> 185.37.212.61 That looks good. If you are making outgoing SMTP connections from a v6 address, then you should have matching PTR+ as well.
Re: New question, do I really need a AAAA record?
In article you wrote: > Hi Stuart, > > In article you wrote: > > On 2017-08-10, Rui Ribeiro wrote: > > > An email server in a residential setting will fail PTR unless you are > > > working with a medium sized/an ISP that cares about their customers. > > > > > > see answer here > > > https://unix.stackexchange.com/questions/371329/bind-proper-reverse-config > > > > You can't expect to reliably deliver email unless you have a PTR record and > > an A/ record (at least within the same domain, though in some cases > > the full hostname needs to match). > > > > At this point things got a bit confusing. First of all I don't run my > own DNS server, I use the free dns service from the registrar company > where I bought my domain names. There I configured the records I need > for the web and mail servers I run at home. Then, asking my ISP to add > a PTR record on *their* DNS was the first thing I did when I contracted > the service, and was the first thing I checked again last weekend after > the problem I explain in this thread happened. Despite the negative > results the website someone recommended me shows (dnsinspect.com) I > think my PTR is working well, you can use host(1), dig(1) or nslookup(1) > to check my IP (185.37.212.61) against yours or any public DNS to > corroborate it. Or simply put the IP in your browser URL bar, press > ENTER and see if it resolves to my web site. :-) > > Stated the above, now the new question. By A/ records I understand > you mean the records on *my* side (not my ISP's), don't you? Well, > since I'm not using ipv6 I didn't added any record. Do you > recommend me to add it, anyways? > > Sorry, I think I didn't formulate the question well. What I meant was, do I need also a static ipv6 to be considered by big smtp servers as a legal sender?
Re: New question, do I really need a AAAA record?
On Thu, Aug 10, 2017 at 08:18:31PM +0200, Walter Alejandro Iglesias wrote: > > Sorry, I think I didn't formulate the question well. What I meant was, > do I need also a static ipv6 to be considered by big smtp servers as a > legal sender? > No. khm
New question, do I really need a AAAA record?
Hi Stuart, In article you wrote: > On 2017-08-10, Rui Ribeiro wrote: > > An email server in a residential setting will fail PTR unless you are > > working with a medium sized/an ISP that cares about their customers. > > > > see answer here > > https://unix.stackexchange.com/questions/371329/bind-proper-reverse-config > > You can't expect to reliably deliver email unless you have a PTR record and > an A/ record (at least within the same domain, though in some cases > the full hostname needs to match). > At this point things got a bit confusing. First of all I don't run my own DNS server, I use the free dns service from the registrar company where I bought my domain names. There I configured the records I need for the web and mail servers I run at home. Then, asking my ISP to add a PTR record on *their* DNS was the first thing I did when I contracted the service, and was the first thing I checked again last weekend after the problem I explain in this thread happened. Despite the negative results the website someone recommended me shows (dnsinspect.com) I think my PTR is working well, you can use host(1), dig(1) or nslookup(1) to check my IP (185.37.212.61) against yours or any public DNS to corroborate it. Or simply put the IP in your browser URL bar, press ENTER and see if it resolves to my web site. :-) Stated the above, now the new question. By A/ records I understand you mean the records on *my* side (not my ISP's), don't you? Well, since I'm not using ipv6 I didn't added any record. Do you recommend me to add it, anyways?
