Affected URL(s)
https://nodejs.org/api/dns.html#dnspromisesreverseip
Description of the problem
fixing incorrect 4.4.4.4
to (what I assume) should be 8.8.8.8/8.8.4.4/dns.google (Google DNS 1 2 3).
note
not sure what the source of this mistake is
(I think it was an old Verizon name server),
but I see this a lot and not just in n00b codes,
but in big a$$ companies as well..
in most cases running the code in the example will just render a timeout (and a puzzled developer),
in other cases (silent fallback..) it may go through the os default name resolving chain which will render some unexpected results and be somewhat challenging to debug.. :|
edit:
IP address ranges that are designated for use in documentation 1
I would prefer a working example.
edit:
- https://github.com/features/code-search/signup
- https://cs.github.com/?scopeName=All+repos&scope=&q=repo%3Anodejs%2Fnode+%224.4.4.4%22
Affected URL(s)
https://nodejs.org/api/dns.html#dnspromisesreverseip
Description of the problem
fixing incorrect
4.4.4.4to (what I assume) should be
8.8.8.8/8.8.4.4/dns.google(Google DNS 1 2 3).note
not sure what the source of this mistake is
(I think it was an old Verizon name server),
but I see this a lot and not just in n00b codes,
but in big a$$ companies as well..
in most cases running the code in the example will just render a timeout (and a puzzled developer),
in other cases (silent fallback..) it may go through the os default name resolving chain which will render some unexpected results and be somewhat challenging to debug.. :|
edit:
I would prefer a working example.edit: