- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- BIND DNS record
Operating System - HP-UX
1748169
Members
4137
Online
108758
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2011 11:56 PM
04-22-2011 11:56 PM
how to add two A records in bind dns, the two should have the same HOSTNAME but different IP address.
the scenario is, when DNS detects the first IP is unreachable it will directly use the second record with the second IP to refer to the same HOSTNAME.
thanks
the scenario is, when DNS detects the first IP is unreachable it will directly use the second record with the second IP to refer to the same HOSTNAME.
thanks
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2011 04:01 AM
04-23-2011 04:01 AM
Solution
> how to add two A records in bind dns, the two should have the same HOSTNAME but different IP address.
Just write two A records, like this:
hostname IN A 111.111.111.111
hostname IN A 222.222.222.222
The DNS server will return both records to the client asking for the A record of "hostname". The records will normally be returned in round-robin order, i.e. the first answer has 111.111.111.111 listed as the first address, the second answer lists 222.222.222.222 as the first one, etc.
> the scenario is, when DNS detects the first IP is unreachable it will directly use the second record
This is a nice theory, but unfortunately it won't work so well in practice.
The DNS server won't check the reachability of the IPs: that is not its job. Whether the DNS server can reach some IP or not has no bearing on whether the client can reach it too. Sometimes the client is authorized to access some things the DNS server is forbidden to access; sometimes the client may be blocked from accessing some IP addresses, either intentionally or otherwise.
Besides, the only sure way to test if an IP address is reachable is to try and access it. If the host responds immediately, either positively (connection accepted) or negatively (with a TCP reset or an ICMP error packet), there is no problem. But what to do when there is no answer at all? If you're attempting a TCP connection, the standard says you should wait up to 1-3 minutes while retransmitting the connection request multiple times. For a WWW application, this is clearly too slow: the user will often run out of patience before the timeout expires.
Most web browsers will use multiple sockets and other strategies to achieve faster response. Because of this, the DNS round-robin is not suitable as a high-availability solution for HTTP services: a common result is that when one of the servers is unreachable, you'll get a partially-loaded web page with some individual images and other page elements missing/broken.
MK
Just write two A records, like this:
hostname IN A 111.111.111.111
hostname IN A 222.222.222.222
The DNS server will return both records to the client asking for the A record of "hostname". The records will normally be returned in round-robin order, i.e. the first answer has 111.111.111.111 listed as the first address, the second answer lists 222.222.222.222 as the first one, etc.
> the scenario is, when DNS detects the first IP is unreachable it will directly use the second record
This is a nice theory, but unfortunately it won't work so well in practice.
The DNS server won't check the reachability of the IPs: that is not its job. Whether the DNS server can reach some IP or not has no bearing on whether the client can reach it too. Sometimes the client is authorized to access some things the DNS server is forbidden to access; sometimes the client may be blocked from accessing some IP addresses, either intentionally or otherwise.
Besides, the only sure way to test if an IP address is reachable is to try and access it. If the host responds immediately, either positively (connection accepted) or negatively (with a TCP reset or an ICMP error packet), there is no problem. But what to do when there is no answer at all? If you're attempting a TCP connection, the standard says you should wait up to 1-3 minutes while retransmitting the connection request multiple times. For a WWW application, this is clearly too slow: the user will often run out of patience before the timeout expires.
Most web browsers will use multiple sockets and other strategies to achieve faster response. Because of this, the DNS round-robin is not suitable as a high-availability solution for HTTP services: a common result is that when one of the servers is unreachable, you'll get a partially-loaded web page with some individual images and other page elements missing/broken.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP