search for: dnsbest

On 11/03/15 18:01, James wrote: > Bob, > > Take a look at the following two links. > > http://retrohack.com/a-word-or-two-about-dns-islanding/ > > http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx#dnsbest > > I have more than two DC's but generally I would have each one point at > the other. > > I tried that, pointing each DC to the other and my DNS resolving slowed to a crawl, hung for short periods and generally became unresponsive. I just have: search <dns domain> nam...

...; any use. > > >If you're having more than one DC, then you should not use the own DNS >as primary on a DC. It can cause problems like DNS islanding. > >Some DNS best practices: >http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail >-sack-saturday-edition.aspx#dnsbest > > >We should mention this on the "Join as DC" page and somewhere >on the DNS >pages, too. I'll put this on my list. > > >Regards, >Marc >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.o...

When running two DC's is the recommended practice for the first DC to resolve to itself, like this: first DC /etc/resolv.conf file: search samdom.tld nameserver [DC1 ip address] nameserver 127.0.0.1 And on second DC to both DC1 and DC2, like this: search samdom.tld nameserver [DC1 ip address] nameserver [DC2 ip address] nameserver 127.0.0.1 Or is the incorrect? --

Hello, what IP(s) should be set for each domain controller? If there are two should both have their own IP set in resolv.conf or should they have the IPs of both DCs? Or possibly just 127.0.0.1 on each DC? Second thing I had was that clients with DNS set to both DCs could not resolve a special host in the internet while the DNS forwarder can. I needed to restart DCs to get it work again. Thanks

...g more than one DC, then you should not use the own DNS >>> as primary on a DC. It can cause problems like DNS islanding. >>> >>> Some DNS best practices: >>> http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail >>> -sack-saturday-edition.aspx#dnsbest >>> >>> >>> We should mention this on the "Join as DC" page and somewhere >>> on the DNS >>> pages, too. I'll put this on my list. >>> >>> >>> Regards, >>> Marc >>> -- >>> To unsubscrib...

...;>If you're having more than one DC, then you should not use the own DNS >>as primary on a DC. It can cause problems like DNS islanding. >> >>Some DNS best practices: >>http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail >>-sack-saturday-edition.aspx#dnsbest >> >> >>We should mention this on the "Join as DC" page and somewhere >>on the DNS >>pages, too. I'll put this on my list. >> >> >>Regards, >>Marc >>-- >>To unsubscribe from this list go to the following URL and read...

...ng to DC1. > I changed that later on as I want to be able to continue to operate > DC2 while DC1 is down. It's better if you use the local IP only as _secondary_ nameserver entry in your resolv.conf. https://blogs.technet.microsoft.com/askds/2010/07/17/friday-mail-sack-saturday-edition/#dnsbest Regards, Marc