But /etc/hosts has nothing to do with DNS. Yes, they are both related to host name resolving, but so is NetBIOS.
Why should I know that I first ask the known root DNS about which server knows about .tld, then use the returned NS records to contact the next DNS server about a name server for example.tld so that I can ask that server what www.example.tld is, only to get told it is a CNAME so I have to do the same thing until I finally get a hold on an A record.
They are looking for a back-end developer working on standard business logic. Not for a network engineer or a developer writing a DNS client or server.
Oh wait... we did not even reach the DNS part yet, we are first going to through the OS's name resolving. Maybe messed up the resolv.conf or nsswitch.conf. We're also supposed to be system admins.
So how about that multi threaded weighted graph exploration algorithm...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But
/etc/hostshas nothing to do with DNS. Yes, they are both related to host name resolving, but so is NetBIOS.Why should I know that I first ask the known root DNS about which server knows about
.tld, then use the returnedNSrecords to contact the next DNS server about a name server forexample.tldso that I can ask that server whatwww.example.tldis, only to get told it is aCNAMEso I have to do the same thing until I finally get a hold on anArecord.They are looking for a back-end developer working on standard business logic. Not for a network engineer or a developer writing a DNS client or server.
Oh wait... we did not even reach the DNS part yet, we are first going to through the OS's name resolving. Maybe messed up the
resolv.confornsswitch.conf. We're also supposed to be system admins.So how about that multi threaded weighted graph exploration algorithm...