I hope you can help me.

I have 5 Public IP's in an subnet `186.121.200.X/29`

I have `example.com` addressed to one of those public IPs, and some subdomains that point to the rest of them.

Now, I have other 5 Public IP's in another subnet `190.181.15.Y/29`

**My question is:**

*Can I configure `example.com` to also point to an IP of the subnet `190.181.15.Y/29` ?*

*How can I do it?*

I have these configuration files:

```
(named.conf.options)
options {
        directory "/var/cache/bind";
        forwarders {
                // Google Public DNS (IPv4)
                8.8.8.8;
                8.8.4.4;
                // Google Public DNS (IPv6)
                2001:4860:4860::8888;
                2001:4860:4860::8844;
                // ADSL router
                186.121.200.X;
        };
        dnssec-validation auto;
        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
};
(named.conf.local)
zone "example.com" {
        type master;
        file "/etc/bind/db.direct";
        allow-query { any; };
};
zone "206.121.186.in-addr.arpa" {
        type master;
        file "/etc/bind/db.reverse";
        allow-query { any; };
};
(db.direct)
$TTL    604800
@       IN      SOA     example.com. root.example.com. (
                             11         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@               IN       NS     example.com.
@               IN       MX     10    mail
@               IN       A      186.121.206.X1
www             IN       A      186.121.206.X1
mail            IN       A      186.121.206.X2
subdomain1      IN       A      186.121.206.X3
subdomain2      IN       A      186.121.206.X4
subdomain3      IN       A      186.121.206.X5

(db.reverse)
$TTL    604800
@       IN      SOA     example.com. root.example.com. (
                              8         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      example.com.
X1     IN      PTR     ns.example.com.
X1     IN      PTR     www.example.com.
X2     IN      PTR     mail.example.com.
X3     IN      PTR     subdomain1.example.com.
X4     IN      PTR     subdomain2.example.com.
X5     IN      PTR     subdomain3.example.com.

```

EDIT:
I have tried doing the following:

```
(db.direct)
...
subdomain4      IN       A      190.181.15.Y1

```

```
(db.reverse)
...
Y1     IN      PTR     subdomain4.example.com.

```

When saving files and restarting bind, the subdomain responds to a ping.

`ping subdomain4.example.com`

`PING subdomain4.example.com (190.181.15.Y1) 56(84) bytes of data.`

But when accessing subdomain by browser, it redirects to Public IP. It is not kept with the name of the subdomain.

What is the problem?
['https://serverfault.com/questions/1021071', 'https://serverfault.com', 'https://serverfault.com/users/578810/']
You can add multiple ip addresses for a single record in a zone, but you can't control (without additional resources) which ip will be resolved for each request, there'll be random resolutions (e: for two ip addresses, 50% of possibilities for each one)
If I'm not mistaking, you are trying to do:

```
subdomain1      IN       A      186.121.206.X3

```

Then point the reverse IP of:

```
190.181.15.Y      IN       PTR      subdomain1.example.com.  

```

Based on my experience, the organization who had received the direct IP allocation from ARIN, APNIC, AFRINIC, RIPE (regional IP registrant organization) is able to create a PTR record for the IP address that they received from their regional IP registrant.

I do not believe any regional IP registrant ever provided IPs that are smaller than a class C (/24).

So, you can do below (multiple A records for the same subdomain), but the result IP when looking up subdomain1.example.com is randomly selected

```
subdomain1      IN       A      186.121.206.X3
subdomain1      IN       A      190.181.15.Y3

```

Unless you own 190.181.15.Y, even though you create PTR record like below for the IPs, those PTR records more likely won't be available publicly unless on a rare situation that the owner of the IPs provided you an option to create PTR records for their IP address:

```
15.181.190.in-addr.arpa. IN SOA ns.example.com. 
Y3      IN       PTR      subdomain1.example.com.  

```