You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dns: domain must be fully qualified / or what does it do? #126
The fully qualified domain name consists of three or more labels: The top level domain, the domain names, optional subdomains, and the host name.
So, from what I understand, a www.foo.com should be a fqdn, while foo.com is not. You could try with foo.com. (trailing dot), but i'm not sure that it's going to work.
What can we do better?
- don’t require a fqdn (a less strict check),
- assert resolved ips against []string list of IPs,
- check ipv6 options (AAAA record)
If you have other suggestions, please add a comment with a related feature
request for the dns checker, or a new issue if a different area of checkup
Activity
titpetric commentedon May 21, 2020
So, from what I understand, a
www.foo.comshould be a fqdn, whilefoo.comis not. You could try withfoo.com.(trailing dot), but i'm not sure that it's going to work.titpetric commentedon May 21, 2020
https://ut.service-now.com/sp?id=kb_article&number=KB0011254
rrjanbiah commentedon May 21, 2020
@titpetric Thank you so much for your quick reply. So, is it different from
nslookup? IOW, is it to check if the given hostname is resolving? TIArrjanbiah commentedon May 21, 2020
Also, for the sake of record trailing dot fixed it.
titpetric commentedon May 21, 2020
rrjanbiah commentedon May 21, 2020
@titpetric I think, current checks are perfectly fine. Some doc or sample config will suffice, IMHO.