- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: DNS issue
Operating System - Linux
1748128
Members
3806
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО05-21-2011 11:27 PM
тАО05-21-2011 11:27 PM
DNS issue
hi all,
I have a sles 10 system and Oracle BI is installed on the same.
Authentication for Oracle BI users is through windows AD.
when i do a nslookup to the windows AD in our network, this is what I get:
nslookup mic.com
Server: 10.1.1.100
Address: 10.1.1.100#53
Name: mic.com
Address: 10.1.1.110
Name: mic.com
Address: 10.25.100.2
Name: mic.com
Address: 10.1.1.100
one is primary and other two are backup domain controllers:
out of the three, one domain controller is at a remote site and is not accessible from the Oracle BI server.
when i ping mic.com from the Linux BI server I am taken to one of the three Windows DCs alternatively in a round-robin fashion.
i.e
if I ping mic.com I am taken to 10.1.1.110
few seconds later
if I ping mic.com I am taken to 10.25.100.2
few seconds later
if I ping mic.com I am taken to 10.1.1.100
this doesn't happen on windows clients.
so every time a user authenticates he is either taken either of the three IPs. As I said earlier the third backup DC is not accessible from the Oracle BI server resulting in users complaining about failed windows authentication off and on.
I have a sles 10 system and Oracle BI is installed on the same.
Authentication for Oracle BI users is through windows AD.
when i do a nslookup to the windows AD in our network, this is what I get:
nslookup mic.com
Server: 10.1.1.100
Address: 10.1.1.100#53
Name: mic.com
Address: 10.1.1.110
Name: mic.com
Address: 10.25.100.2
Name: mic.com
Address: 10.1.1.100
one is primary and other two are backup domain controllers:
out of the three, one domain controller is at a remote site and is not accessible from the Oracle BI server.
when i ping mic.com from the Linux BI server I am taken to one of the three Windows DCs alternatively in a round-robin fashion.
i.e
if I ping mic.com I am taken to 10.1.1.110
few seconds later
if I ping mic.com I am taken to 10.25.100.2
few seconds later
if I ping mic.com I am taken to 10.1.1.100
this doesn't happen on windows clients.
so every time a user authenticates he is either taken either of the three IPs. As I said earlier the third backup DC is not accessible from the Oracle BI server resulting in users complaining about failed windows authentication off and on.
- Tags:
- DNS
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2011 02:24 AM
тАО05-22-2011 02:24 AM
Re: DNS issue
Please run "man resolv.conf" and look for the "sortlist" option. If it's not supported in SLES 10, too bad.
If Oracle BI uses the standard system library functions for DNS queries (like almost all programs do), adding "sortlist 10.1.0.0/255.255.0.0" to /etc/resolv.conf might help. It should cause the 10.1.*.* addresses to always be given to applications before 10.25.*.* (or any other) addresses associated with the same hostname.
This is just a workaround, though: the real fix would be to make Oracle BI use a smarter DNS lookup algorithm when looking for AD. Unfortunately, this is probably something only Oracle (the company) can do.
MK
If Oracle BI uses the standard system library functions for DNS queries (like almost all programs do), adding "sortlist 10.1.0.0/255.255.0.0" to /etc/resolv.conf might help. It should cause the 10.1.*.* addresses to always be given to applications before 10.25.*.* (or any other) addresses associated with the same hostname.
This is just a workaround, though: the real fix would be to make Oracle BI use a smarter DNS lookup algorithm when looking for AD. Unfortunately, this is probably something only Oracle (the company) can do.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-23-2011 02:37 AM
тАО05-23-2011 02:37 AM
Re: DNS issue
thank you Matti. i will check this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-23-2011 10:45 AM
тАО05-23-2011 10:45 AM
Re: DNS issue
try add this to resolv.conf too
options timeout:1
options attempts:1
The first option tells the resolver to timeout for 1 sec before switching to the second DNS server listed. The second options said only query the same DNS once.
This does not solve your issue but will help you shorten the DNS failover time.
options timeout:1
options attempts:1
The first option tells the resolver to timeout for 1 sec before switching to the second DNS server listed. The second options said only query the same DNS once.
This does not solve your issue but will help you shorten the DNS failover time.
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