Page 14 of 19

Re: Server updates

Posted: Mon Jun 13, 2022 2:22 pm
by exxos
I may need to update the DNS again for IPv6 support. So we may go down again for a bit later.

Re: Server updates

Posted: Mon Jun 13, 2022 2:35 pm
by stween
exxos wrote: Mon Jun 13, 2022 2:22 pm I may need to update the DNS again for IPv6 support. So we may go down again for a bit later.
Oh, you've dropped a link-local (fe80) address into the public record. A mistake? That will do no harm, but everything will ignore it because it's not globally routable.

Re: Server updates

Posted: Mon Jun 13, 2022 2:38 pm
by exxos
stween wrote: Mon Jun 13, 2022 2:35 pm Oh, you've dropped a link-local (fe80) address into the public record. A mistake? That will do no harm, but everything will ignore it because it's not globally routable.
Have no idea what that means :)

I just added a AAAA record for the IPv6 .. I think..

https://www.123-reg.co.uk/support/domai ... main-name/

Apparently I am supposed to remove the v4 one... But I have a feeling everything will break if I do.

Re: Server updates

Posted: Mon Jun 13, 2022 2:52 pm
by stween
exxos wrote: Mon Jun 13, 2022 2:38 pm
stween wrote: Mon Jun 13, 2022 2:35 pm Oh, you've dropped a link-local (fe80) address into the public record. A mistake? That will do no harm, but everything will ignore it because it's not globally routable.
Have no idea what that means :)

I just added a AAAA record for the IPv6 .. I think..

https://www.123-reg.co.uk/support/domai ... main-name/
Link-local is an address range which only operates on the local ethernet/wifi link; it won't be routed anywhere else. IPv6 network configs alway show the link-local address to you. But because it's locally scoped, it can't be used over the internet to reach your network from mine.

So it's redundant in that AAAA record; clients will get the record and immediately ignore it because they can't use it. They'll always select the A record instead.

If your host has another IPv6 address (it'll start with a 2), then that's your public one. Happy to test it before DNS changes, if you like. If your host doesn't have that, then it's not been configured with public v6.
Apparently I am supposed to remove the v4 one... But I have a feeling everything will break if I do.
If you do that right now, nobody will reach you. If you set up public v6 then remove the A record, you might lose 60% of your users :)

Re: Server updates

Posted: Mon Jun 13, 2022 2:55 pm
by exxos
Not sure how to find the IPv6.. all the sites say something different :roll:

I think its 2a00:d880:11::243 so added that just..

Re: Server updates

Posted: Mon Jun 13, 2022 3:13 pm
by stween
exxos wrote: Mon Jun 13, 2022 2:55 pm Not sure how to find the IPv6.. all the sites say something different :roll:
Assuming linux or closely related, "ip addr list" or "ifconfig', will list inet6 addresses.
I think its 2a00:d880:11::243 so added that just..
Yup, that responds with exxosforum content.

Code: Select all

$ curl -H "Host: exxosforum.co.uk" http://[2a00:d880:11::243]
<html>
<head>
<title>EXXOS FORUM</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

<meta http-equiv="refresh" content="0; url=https://www.exxosforum.co.uk/forum/index.php" />

</head>
<body>

</body>
</html>
Change your existing AAAA to remove the fe80 address, replace it with the 2a00 address, and I reckon you're done.

Re: Server updates

Posted: Mon Jun 13, 2022 3:13 pm
by exxos
Not happy still for some reason.

Code: Select all

host aspmx.l.google.com[2a00:1450:4025:402::1b] said:
    550-5.7.1 [2a00:d880:11::243] Our system has detected that this message
    does not 550-5.7.1 meet IPv6 sending guidelines regarding PTR records and
    authentication 550-5.7.1 . Please review 550-5.7.1
    https://support.google.com/mail/?p=IPv6AuthError for more information 550
    5.7.1 . sa35-20020a1709076d2300b00712128834c2si8132567ejc.408 - gsmtp (in
    reply to end of DATA command)
This was trying to send a email to @IngoQ and also had the same problem with @terriblefire Though when I had the previous number in IPv6, @terriblefire emai seemed to then work :shrug:

https://mxtoolbox.com/SuperTool.aspx still reports the wrong number :roll:

Capture.PNG
Capture.PNG (23.93 KiB) Viewed 1529 times

Guess i'll have to wait a bit ...

Re: Server updates

Posted: Mon Jun 13, 2022 3:29 pm
by IngoQ
The notifications worked, I guess they did a fallback to IPv4?

But the AAAA-Record is still unchanged, even if you query your hosters DNS directly:

host exxosforum.co.uk ns44.domaincontrol.com
Using domain server:
Name: ns44.domaincontrol.com
Address: 173.201.69.22#53
Aliases: 

exxosforum.co.uk has address 185.52.2.172
exxosforum.co.uk has IPv6 address fe80::f816:3eff:fe20:5ec0
exxosforum.co.uk mail is handled by 31 exxosforum.co.uk.


Re: Server updates

Posted: Mon Jun 13, 2022 3:30 pm
by stween
exxos wrote: Mon Jun 13, 2022 3:13 pm Not happy still for some reason.

Code: Select all

host aspmx.l.google.com[2a00:1450:4025:402::1b] said:
    550-5.7.1 [2a00:d880:11::243] Our system has detected that this message
    does not 550-5.7.1 meet IPv6 sending guidelines regarding PTR records and
    authentication 550-5.7.1 . Please review 550-5.7.1
    https://support.google.com/mail/?p=IPv6AuthError for more information 550
    5.7.1 . sa35-20020a1709076d2300b00712128834c2si8132567ejc.408 - gsmtp (in
    reply to end of DATA command)
Ah, mail. You do have a PTR record set up for that v6 address

Code: Select all

$ dig -x 2a00:d880:11::243 +short
exxosforum.co.uk.
But the page that google links to suggests they use other signals. I haven't gone digging further.

If v6 is a headache that you want to avoid for mail, you could consider putting mail on its own subdomain without any AAAA records. That pains my ipv6 heart, but I also hate doing mail ops.
Capture.PNG


Guess i'll have to wait a bit ...
I think your authoritative is still issuing the fe80 address. So either their revision control is extremely slow, or it didn't take when you tried to change it.

Re: Server updates

Posted: Mon Jun 13, 2022 4:35 pm
by exxos
For some reason it had reverted back to the previous old number :shrug:

I deleted it out and put it back in again and now I think it is okay ?