| Home | Libraries | People | FAQ | More

##### ip::basic_resolver_query::basic_resolver_query (4 of 4 overloads)

Construct with specified host name and service name for a given protocol.

    basic_resolver_query(
        const protocol_type & protocol,
        const std::string & host_name,
        const std::string & service_name,
        resolver_query_base::flags resolve_flags = address_configured);

This constructor is typically used to perform name resolution for communication with remote hosts.

###### Parameters

protocol

  A protocol object, normally representing either the IPv4 or IPv6 version of an internet protocol.

host_name

  A string identifying a location. May be a descriptive name or a numeric address string. If an empty string and the passive flag has been specified, the resolved endpoints are suitable for local service binding. If an empty string and passive is not specified, the resolved endpoints will use the loopback address.

service_name

  A string identifying the requested service. This may be a descriptive name or a numeric string corresponding to a port number. May be an empty string, in which case all resolved endpoints will have a port number of 0.

resolve_flags

  A set of flags that determine how name resolution should be performed. The default flags are suitable for communication with remote hosts.

###### Remarks

On POSIX systems, host names may be locally defined in the file `/etc/hosts`. On Windows, host names may be defined in the file `c:\windows\system32\drivers\etc\hosts`. Remote host name resolution is performed using DNS. Operating systems may use additional locations when resolving host names (such as NETBIOS names on Windows).

On POSIX systems, service names are typically defined in the file `/etc/services`. On Windows, service names may be found in the file `c:\windows\system32\drivers\etc\services`. Operating systems may use additional locations when resolving service names.