ipv6 disagreement on Status page


#1

All is well…except: “This domain (my www variant) should resolve to your box’s IP address (AAAA…”

My ipV6 address includes 00ff. Somewhere, something pared it down to just ff, causing the System Status to report the above warning. There is no similar warning for my non-www domain.

So…my public DNS reports the ff (not 00ff). My External DNS page reports it as 00ff.

How can I either:

  1. Fix my box to get rid of the leading 00
  2. Silence that warning

#2

[EDIT] Nope…it’s still warning me. I have two MIAB servers with similar IPv6 addresses. One doesn’t warn me about 00ff, and the other does.

new PS: They both warn me. I probably just wasn’t paying attention.


#3

I’m having the same issue.

It seems like there’s a discreprency between what is removing/expecting the leading zeros in ipv6.

For example, my VPS’ ipv6 reverse DNS control panel removes leading 0’s.

The mail-in-a-box status page seems to expect the leading 0’s to remain.

“This domain should resolve to your box’s IP address (AAAA (ipv6 with leading 0’s)) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to (ipv6 without leading 0’s) in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.”

All the default AAAA records using the (ipv6 with leading 0’s).