Timeline for Host command successful but DNS won't resolve
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2018 at 1:20 | vote | accept | Nathan Wiles | ||
| Apr 16, 2018 at 1:20 | answer | added | Nathan Wiles | timeline score: 0 | |
| Apr 11, 2018 at 1:47 | comment | added | Patrick Mevzek | Do not hijack any existing or potentially existing domain name or TLD. Either use the ones in RFC2606 or register a domain name and use it as suffix for your own internal needs. Do not just take one thinking it is not used or will never be used. | |
| Apr 10, 2018 at 21:55 | comment | added | Nathan Wiles | @JohanMyréen changing from TLD .local to .com did the trick, thanks! Please post this as the answer. | |
| Apr 10, 2018 at 21:47 | comment | added | Nathan Wiles | @dave_thompson_085 I get the following output: files mdns4_minimal [NOTFOUND=return] dns myhostname This "myhostname" tag looks like it should be replaced with something else. | |
| Apr 10, 2018 at 13:28 | comment | added | kemotep | Check this out | |
| Apr 10, 2018 at 8:27 | comment | added | dave_thompson_085 | Check grep ^hosts: /etc/nsswitch.conf and see askubuntu.com/questions/843943/… Note host nslookup dig use DNS directly and do NOT use nsslib like normal programs so you cannot rely on them to give the same results. | |
| Apr 10, 2018 at 5:01 | comment | added | Johan Myréen | Please don't use .local as your own private TLD. It is reserved for Multicast DNS. | |
| Apr 10, 2018 at 4:38 | review | First posts | |||
| Apr 10, 2018 at 5:20 | |||||
| Apr 10, 2018 at 4:35 | history | asked | Nathan Wiles | CC BY-SA 3.0 |