I’ve accidently missconfigured the ipv6 address of my host some days ago. ‘nslookup’ reports the correct ipv6 address (tested on different servers), but not ipv6.mailcow.email.
Is there anybody who knows the ttl of this service?

  • Better to not strip answer, in your case 511 is time to next prune of cache of your responding DNS and it can be many things,… you do not see this bc you reduce verbosity of an answer

    In case you want TTL set-up to this domain you need to ask to designated NS so dig AAAA @dexter.ns.servercow.net ipv6.mailcow.email -> 3600 sec

I don’t have IPv6 enabled, but you can check yourself:
dig +nocmd +noall +answer +ttlid a ipv6.mailcow.email

For the ipv4 host it shows 120 seconds:
root@app02:~$ dig +nocmd +noall +answer +ttlid a ipv4.mailcow.email
ipv4.mailcow.email. 120 IN A 49.12.4.251

https://toolbox.googleapps.com/apps/dig/#AAAA/
With “web dig” it shows a TTL of 1 hour.

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

@esackbauer
For ipv6 it shows 511 seconds:
dig +nocmd +noall +answer +ttlid aaaa ipv6.mailcow.email
ipv6.mailcow.email. 511 IN AAAA 2a01:4f8:c17:7906::10
ttl is less enough, but wrong ipv6 is still reported.
BTW: hostname is configured correctly.

Better to not strip answer, in your case 511 is time to next prune of cache of your responding DNS and it can be many things,… you do not see this bc you reduce verbosity of an answer

In case you want TTL set-up to this domain you need to ask to designated NS so dig AAAA @dexter.ns.servercow.net ipv6.mailcow.email -> 3600 sec

No one is typing