× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Remember:
IBM i DNS is BIND.
Windows DNS is not BIND.

That should help you with some of your thinking and pretty much any other blogs Wikis etc about BIND will apply to IBM i.

That said you have a couple choices, easy and hard(er). If you simply set a domain such as 'domain1.corp.' on IBM i to forward all queries to AD then you have made step one. IBM i is answering but only as a 'proxy'.

Then if you set it up as secondary it will query AD and remember those queries so it can reply from cache. (Faster)

The final step is to enable notifications. Thus when the IP address for FQDN server2.domain1.corp. is changed in AD then AD will notify BIND outside the normal timeout that there has been a change. Without this BIND will continue to report the old IP address until the cache timeout expires and it finally requeries AD. I have not tried this so I don't know if it's possible with AD to BIND. In a BIND BIND world this is easy (Directive 'Alsonotify')

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 5/30/2017 11:35 AM, Rob Berendt wrote:
I am thinking of starting an IBM i based DNS server on one of our hosting
lpars.
I would like it to sync up with our existing Windows based DNS servers.
Anyone do this with a wiki, blog, etc?


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.