Using HTTPDNS Service via Android SDK

Updated at：2025-11-03

Overview

This article explains how to use the HTTPDNS service to access BOS.

Requirement scenarios

Based on the usage of BOS, the current issues with mobile uploads mainly focus on the following aspects:

(1) DNS resolution failure, resulting in request errors;

(2) Domain name hijacking, where data is tampered with during transmission, bringing network access risks to users such as phishing and privacy theft;

(3) Under poor network conditions, the speed can be slow, and data uploads might time out.
If you use the HTTPDNS service to access BOS, you will have the following advantages:

(1) Security against hijacking, which can effectively reduce the problem of reduced success rates caused by domain name hijacking;

(2) Precise scheduling can provide the optimal access point and reduce user access delay;

(3) When domain name resolution results change, the HTTPDNS service is not affected by the multi-tier caching of traditional DNS services. This allows mobile devices to acquire new resolution results more quickly, bypassing multi-layer caching and effectively reducing the latency in domain name switching.

Therefore, if you are sensitive to the request success rate, delay, and fault stop-loss speed of BOS, you can use the HTTPDNS service to access BOS.

Solution overview

To access BOS using the HTTPDNS service, you need to activate the HTTPDNS service, add project dependencies, reload OkHttpDns, and adjust the Bosclient configuration.

Notes:

Although HTTPDNS includes a certain free quota (currently 3 million free domain name resolutions per natural month), exceeding this quota will incur additional fees. You can decrease the frequency of HTTPDNS server access by configuring parameters such as cache expiration strategies and selecting either HTTPS or HTTP protocols.

When the app is launched for the first time, the default HTTPDNS downgrade option is enabled. The SDK and network library automatically use DNS resolution to send requests. This is a standard process and does not affect the subsequent usage of the HTTPDNS service for accessing BOS.

Practical operations

1. Activate the HTTPDNS service

Go to the HTTPDNS Official Documentation and complete the service activation;
In the domain name management under Configuration Management, add *.bcebos.com, or the custom domain name or CDN domain name used by the business;
Test the functionality of HTTPDNS.

2. Add project dependencies

We provide an easy-to-use remote dependency setup for utilizing HTTPDNS.

Open the build.gradle of the module that needs to reference this SDK and add the following at the end:

                Java
                
            

                repositories{
    jcenter()
    maven {
        url "https://raw.githubusercontent.com/bdhttpdns/BDHttpDnsSDK/master"
    }
}
            

Add under dependencies:

                Java
                
                dependencies{
    compile 'com.baidu:httpdns:1.3'
}

3. Reload OkHttpDns

Set the account and password for the newly activated HTTPDNS service, and preload commonly used domain names to avoid cache misses during the initial request. At the same time, you can also set various processing strategies to better meet business needs. For reference, see Mobile Domain Name Resolution Android_SDK Setting Interface.

                Java
                
            

                static class OkHttpDns implements Dns {
    private static OkHttpDns instance = null;
    private BDHttpDns httpDns;
    
    private OkHttpDns(Context context) {
        this.httpDns = BDHttpDns.getService(context);
        this.httpDns.setAccountID(account);
        this.httpDns.setSecret(secret);
 // Preload domain names
        ArrayList<String> preResolveHosts = new ArrayList<String>();
        preResolveHosts.add("bj.bcebos.com");
        this.httpDns.setPreResolveHosts(preResolveHosts);
    }
    
    public static OkHttpDns getInstance(Context context) {
        if(instance == null) {
            instance = new OkHttpDns(context);
        }
        return instance;
    }
    
    @Override
    public List<InetAddress> lookup(final String hostname) throws UnknownHostException {
 // Obtain IP through synchronous resolution interface
        final BDHttpDnsResult httpDnsResult = httpDns.syncResolve(hostname, false);
        Log.v("dns", "HttpDns resolve type: " + httpDnsResult.getResolveType());
 // Give priority to using IPv6 results. For IPv6 results, you need to add [] characters before and after the IP
 // If there is no IPv6 result, use the IPv4 result
        ArrayList<String> ipv6List = httpDnsResult.getIpv6List();
        ArrayList<String> ipv4List = httpDnsResult.getIpv4List();
        String ip = null;
        if (ipv6List != null && !ipv6List.isEmpty()) {
            ip = "[" + ipv6List.get(0) + "]";
        } else if (ipv4List != null && !ipv4List.isEmpty()) {
            ip = ipv4List.get(0);
        } else {
            Log.v("DNS", "Get empty iplist from httpdns, use origin url");
        }
        if(ip != null) {
            final String finalIp = ip;
 // If the IP is not null, use the IP directly for network requests
            List<InetAddress> inetAddresses = Arrays.asList(InetAddress.getAllByName(ip));
            Log.d("DNS", "inetAddresses:" + inetAddresses);
            return inetAddresses;
        }
 // If null is returned, use the system DNS service to resolve the domain name
        return Dns.SYSTEM.lookup(hostname);
    }
}
            

4. Adjust Bosclient configuration

Utilize the setDns method.

                Java
                
            

                BosClientConfiguration config = new BosClientConfiguration();
config.setCredentials(new DefaultBceCredentials(accessKeyId, secretAccessKey));
config.setEndpoint(bos_endpoint);
config.setProtocol(Protocol.HTTP);
config.setDns(OkHttpDns.getInstance(getApplicationContext()));
            

5. Experience immediately

After completing the steps above, you can seamlessly experience HTTPDNS domain name resolution services while using BOS.

HTTPDNS Service

How to Solve Browser Cross-Origin CORS Issues

Client-Side Encryption Practice

BOS

BOS